The Project Status Report Clients Actually Read

Every other document on a project is written once. The status report is written every week, which changes what it is for. Its job is not to look good this week. Its job is to make the next surprise smaller.

Judged that way, most status reports fail in the same specific manner: green, green, green, green, red. The trust does not die at the red. It dies at the transition, because the four greens turn out to have been a reporting habit rather than a report.

Six sections, and the order is the point

Status in one line, with a direction. Not just “on track” — on track and better, the same, or worse than the last report. A single status word hides the trend, and the trend is the only part with predictive value.

Decisions I need from you, each with a date. Second, not last. This is the section that makes a client open next week’s report, because it is the only one addressed to them.

What was completed since the last report. Past tense, verifiable, and linked to something they can look at.

What is next and by when. Short. Three items. A list of twelve is a list of nothing.

Risks, each with an owner and a response. A risk with no named owner is a complaint.

Budget and time used against planned. Two numbers. The client will read this one whether you put it in or not.

Putting the asks second is the change that does the most work. A report that opens with an account of your week is a report about you; a report that opens with what is now blocked on the client is a report they cannot ignore without consequence.

Say what is done, not what percentage is done

Percentages on a project of this size are invented. Everybody knows they are invented, which is why nobody trusts them, which is why they get inflated, which is why the last 10% takes as long as the first 90%.

Replace the number with a state:

The design is accepted. The build has not started.

Three of the five templates are built and reviewed; two are not started.

The integration works in testing. It has not been tried against live data.

Each of those is checkable by the client, which is the property a percentage does not have. If you must report a proportion, count something real — deliverables accepted out of deliverables agreed — and say what you counted.

Escalate early, in small amounts

The reason status reports drift to permanent green is that raising a problem feels like admitting one. So raise it in a smaller unit than a problem.

A risk section is exactly the device for this: it lets you name something that has not gone wrong yet, at a moment when it costs nothing, and it gives you a written history showing you named it. The report that says “if the content does not arrive by the 14th, launch moves to the following week” in week two is the report that makes week six a scheduling conversation instead of a fight.

One rule: never let a risk appear for the first time as a problem. If a red item was not amber in an earlier report, the reporting failed, not just the project.

What to cut

Activity logs. “Attended three meetings, responded to emails” is a timesheet, and no client has ever been reassured by one.

Anything that repeats last week unchanged. If an item has not moved in three reports, either it is not real work or it is blocked — say which.

Internal vocabulary. Sprint names, ticket numbers and tool-specific jargon push the reader out of a document you need them inside.

Apology. One sentence of explanation for a slip is professional. Three is a document about your feelings.

Cadence beats depth

The same day, the same shape, the same length, every time. A report that arrives on Friday at four is a report a client learns to look for. A brilliant report that arrives when there is news is one they never build a habit around, and habitual reading is the entire mechanism by which a status report reduces surprise.

Short is what makes weekly sustainable. If you cannot write it in twenty minutes you will eventually stop writing it, and the version you stop writing is always the long one.

The signal from a recurring document is different

A one-off document is read or not read. A weekly series produces a pattern instead, and the pattern is more useful than any single reading.

Never opened, week after week. This is a fact about your channel or your cadence, not about the client’s interest — and it is worth acting on, because it means every risk you have “raised” was raised to nobody. What an unopened document actually means applies here more than anywhere.

Read the moment it arrives, every week. You have a client who is paying attention. Keep the length where it is and put your best sentence at the top.

One report read three times when the others were read once. Something in that one worried somebody. It is usually the budget line or a risk. That is a phone call, not an email — and not a phone call in which you mention that you saw them read it.

Two practical notes. Sending each report as a link rather than an attachment means the series lives in one place and stays current, and Quixli can bundle a run of documents into a single collection with a table of contents so a client arriving in month four can find month one. And an alert when a report is opened arrives quickly enough to be useful the same afternoon — the notification behaviour, including the daily digest is described on the features page.