Client status reports nobody dreads writing

Status reports fail in two directions. Either they're a three-page document that takes someone ninety minutes to assemble and the client skims for four seconds, or they're a two-line email that says "all good, more next week" and provides no record of anything.

The version that works is short, structured identically every time, and written in ten minutes. The structure matters more than the length, because a report with the same six blocks every week trains the client where to look — and trains you to notice when a block is empty for the wrong reasons.

The format

[PROJECT NAME] — Status, week ending [DATE]

STATUS: On track / At risk / Off track
[One sentence. If not "on track", the sentence says why.]

DONE THIS WEEK
- [Item, phrased as an outcome, not an activity]
- [Item]
- [Item]

NEXT WEEK
- [Item] — [owner]
- [Item] — [owner]

WE NEED FROM YOU
- [Thing] — needed by [date] — [what happens if it's late]
- [Thing] — needed by [date] — [what happens if it's late]
(If nothing: "Nothing this week.")

BUDGET AND TIMELINE
Budget: [X] of [Y] hours used ([Z]%)
Progress: roughly [W]% complete
Key dates: [milestone] — [date] — [on track / moved from (old date)]

CHANGES AND RISKS
- [Anything agreed this week that differs from the original scope]
- [Anything that could go wrong, and what you're doing about it]
(If nothing: "No changes to scope this week.")

That's it. Same order, same headings, every single time. A client who receives this for eight weeks learns to scroll straight to "we need from you," which is exactly the behaviour you want.

Why each block earns its place

Status in one word. Clients want the answer before the detail. Burying "we've slipped a week" in paragraph four reads as concealment even when it isn't. Say the word first.

Use only three states, and mean them. At risk means something will go wrong if nothing changes. Off track means something has already gone wrong. If you've been "on track" for nine weeks and then deliver late, you have destroyed more trust than the delay itself ever would have.

Done this week, as outcomes. "Worked on the homepage" tells the client nothing. "Homepage layout finished and ready for your review" tells them what changed in the world. The difference takes no extra time and it's the difference between a report that justifies an invoice and one that reads like a timesheet.

Next week, with owners. Names, including client-side names. A line that reads "Brand guidelines sign-off — Priya (your side)" is a commitment that has been made in writing without anyone having to be awkward about it.

We need from you. This is the block that saves projects, and it's the one most agencies leave out because it feels like nagging.

It isn't nagging if it carries a consequence. Compare:

Please send the product photos when you can.

with:

Product photos — needed by Thursday 14th. If they land after Thursday, the gallery build moves into the following week and the launch date moves with it.

The second version isn't more aggressive, it's more informative. Clients generally aren't ignoring you out of malice; they don't know which of your requests is load-bearing. Tell them.

Budget and timeline as numbers. This is the block that prevents the ugliest conversation in agency work — the one where the client is surprised by an overrun. If a project has used 248 of 400 hours, say "248 of 400 hours used (62%), roughly 55% complete." A client who sees that gap in week five is a client who can make a decision about scope. A client who sees it in week ten is a client who feels ambushed.

Nobody enjoys writing that line when the numbers are unflattering. Write it anyway. The unflattering number in week five is a discussion; in week ten it's a credit note.

Changes and risks. Every "sure, we can add that" from a call gets written down here in one sentence. Not to be difficult — because six weeks later, when the budget is tight, this list is the only record of why. It also converts scope creep from an argument about memory into a review of a written log, which is a much calmer conversation.

Rules that keep it fast

Cap it at one screen. If it doesn't fit on a phone screen without pinching, cut it. Detail lives in the deliverables, not the report.

Send it at the same time every week. Friday afternoon or Monday morning, pick one, never vary. Predictability is what stops clients from sending "any update?" emails, which is most of the value.

Write it as you go. Keep a running note through the week and drop lines in when they happen. Assembling a report from memory on Friday takes an hour and gets details wrong. Adding four lines across five days takes ten minutes total.

Don't write it for a client who doesn't want one. Some clients genuinely prefer a five-minute call. Fine — but still write the record for yourself, and still send the budget and timeline block in writing. The call is for them; the written trail is for you.

What to do when the status is bad

The temptation is to soften it: "minor delays," "slightly behind," "some challenges." Clients read hedged language as a warning sign and start asking harder questions than the situation warrants.

Be plain about what happened, and lead with the recovery:

STATUS: At risk — the photography shoot moved by a week, which puts the gallery build into week 8.

To hold the launch date we can either run the gallery build in parallel with copy review, or launch with placeholder images and swap them the following week. We recommend the first. Can you confirm by Wednesday?

That's still bad news. It reads as competence rather than crisis, because it comes with two options and a date.

Do this week

Take the template above, fill it in for your largest active project, and send it. Don't announce a new process or ask permission — just send one.

The block that will be hardest to fill in is budget and timeline, and the difficulty is the finding. If you can't say what percentage of the budget a project has used without half a day of digging, that's the actual problem, and the status report is just the thing that made it visible.