Keeping a work log: proving what you actually did

End of month. Your invoice is due. You know exactly what you did last week, roughly what you did the week before, and you have no precise idea what happened in the first fortnight.

So you round. Downward, nearly always — because billing for something you can't quite recall feels wrong. You've just given away several hours of real work, not out of generosity, but for lack of a record.

Three months later, the same client writes: "I assumed that was covered by the retainer." You're certain it wasn't. You have nothing to show for it.

Both situations have one cause. Knowledge work leaves no natural trace: once delivered, it becomes invisible — including to the person who did it.

What a work log is not

It isn't a professional diary. It's not there to record your mood, your motivation or your doubts.

It also isn't a decision log — the one that preserves what you knew at the moment of a judgement call. That's a useful object, but a different one, answering a different question.

A work log answers three factual questions and nothing else: what, for whom, when.

Its purpose isn't reflection. It's evidence.

Why time tracking doesn't cover it

The obvious objection: there are dozens of time trackers, and plenty of people bill straight off the clock.

They fail for two reasons.

They measure duration, not substance. "3h15 — Martin project" tells you nothing three months later. The number can't be disputed, but it can't be defended either: facing a client who questions a line item, a total of hours isn't an argument. What was produced is.

They have to be started at the right moment. A timer wants to be running before the task and stopped after it. Real work gets interrupted, resumed, derailed by an unplanned call. It takes about two weeks for a forgotten timer to become an abandoned one.

A work log is filled in afterwards, once the thing is finished and known. That's the only writing position that survives a disorderly week.

One line per unit of delivered work

The format is a single line, written when something is done:

9 September — Martin — pricing page redesign delivered, 3 variants. Sign-off expected Friday.

Four elements: the date, the client, what was produced, and where it now stands.

What earns a line: a deliverable, a meeting, a decision taken with the client, a request that arrived outside the agreed scope. What doesn't: "worked on the project." If the line doesn't say what exists now that didn't exist this morning, it will never be useful.

Two minutes at the end of the day is enough. The survival rule is the same as for any personal system: it has to cost less than it returns, starting in week one. A work log demanding fifteen minutes a day will be abandoned before it has paid for itself once.

What it makes possible

Billing for what you actually did. You re-read thirty dated lines instead of interrogating your memory. The downward rounding stops — not through commercial firmness, but because the uncertainty that caused it is gone.

Answering a dispute with facts. "On 12 August you asked to add the English version; it's in my log, outside the original scope." The tone stays calm because nothing rests on one person's recollection against another's.

Seeing scope creep while it's happening. This is the least expected benefit and probably the most valuable. No out-of-scope request is unreasonable on its own — it's the accumulation that is, and it stays invisible as long as the requests sit scattered across email threads. Lined up in a log, seven small requests over six weeks become self-evident. You no longer have to decide whether you're overreacting: you can read it.

Writing your reviews instead of reconstructing them. An end-of-engagement report, a quarterly check-in, a proposal for the next client: all need the same raw material, and it's already there.

In Keepsake, a dated entry attached to a contact or a project page does exactly this — the trail accumulates day by day and reads back per client or per engagement.

The cost of not keeping one

It shows up on no statement, which is precisely the problem. It shows up as hours rounded down because you weren't sure. As requests accepted one at a time because each looked small. As end-of-engagement weeks spent rebuilding what you did instead of lining up what comes next.

It isn't your memory failing. It's that unwritten work never existed in anyone's eyes, including your own.

One line per deliverable, dated, attached to a client. That's the whole system — and it's the only document that speaks for you once you can no longer remember.