Daily work log: what to record each workday

A daily work log is a short, private analysis of what you finished, what got in the way, what you decided, and what’s 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.

“What did you get done today?” is the simplest question, and most days you can’t answer it well. You worked for eight hours. You were busy. Properly busy.

The specifics have already gone soft: a couple of meetings, something that broke, a thing you fixed, two things you meant to start and didn’t. By Friday the whole week is a blur.

You don’t need a tracker logging every tab. You need to name what actually changed.

Here is the template, what belongs in it, and when a timer helps.

A daily work log template you can copy

Here’s the whole thing. Paste it into a note, a doc, or the top of a file you keep open:

Date:

Worked on:
-
-

Done:
-

Blocked / slow:
-

Decided:
-

Next:
-

That’s a complete work log template. Six fields. Most days, half of them are one line each.

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:
- Update launch emails once pricing copy lands; write the LinkedIn post

Read that back tomorrow morning and you know exactly where you are.

The same six fields work for drawings, not only a campaign. Stay close to output and decisions.

“Worked on drawings” is too vague. Write what changed because you touched them.

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

The mistake most daily work logs make is recording activity. “Attended standup. Answered emails. Worked on the campaign. More emails. Meeting with Sarah.”

That’s a list of things you sat through. It tells you the day was full. It doesn’t tell you anything you can use.

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.”

So when you write the Done line, state the result. If you can’t, that tells you something: the work was unclear, noise swallowed the day, yet another meeting with Sarah appeared, or urgent tasks crowded out the work you meant to do. The log shows that while it is still fresh.

This is the opposite of what an automatic time tracker does. Those capture every window you opened and every app you touched: activity in enormous detail, and intent nowhere. A daily work log is your own analysis of what you did.

Blockers explain the week

Most people skip the Blocked / slow line, but it’s worth filling in.

Outcomes tell you what worked. Blockers tell you why the week went sideways. The pricing copy you waited two days for. The campaign review that sat unanswered. The messy UTM spreadsheet that ate another hour.

Fill in this line to spot patterns. Dated blocker facts also help later conversations.

When someone asks why the campaign slipped, “I was busy” is a feeling. “Launch emails were blocked on pricing copy for two days, here are the dates” is a fact.

Keep the note factual, light, and off employer systems. A personal log can later be asked for. You are not writing a case file.

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.

Without it you reopen everything, reread where you were, and rebuild the thread you already had yesterday. A single Next line skips most of that.

It costs a few seconds. Tomorrow, it’s usually the line you’re most grateful for.

Keep the log small

A daily work log goes wrong when it tries to be complete.

You don’t need every task. You don’t need a minute-by-minute account. You don’t need to log lunch, the coffee, the walk, the ten minutes you lost to a group chat.

If logging the day takes longer than the smallest real task in it, you’ve overbuilt it. You’ll quit during exactly the busy weeks when it would have helped most.

Leave out anything you’d only write to look busy.

Keep dated blockers and decisions even after the week has passed. Those lines explain why something slipped.

If the work involves a client or a patient, keep their names and clinical detail 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. Put the block on a timeline for the client or project, tag the kind of activity, and add a short description.

At the end of the day the timer has already answered duration. You add the result, the blocker, and the next step.

You rarely need precision down to the minute. 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. Only one tells you what to change.

A time audit worksheet is a different job: start and stop times for a few days, then a review. Do not merge that into these six fields.

The spreadsheet question

You can keep a daily work log in a notebook, a notes app, a text file, or a spreadsheet. It is a note you can keep up with.

The catch is remembering what happened after meetings, messages, and context switches.

A manual timer gives you raw material: a short list of work blocks you chose yourself. Click start, name the block, click stop. Write the analysis at the end of the day, not as a running log.

TimeRetain is a manual timer on your device. You start and stop the blocks yourself, so the day’s list already has intent in it.

Work goes on a timeline per client or project, with tags for the kind of work. Export CSV if you want the hours in a sheet you already use.

No account, and no screenshots. The data stays on your device; sync is optional.

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, write the log by hand at the end of the day. Date. Worked on. Done. Blocked. 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, add a manual timer.