PeopleMuster

Daily work log template

A daily work log records what you did today, block by block, while you still remember it. Each line has a start time, an end time, the project, the task and what came of it. Five minutes at the end of the day turns those lines into a short recap: hours, what's finished, what's stuck and what's next.

Use a daily log when your work is split across projects, or when your manager reads a recap instead of holding a stand-up. It also helps anyone who has to explain a week later where a Tuesday went. When all you need is a start and finish time for pay, the weekly timesheet is shorter.

DAILY WORK LOG
Name: [YOUR NAME]
Date: [DATE]
Planned hours today: [PLANNED HOURS]

TIME BLOCKS
From | To | Hours | Project | What I worked on | Outcome | State
[FROM] | [TO] | [HOURS] | [PROJECT] | [TASK] | [OUTCOME] | Done / Ongoing / Blocked
[FROM] | [TO] | [HOURS] | [PROJECT] | [TASK] | [OUTCOME] | Done / Ongoing / Blocked
[FROM] | [TO] | [HOURS] | [PROJECT] | [TASK] | [OUTCOME] | Done / Ongoing / Blocked
[FROM] | [TO] | [HOURS] | [PROJECT] | [TASK] | [OUTCOME] | Done / Ongoing / Blocked
[FROM] | [TO] | [HOURS] | [PROJECT] | [TASK] | [OUTCOME] | Done / Ongoing / Blocked
[FROM] | [TO] | [HOURS] | [PROJECT] | [TASK] | [OUTCOME] | Done / Ongoing / Blocked

END-OF-DAY RECAP
Hours logged: [TOTAL HOURS] of [PLANNED HOURS]
Hours by project: [PROJECT] [HOURS] / [PROJECT] [HOURS] / Internal [HOURS]
Finished today: [FINISHED]
Blocked on: [BLOCKER] (waiting for [WHO])
First thing tomorrow: [NEXT TASK]

What to put in each blank

[FROM]
Write the time you started the block on a 24-hour clock. Blocks of 30 minutes or more are enough; nobody needs a line for every email.
[HOURS]
Round to the nearest quarter hour, such as 1.25 or 0.5.
[TASK]
Name the task in words a colleague would recognise: 'client onboarding call', not 'meeting'.
[OUTCOME]
Say what exists now that didn't this morning: a sent draft, a fixed bug, a decision. Leave it blank only for work still under way.
[BLOCKER]
Describe what stops the next step, in one line. Name who it waits on, so the recap reader can act.
[NEXT TASK]
Pick one task to start tomorrow. A single task gets started; a list of five gets reread.

Before you send it

  • Fill the log as you switch tasks, not at 18:00. Blocks written after the fact shrink the hard work and stretch the easy work.
  • Use the same project names every day. Hours totalled by project only add up when the names match.
  • Send the recap, not the whole log, to whoever reads it. Five lines get read; a table of twelve blocks gets skimmed.
  • Keep a week of logs together before you judge anything. One day is noise; five days show a pattern.

In PeopleMuster the daily recap is where people log how each day was spent, per project, and an admin sets the logging window that decides how far back a day can still be filled in.

Questions people ask about this letter

How do I log daily activities without losing an hour to it?

Write one line each time you switch tasks, which takes under a minute. Then spend five minutes on the recap at the end of the day. Most people land at about 10 minutes a day once the project names are fixed.

What is the difference between a daily work log and a timesheet?

A timesheet records hours, usually per project. A daily work log records hours plus what the hours produced. Many teams keep the log and total its hours column into the timesheet at the end of the week.

How far back can someone fill in a missed day?

Set a rule and write it down, such as two working days. Past that, memory fills gaps with guesses. A short, fixed window keeps logs honest without punishing a genuinely busy day.

Other templates