A good status update serves two purposes: it tells the client what’s happening with their project, and it gives them confidence that you’re on top of it. Most status updates fail on both counts — they’re either too detailed to be read, or too vague to be reassuring. Here’s a format that works.
Keep it short
A status update that requires ten minutes to read will not be read carefully. Aim for five to eight bullet points or a short paragraph. If there’s more to say, put the essential information at the top and the detail below a “More detail” heading that they can read if they want to.
Cover three things
What’s been done: the progress since the last update. Be specific — “completed the stakeholder interview report” is more useful than “making good progress”.
What’s next: what you’re working on now and what’s coming up this week. This helps the client track progress without having to ask.
What you need from them: any decisions, approvals, or information required from the client side. Make these explicit — “I need your feedback on the draft by Wednesday to stay on schedule” is more effective than “please review when you have a moment”.
Flag any risks
If something is at risk — a deadline that might slip, a dependency that hasn’t come in — say so briefly and clearly. Clients who are kept informed of risks early can usually help resolve them. Clients who find out at the last minute cannot.
The status report template below gives you a reusable format for weekly project updates that covers progress, next steps, and client actions in a consistent, readable structure.