How to write client status updates that arrive before the question
Clients rarely chase work. They chase uncertainty. The “just checking in” email does not usually mean the project is late; it means the client has gone a week without knowing where it stands, and the not-knowing has started to cost more than the waiting. A status update removes the uncertainty before it forms: five lines, the same shape every time, sent on a predictable rhythm whether or not there is news. It costs about ten minutes a week, and it is the cheapest trust a freelancer can buy — the client who always knows never has to wonder, never has to escalate, and never quietly starts doubting the invoice when it lands. This guide covers the five lines, the rhythm that makes them work, and the traps that turn a good habit into noise.
1. The shape: five lines, always the same five
Every update carries the same five lines, in the same order, every week. The fixed shape is the point: the client learns where to look, you never face a blank page wondering what to include, and a missing line is itself information — an update with no waiting-on line says nobody owes you anything.
Done, since last time. Past tense, concrete, countable. “Homepage draft 2 finished” is a fact a client can hold; “made good progress” is a mood. Name the artefact and its state — drafted, built, sent, approved — and if something was delivered, say where it lives. This is the line clients read first, and the evidence the rest of the project stands on.
Next, before the next update. One or two items, no more. This is a plan, not a wish list: the things you will genuinely touch before the next update lands. A next line with six items is a hope, and the client can tell. Keep it to what the week honestly holds, and let next week’s done line be those same items, finished.
Waiting on. The inputs you need from the client, stated neutrally, each with the date it was asked. This is the discipline of the guide to projects that stall on the client, in miniature: a missing input named in week one is a line in an email, while the same input discovered in week five is a blown deadline with an argument attached. Neutral is the whole tone — “the product photos, asked Tuesday” is a fact, not a nudge with elbows.
The date. When the next milestone lands, and whether it has moved. A date that moves is not the disaster; a date that moves silently is. Announced in the week it slips, with the plan that absorbs it, a moved date reads as management. Announced at the deadline itself, the same move reads as an excuse — the facts are identical, and only the timing of the telling differs.
One question, maximum. Updates that end with three questions get answered never: the client means to reply properly, later, and later is where questions go to be forgotten. If the update needs an answer, it carries exactly one, and an easy one. Anything that needs a real decision gets its own message, where it can be the subject line instead of a burial in line five.
Here is a complete one, for a fictional bakery website — subject line, labels and all, it runs to 85 words:
That is the whole artefact. It took longer to read this section than it takes to write the update — which is the demonstration. Brevity is not the update being lazy; it is the update being finished. A client can absorb it in twenty seconds and know exactly where their project stands.
The fixed shape has one more virtue: it survives a change of reader. When your client forwards the thread to their boss, their partner or their eventual replacement, a stranger can read three updates in a row and reconstruct the project — which is precisely what happens the first time anyone senior asks where things stand.
2. The rhythm: same day, same thread, five minutes
Send it on the same day, at roughly the same time, every week the project is active. Friday late morning is the classic slot, but the day matters less than the predictability: an update that arrives like a train teaches the client that silence between updates means work, not trouble. And send it whether or not there is news. “No change this week — the shop still lands on the 13th” is a complete, professional update. The only failed update is the one that does not arrive, because its absence is the one message a client cannot interpret kindly.
Send it where the client already lives — for most, one email thread whose subject line never changes. The thread becomes the running record of the project: every update, every date, every waiting-on item in one searchable place, the same filing discipline the call-notes guide applies to decisions. If the client lives in a project tool or a chat channel instead, the update lives there. The rule is one home, always the same one — never scattered across three apps by mood.
Hold the length law: if an update takes longer than five minutes to write, it has stopped being an update and become a report. Reports are a different artefact — sometimes worth doing, occasionally worth billing for — with their own place in your documented processes. The five-minute ceiling is what keeps the habit alive for a whole project. A ritual that costs an hour a week dies by week three, and it dies silently.
If a week does slip — it will, eventually — do not write a double update to catch up. Send the normal five lines, a week late, with the rhythm simply resumed. The catch-up edition, with its apology and its backlog, teaches the client that the rhythm is negotiable. The ordinary one teaches them it is not.
3. What the update prevents
The status meeting. Every project without updates eventually grows a recurring call whose only real agenda is “where are we?” Run our meeting cost calculator on one such call — 45 minutes, plus 15 minutes of prep and follow-up, at the calculator’s own $95 default rate — and it prices your seat alone at $95 a week: one hour, every week, 48 hours and $4,560 across a working year, spent reporting on work instead of doing it. The five-line update replaces that call. The meetings that remain can then be about decisions, which is what they were for.
The surprise invoice. An invoice that arrives after three silent weeks is a revelation, and revelations get questioned. The same invoice at the end of a run of updates is a summary of things the client watched happen — the done lines were its covering letter, already read. How to send an invoice covers the mechanics; the update trail is what makes the amount feel inevitable rather than sudden.
The stall that festers, and the scramble at the end. The waiting-on line surfaces a missing input in the week it goes missing, while it is still cheap to chase. And when the project closes, the update archive is the handover document’s first draft — the done lines, dates and decisions already written, in order, needing tidying rather than archaeology. The habit you kept for the client’s peace of mind pays you back at the exact moment projects usually get messy.
4. Tone and traps
Write for the busiest reader. The update is designed to be skimmed in twenty seconds: same shape, same order, facts at the front. If a line needs a second read, it is carrying something it should not — a justification, a history, a worry — and that thing belongs in a conversation or a message of its own, not compressed into a status line.
Never bury a problem. A real problem — a missed dependency, a defect, a date in danger — gets its own message the day it is known, in full. The update may reference it (“the date below reflects the issue in Tuesday’s email”), but a cheerful update with bad news folded into line four teaches the client to distrust the other four lines. The update’s credibility is the asset; spend nothing that devalues it.
No performative detail. File names, tool names, an afternoon wrestled with a plugin — this is effort theatre, and clients can smell it. Outcomes and dates only: what exists now that did not exist last week, and when the next thing lands. The update is not a timesheet either; unless the client is buying hours, it never itemises your time, or you will train them to audit your week instead of watching their project move.
Do not apologise in updates. “Sorry, short one this week” apologises for the design working. Facts carry their own tone: a two-line update in a quiet week is not a failure of effort, it is the rhythm holding. The clients who forward your updates to a partner or a boss — and they do — need them boring, regular and true, not warm and apologetic.
5. Starting mid-project, and keeping it alive
Most projects that need updates do not have them yet, so start where you are. The first update explains itself in one line — “Starting a short Friday update so you always know where things stand; the first one is below” — and then simply takes the shape in section 1. No announcement campaign, no apology for the previous silence. Clients do not grade the weeks before the habit started. They notice, within a fortnight, that they have stopped wondering.
With several clients, batch it: every update written in one sitting, on the same morning, one after another — the Friday close-out in the guide to managing multiple clients is exactly where the habit belongs. The shape is the template. After two clients it lives in your fingers rather than in a document, which is why it survives the busy weeks that kill grander systems.
Stop at the handover. The final update doubles as the closing summary — everything done, nothing waiting, the date met — and hands over to the handover document itself. Then the thread closes. A rhythm that ends cleanly is one the client remembers as part of how the whole project felt: predictable from the first week to the last.
Questions
Related: the record, running both ways
Call notes record what the client decided; the status update reports what you did about it — the same discipline pointed the other way. The stalls guide is what happens when a waiting-on line goes unanswered for weeks. And the wrap-up email is this habit’s final form: the last update, sent with delivery, closing the record the weekly ones built.