Write a client update before they have to ask

Clients often ask for updates because they cannot see the work happening between milestones. A short, predictable message can reduce that uncertainty without turning every week into a presentation. The useful question is not ‘What have we been busy doing?’ but ‘What does the client need to understand or decide now?’

Lead with the current position

Open with the state of the agreed deliverable. If it remains on schedule, say what that means in concrete terms. If a date is at risk, put that near the beginning. Do not bury a dependency below a cheerful account of completed tasks. A client should not have to infer the project status from your tone.

For a hypothetical website project, an opening could read: ‘The service-page draft is ready for your review. The design work can start as planned once you confirm the two pricing examples by Tuesday.’ This separates completed work from the condition attached to the next stage. It is more informative than ‘Everything is progressing well’.

Report movement, not an activity diary

Describe what changed since the last update. A reviewed outline, a resolved question or a tested draft is a change the reader can understand. ‘Several internal meetings’ says little unless those meetings produced a relevant decision. Keep supporting detail in the project record and link to it when the client may need to inspect it.

Then name the next visible output. Explain what the client will receive and whether it is for information, comment or approval. Those are different requests. An early draft sent for discussion should not unexpectedly become the version treated as approved because the recipient did not reply.

If you need a response, make the request easy to isolate. State the question, the available options and the effect of waiting. Avoid making the client reconstruct the request from several paragraphs. Where there are multiple questions, group those requiring the same decision-maker rather than scattering them through the email.

Keep problems proportionate and specific

A useful risk note describes the issue, its likely effect and the current response. ‘We are waiting for the image files; this may move the design review by two days’ is a bounded statement. Do not call every unfinished task a risk, and do not present an unconfirmed recovery plan as a promise. If the impact is still being assessed, say when you will provide a firmer view.

Agree a cadence suited to the project. A weekly update may work for a multi-week assignment; a short, fast-moving engagement may need updates around decisions instead. Consistency matters more than a particular weekday. Send a brief note even when the honest update is that a dependency remains unresolved, but add the action being taken rather than repeating last week's wording.

Finally, read the message from the client's side. Can they identify what is complete, what happens next and what you need from them? If those answers are clear, the update is doing its job. It does not need an elaborate dashboard to prove that work is happening.