Daily work log: what to record each workday
Updated 7 min read By David from TimeRetain
A daily work log is a short, private record of what you finished, what got in the way, and what comes next. You write it yourself, because the thinking is the point. A few lines at the end of the day give tomorrow-you a place to start.
- Date:
- Worked on:
- Done:
- Blocked / slow:
- Decided:
- Next:
Date: Worked on: - - Done: - Blocked / slow: - Decided: - Next: -
Copy the template into a note. Keep one dated entry per workday. A short line can be enough for each field, and you can leave a field blank when nothing applies.
A daily work log example
A filled-in day might look like this:
- Date:
Thu 18 Jun
- Worked on:
- Newsletter draft, launch email sequence
- Reviewed ad performance
- Done:
- Newsletter draft finished, sent to design
- Blocked / slow:
- Launch email sequence waiting on final pricing copy, pinged product
- Decided:
- Pausing the low-intent ad group for now, spend is outrunning signups
- Next:
- Draft the LinkedIn launch post while pricing copy is pending
Date: Thu 18 Jun Worked on: - Newsletter draft, launch email sequence - Reviewed ad performance Done: - Newsletter draft finished, sent to design Blocked / slow: - Launch email sequence waiting on final pricing copy, pinged product Decided: - Pausing the low-intent ad group for now, spend is outrunning signups Next: - Draft the LinkedIn launch post while pricing copy is pending
Tomorrow morning, that entry names the finished draft, the missing pricing copy, and a task you can start while you wait.
The same six fields also work for a drawing review. Stay close to output and decisions.
“Worked on drawings” is too vague. Write what changed because you touched them.
- Date:
Thu 18 Jun
- Worked on:
- Beam schedule, connection details
- Done:
- Updated second-floor beam sizes after load review
- Blocked / slow:
- Waiting on revised architectural grid from the design team
- Decided:
- Flagging the cantilever detail for senior review before issue
- Next:
- Check revised grid against column layout, then update detail S-412
Date: Thu 18 Jun Worked on: - Beam schedule, connection details Done: - Updated second-floor beam sizes after load review Blocked / slow: - Waiting on revised architectural grid from the design team Decided: - Flagging the cantilever detail for senior review before issue Next: - Check revised grid against column layout, then update detail S-412
Record what changed
A list of activities can leave out the result: “Attended standup. Answered emails. Worked on the campaign. More emails. Meeting with Sarah.”
That list names the activities, but leaves out what changed. You still need to know whether the campaign draft is ready or the meeting left a decision open.
The useful question is simple: what’s done now that wasn’t done this morning? “Launch email draft finished” tells you more than “worked on the campaign.” “Cut the webinar follow-up from five emails to three” tells you more than “meeting with Sarah.”
When you write the Done line, state the result. If the task is unfinished, record a useful change: “Ruled out two causes of the export error” or “Drafted the opening section.”
If you rebuild the day from timer or calendar entries, their titles rarely name the result, so add that yourself. A title can still leave the task unclear.
Record what held up the work
Use the Blocked / slow line when something delays the work.
The Done line records what changed. If you also need to know whether it worked, add that to the same line. The Blocked / slow line records a specific delay: pricing copy you waited two days for, or a campaign review that sat unanswered.
Across several entries, look for delays that repeat. Those dates give you specific cases to discuss. A single entry records that delay, not the whole explanation for the week.
If someone asks why the campaign slipped, point to the dated entries. “Launch emails waited on pricing copy from Tuesday through Thursday” names one delay.
Keep the note factual. Record what you needed, when you asked for it, and what you could do while you waited.
The “next” line is for tomorrow-you
End every log with one line about what comes next. Where you stopped. What to pick up first.
Name the task and the first action. In the drawing example, “Check revised grid against column layout” gives you a place to resume once the grid arrives.
If the next step depends on someone else, name that dependency too. You can still choose another task tomorrow if priorities change.
Keep the log small
A daily work log goes wrong when it tries to be complete.
You don’t need every task or a minute-by-minute account. Leave out lunch, coffee, the walk, and the group chat unless they explain a detail you need later.
Keep details that help you resume work or explain a decision later.
Leave out anything you’d only write to look busy.
Keep dated blockers and decisions even after the week has passed. Those lines preserve details you can refer to when you discuss a delay.
If the work involves patients or confidential client matters, keep identifying and clinical details out of this note. Those belong in the record your workplace already uses.
Where a work hours log fits
A daily work log is a record of what. Sometimes you also want the how long.
That’s where a work hours log helps. Run a timer while you work, with a short description such as “Newsletter draft.” Group the blocks by client or project so you can find the work behind each summary.
If you start and stop with each work block, the timer records its duration. At the end of the day, you add the result, the blocker, and the next step.
For a rough account of your day, whole-block timing is fine. A couple of hours on the launch page, forty minutes on ad review. This is not a billing record (that’s a different job, and a stricter one).
“I felt slammed” and “I spent four hours in meetings and ninety minutes writing campaign copy” are very different sentences. The second gives you something to investigate: which meetings helped, and which can you shorten or skip?
A time audit worksheet helps when you want to study where the hours went. You don’t need one to write tomorrow’s starting point.
Choose where to keep it
You can keep a daily work log in a notebook, a notes app, a text file, or a spreadsheet. Pick the one you’ll actually open at the end of the day.
The catch is remembering what happened after meetings, messages, and context switches.
A manual timer gives you raw material: a short list of the work blocks you chose to record. Use it to recall the day, then add the decisions and results yourself.
TimeRetain helps you remember the work behind today’s log. A list of the blocks you timed can jog your memory about the newsletter draft or ad review, and shows roughly how long each one took.
Look back at the day’s work when you fill the Worked on line, then add what changed and where to resume.
No account, and no screenshots. Your time records live on your device. Optional Sync stores an encrypted copy on TimeRetain’s servers.
Try timing tomorrow’s work blocks in TimeRetain. Use the list to write what changed and where to start next.
Try it for three days
Start with the template at the top of this article. Skip the setup work. Use a note, unless spreadsheets already feel natural.
For three workdays, fill the six fields at the end of the day: Date, Worked on, Done, Blocked / slow, Decided, Next. Keep it rough. Fragments are fine.
After three days, read it back. If it feels useless, stop. No productivity ritual deserves a permanent slot in your life because an article told you to try it.
But if you read it back and think, “oh, this helps,” keep going.
Then look at the friction. If the log takes a minute or two, you already have the right setup. If it takes five or ten minutes because you’re piecing the day together from memory, try timing your work blocks. Keep the timer only if those records help you write the log.
Questions and answers
What is a daily work log?
A daily work log is a short record of what happened at work today: what you finished, what got in your way, what you decided, and what comes next. Write it for the version of you who sits down tomorrow.
What information should be included in a daily work log?
Six fields are enough: the date, the main work blocks, what you finished, anything that blocked or slowed you, decisions you made, and the one thing to pick up next. A short line per field will do. Leave a field blank when nothing applies.
How do I make a daily work log?
At the end of the day, fill the six fields: date, what you worked on, what you finished, what blocked or slowed you, any decision, and what's next. Keep each field to a short line. If piecing the day together takes five or ten minutes, try timing the blocks and use those records to write the log after.
Should I update a daily work log throughout the day?
You can write the summary at the end of the day. If you forget details, take rough notes or time your work blocks as you go. Use those records to write the result, blocker, decision, and next step.