Quick answer

A good timesheet note names what you did, for what, and why it took the time, in one line a client can read without calling you. Write 'Revised homepage hero copy and two CTA variants per Tuesday feedback' instead of 'design work'. Vague notes are the quiet cause of billing disputes and written-off hours, because a line nobody can picture is a line nobody will pay.

This guide is written for freelancers, agencies, and consultants whose tracked hours end up on a client invoice and who want fewer billing questions and write-downs who want time tracking to support better planning, billing, reporting, and project decisions.

What a defensible note contains

Every useful timesheet note answers three questions: what did you do, what was it connected to, and why did it take the time it took. 'Did' is the action in plain verbs. 'Connected to' is the deliverable, feature, or request it served. 'Why it took the time' is the detail that makes a two-hour entry believable, such as the number of revisions, the problem you solved, or the input you were waiting on. A note that covers all three reads as a record; a note that covers none reads as a guess.

The audience for the note is not you and not your project manager. It is the client's finance person three weeks from now, reading a line item with no memory of the project and a reason to question anything they cannot follow. Write for that reader and the note does double duty: it jogs your own memory when you review the week, and it answers the client's question before they think to ask it.

  • The action, in concrete verbs: drafted, revised, debugged, presented
  • The thing it served: the deliverable, feature, document, or request
  • The reason for the duration: revisions, complexity, scope, or a blocker
  • Enough specificity that a stranger could picture the work

Weak notes and the stronger version

Most bad notes are not wrong, they are empty. 'Admin', 'meeting', 'development', and 'design work' are all technically true and completely unbillable to a skeptical reader, because none of them describes anything a client can connect to value they received. The fix is rarely more words, it is more specific words: swap the category for the actual task and the vague note becomes a defensible one at the same length.

Compare the pairs and the pattern is obvious. 'Meeting, 1h' becomes 'Kickoff call to confirm sitemap and content priorities, 1h'. 'Dev work, 3h' becomes 'Built and tested checkout validation for three edge cases flagged in QA, 3h'. 'Emails, 30m' becomes 'Answered client questions on hosting migration and confirmed go-live date, 30m'. Same hours, same truth, but now every line can stand on an invoice on its own.

  • Weak: 'Design work' → Strong: 'Revised hero section and two CTA layouts per feedback'
  • Weak: 'Meeting' → Strong: 'Kickoff call to confirm sitemap and content priorities'
  • Weak: 'Admin' → Strong: 'Prepared and sent September invoice and project status update'
  • Weak: 'Research' → Strong: 'Compared three payment providers on fees and integration effort'

How to write good notes without slowing down

The objection to detailed notes is always time, and it is a fair one: nobody wants to write an essay per entry. The answer is to write the note while the work is fresh, not to reconstruct it on Friday. A note written the moment you stop a task takes ten seconds and is accurate; the same note written five days later takes two minutes, is vague, and is half invented, which is exactly how hours end up written down out of uncertainty.

Keep the format consistent so it becomes a reflex rather than a decision. Lead with a verb, name the deliverable, add the reason for the time if it is not obvious, and stop. You are not writing prose, you are writing a line of evidence, and evidence is better short and specific than long and padded. If your time tracker lets you note against the entry as you log it, the whole habit costs you almost nothing.

Why vague notes cost real money

Vague notes leak revenue in two places. Before the invoice, you write hours down because you are not confident you can defend them, trimming a three-hour entry to two because 'development, 3h' feels too thin to send. After the invoice, the client queries the lines they cannot follow, and the hours you concede to keep the peace never come back. Both are realization losses, and both trace straight back to a note that failed to describe the work.

The opinion worth stating bluntly is that unbillable notes are a self-inflicted discount, and most firms give it away without ever seeing it. The hour was real and the work was done; the only thing missing was a sentence. Teams that review their notes before billing, rather than their hours alone, consistently recover time they used to quietly surrender, because the fix was never working more, it was writing the line that lets the work speak for itself.

When heavy notes are overkill

Not every engagement needs forensic notes. On a fixed-fee project where the client agreed an outcome and does not see your hours, detailed per-entry notes are mostly for your own cost tracking, and a lighter touch is fine. The same is true for trusted retainers where the relationship carries the trust that an itemised invoice would otherwise have to earn. Match the effort of the note to how closely the line will be read.

What never changes is that the note has to mean something to you later. Even when no client will see it, a timesheet full of 'misc' is a timesheet you cannot learn from, and the whole point of tracking time is to find out where it actually goes. So dial the client-facing detail up or down with the billing model, but keep enough specificity that your own reports still tell you the truth about the week.

Where Zeitio fits

Zeitio helps teams connect tracked hours to clients, projects, tasks, reports, approvals, and invoices so time data becomes useful business context instead of another spreadsheet.

Start with simple time entries, review them weekly, and use the data to improve project planning, billing accuracy, and team workload decisions.

Compare Zeitio pricing or create a workspace to try the workflow.

Further reading

FAQs

What makes a good timesheet note?

A good note names what you did, what it was connected to, and why it took the time, in a single line a client can understand without calling you. Write 'Revised homepage hero copy and two CTA variants per Tuesday feedback' rather than 'design work'.

Why are vague timesheet notes a problem?

Vague notes cost you money twice. Before invoicing you write hours down because a thin note feels indefensible, and after invoicing the client questions lines they cannot follow and you concede hours to keep the peace. Both are realization losses caused by a missing sentence.

How detailed should a timesheet note be?

Detailed enough that a stranger reading the invoice could picture the work, but no longer. Lead with a verb, name the deliverable, and add the reason for the duration only if it is not obvious. A short specific note beats a long padded one.

How do I write notes without wasting time?

Write the note the moment you stop the task, while the work is fresh, instead of reconstructing your week on Friday. A note written in the moment takes about ten seconds and is accurate, whereas a late one takes longer, reads vaguely, and is partly invented.

Do I need detailed notes on fixed-fee work?

Less so for the client, since they agreed an outcome and do not see your hours, but still enough for your own cost tracking. Match client-facing detail to how closely the line will be read, while keeping enough specificity that your own reports still show where time went.