Write a client status update in five minutes, without a blank page

The monthly status update is nobody's favourite hour. Not because writing is hard, but because you're doing archaeology first: digging back through a month of email, half-remembered calls, and a notes app to reconstruct what actually happened before you can write a word about it.

The blank page is the tax. Here's how to stop paying it.

The problem is retrieval, not writing

By the time you sit down to write, the information exists — it's just scattered across your inbox, your calendar, and your memory. Most of the effort goes into gathering, not composing. Any approach that starts with a blank document has the order backwards.

Keep the record as you go, write from it at the end

The fix is to capture the moments as they happen — a two-line note after a call, a forwarded decision, a logged hour — into one place per client. Not a perfect journal; just the spine of what happened.

Then, when the update is due, you generate it from that record:

1. The draft pulls from the ledger — dates, decisions, commitments, open items.
2. Gaps show up as [TBC] so you know exactly what still needs a human answer, instead of quietly guessing.
3. You edit for tone and send. Five minutes, not an hour.

Why this beats pasting into ChatGPT

You could paste your notes into a general AI and ask for an update — and you'd get one. But you'd also get invented specifics wherever your notes were thin, in the same confident voice as the real parts, with no way to tell which is which. (More on that in our piece on why AI invents lies in client documents.)

Starting from a grounded record means the update is accountable: every line traces back to something that actually happened. That's the difference between a draft you skim nervously and one you send.