How to Write a Weekly Status Report a Client Actually Reads
A status report is not a record of activity. It is a request for the client to do something, wrapped in enough context to make the request reasonable.
Most weekly status reports are written for the author. They list what the team did, in the order it was done, at a level of detail that proves effort. A sponsor scans the first paragraph, sees nothing that requires them, and stops. The report has cost an hour to write and has changed nothing.
The reports that work are written for the reader's decision. They answer, in order: is this on track, what do you need from me, what has changed since last week, and what should worry you. Everything else is an appendix.
The four things that must appear
- A single status, stated plainly, with the reason if it is anything other than on track. A colour with no sentence behind it is decoration, and a status that has been amber for six weeks is a status nobody is acting on.
- What is needed from the client, each item with an owner by name and a date. This is the part that produces action, and it belongs above the fold rather than at the end.
- What changed since the last report: milestones that moved, decisions taken, scope accepted, assumptions that turned out to be wrong.
- The next two weeks, at milestone level. Not a task list, but what will be true when the next two reports are written.
The three that never should
A status report is not a place to raise something for the first time. A risk that appears in writing without having been said out loud reads as a defensive filing, and it damages the relationship precisely when the relationship is needed. Raise it in the conversation and then record it.
It is also not the place for internal detail: who was on holiday, which internal review is outstanding, how many hours were charged. And it is not the place for a hedge. A sentence that could be read two ways will be read the way that suits the reader, and the misunderstanding will surface at the worst moment.
The escalation ladder that makes status mean something
Status is only useful if there is a defined consequence attached to each level. Agree at the start of the engagement what happens at each one, and write it into the governance schedule.
A workable ladder is that green requires nothing, amber requires a named recovery action with a date and a named owner, and red requires a meeting within a stated number of working days at a level above the engagement. Once that ladder exists, nobody argues about whether the status is amber for political reasons. They argue about whether the recovery action is right, which is the useful argument.
Writing it in fifteen minutes
Status reporting becomes expensive when it is composed from scratch each week. It should instead be assembled from records that already exist: the plan supplies the milestone dates, the change log supplies what was accepted, the risk register supplies what is being watched, and the information request list supplies what is outstanding with the client.
If those records are maintained as the work happens, the report is a summary and takes fifteen minutes. If they are not, the report becomes the only place the information exists, which is why it takes two hours and why it is always slightly out of date.
A short template
- Status, one line, with the reason if not green.
- Needed from you: up to five items, each with an owner and a date.
- Changed this week: decisions, movements, accepted changes.
- Next two weeks: milestone level only.
- Watching: the two or three risks with the highest exposure, each with the action being taken.
- Commercials: position against fee or budget, in the terms the fee model requires.