End-of-day report template: EOD format, email and spreadsheet
What is an EOD report? EOD stands for end of day. An EOD report is the short written update you send when you finish work: what you completed, what is still in progress, what is blocked, and what you need from someone else. It lets a manager see the day without a meeting.
Use the fill-in version on this page: type your day, choose plain text, Slack or email, and copy. Nothing you type is saved or sent anywhere. Below you will find the blank template to copy as-is, what belongs on each line, how to send it as an email, what your manager wants from it, a spreadsheet version for Excel or Google Sheets, worked examples for four different roles, and how to write one for a manager in another time zone.
The blank template
Date:
Shipped:
In progress:
Blocked:
Need from you:
Proof/links:
Fill in only the lines that apply and delete the rest. Five honest lines are worth more than twenty padded ones.
What goes on each line
Shipped. What reached done today, each item named specifically. "Merged the refund flow" tells the reader something; "worked on payments" does not.
In progress. What moved, how far it got, and what is left. A rough share of the work or the one remaining step is enough.
Blocked. What is stuck and what would unblock it. This is the most valuable line in the report, because it is the one someone else can do something about. Write it even on a good day if anything is waiting on someone.
Need from you. The specific ask, and from whom: a review, an answer, access, a decision. It turns a report into something the reader can act on straight away.
Proof/links. Links to the work itself. They make the report checkable without a follow-up question, and they protect you: nobody has to take "it is done" on trust.
For the reasoning behind each line and the habits that make reports useless, read how to write an end-of-day report.
EOD report email format
Most EOD reports go out by email or chat. For email, keep the subject line the same every day apart from the date, so your manager can search for it and filter it:
Subject: End-of-day report, 2026-09-21 (Priya)
The date is what makes a month of reports findable later. Add your name if your manager gets reports from several people. The email option in the generator above writes the subject line with the date filled in; add your name to it if you need to.
A sample EOD email to a manager:
Subject: End-of-day report, 2026-09-21 (Priya)
Hi Daniel,
Need from you by Friday: 15 or 22 October for the webinar, so the invite can go out
Shipped: September newsletter sent to the full list
In progress: Webinar landing page; first draft done, waiting on design
Blocked: The webinar invite, until the date is confirmed
Proof/links: The newsletter in the archive and the landing page draft
Priya
The ask has a deadline, so it goes first; on a day with nothing urgent, keep the usual order. The date is in the subject line, so the Date line can go. A one-line greeting is enough: the report is the email, so there is no need for an opening paragraph or a long sign-off.
Ask your manager once whether they want a new email each day or replies on one running thread. A new email is easier to file and forward; one thread keeps the whole week in one place.
In Slack or any other chat app, drop the subject line and the greeting and paste the lines as one message. The Slack option in the generator bolds the labels.
For other update emails, such as a weekly update, a delay or a blocker, see the status update email templates.
Writing it for your manager
The lines are the same whoever reads the report. What changes for a manager is the order and the timing.
Agree the shape once. Some managers want outcomes only; some also want time spent per task. Ask in your first week, then keep the format fixed so they can scan it in the same place every day.
Put a deadline ask at the top. If your "Need from you" line has a date in it, move it to the first line of the email. An ask buried at the bottom of a report can sit unread until the deadline has passed.
Report a slip before it is noticed. If something you said yesterday would be done is not, say so under "In progress" with the new expected day. One line today is easier than explaining it at the end of the week.
Send it at the same time each day. A report that arrives at a predictable time gets read. One that arrives whenever gets skimmed or missed.
Spreadsheet version for Excel or Google Sheets
If you or your manager would rather keep a running log than a pile of emails, use the spreadsheet: one row per day, one column per line of the template.
Download the end-of-day report spreadsheet (CSV)
It opens directly in Excel. In Google Sheets, choose File, then Import, then Upload. The first row is an illustrative example: delete it and add one row each day.
A log shows patterns that single reports hide: the same blocker three days running, or an item that has said "in progress" for a week. For Word or Google Docs, copy the blank template above into a document instead.
Worked examples for four roles
These are illustrative. The names, numbers and links are made up to show the shape, not taken from real reports.
Software engineer
Date: 2026-09-21
Shipped: Search filters on the orders page, merged and on staging
In progress: CSV export, about half done; pagination for large files left
Blocked: Nothing
Need from you: A yes or no on whether exports include cancelled orders
Proof/links: github.com/acme/app/pull/914
Why this works: every line is a state rather than an activity, and the one question is specific enough to answer in a single word.
Sales
Date: 2026-09-21
Shipped: Sent proposals to two new accounts
In progress: Contract review with a logistics prospect; their legal comments are due tomorrow
Blocked: Pricing approval for the three-year version of that deal
Need from you: Sign-off on the multi-year discount by Thursday
Proof/links: The three deal records in the CRM
Why this works: it leads with the outcomes the manager tracks and names the one decision that has a deadline, so it does not sit unread in an inbox.
Customer support
Date: 2026-09-21
Shipped: Closed 34 tickets; wrote a saved reply for the password reset loop
In progress: A refund escalation, waiting on finance
Blocked: Three tickets that cannot close until a login bug is fixed
Need from you: Priority on the login bug; it is behind most of today's volume
Proof/links: The bug ticket and the support queue view
Why this works: it turns a count into a pattern, one bug behind most of the tickets, which is the thing a manager can actually fix.
Remote contractor reporting to a client abroad
Date: 2026-09-21 (IST)
Shipped: Homepage hero redesign, deployed to the preview link
In progress: Mobile menu; desktop is done, tablet breakpoints are left
Blocked: Waiting for the final brand colours
Need from you: The brand colour codes before your morning, so I can finish tomorrow
Proof/links: The preview link and the design file
Why this works: it states the time zone and asks for the missing input before the client's day starts, so a whole day is not lost to the time difference.
Reporting to a manager in another time zone
When your day ends as theirs begins, the report does more work than usual, because it is the only update they get before they start making decisions.
Send it before you log off, not the next morning. It should already be waiting when their day starts.
Put the date in your own time zone, or both. "Yesterday" means different things on either side of the clock.
Lead with anything blocked. Across a large time difference, a blocker raised at the end of your day costs a full day unless it is visible at the start of theirs.
Make every ask answerable without a call: a yes or no question, a specific file, a specific decision. If they have to message you to understand it, you will not see the reply until tomorrow.
End-of-day report or daily report?
Mostly the same document under two names. Both summarize one person's day for whoever depends on it, and this template works for either.
The exception is site work. In construction and field service, a "daily report" is a site log that records weather, crew, equipment and incidents. That is a different document with its own formats, and this template is not it. This one is for knowledge work.
If you manage a team, not just yourself
Filling this in for yourself takes two minutes. Collecting it from ten people every day, and working out which "almost done" is genuinely almost done, is the hard part.
That is what Eodly does. Each person gets asked for a check-in in Slack, Telegram or Discord (Microsoft Teams coming soon), the claims are weighed against what actually moved in GitHub and Linear, and you get one page each evening instead of ten separate reports. Read how to collect end-of-day reports from your whole team.