The status report nobody reads
If your weekly update is a list of what happened, you have written a diary, not a status report. Here is what stakeholders actually need in it.
If your weekly update is a list of what happened, you have written a diary. Diaries are for the writer. Status reports are for the reader, and the reader has three questions.
The three questions
Are we going to hit the date? Not "are we busy". Not "did we close eleven tickets". Whether the commitment still holds, and if it does not, by how much it has moved.
What do you need from me? Every stakeholder is scanning for the sentence that requires them to act. Bury it in paragraph four and it will not happen.
What changed since last time? They read last week's update. Repeating it wastes the only attention you get.
Everything else — velocity, tickets closed, meetings held — is evidence you may need in order to support an answer. It is not the answer.
The RAG trap
Most organisations run a red / amber / green status. Most project managers avoid red until it is undeniable, because red triggers attention and attention feels like criticism.
This is exactly backwards. Red early is cheap: people can reallocate, renegotiate scope, or move a dependency. Red late is expensive, and it damages your credibility permanently, because everyone can see the problem did not appear on the day you finally reported it.
A useful rule: if you would be uncomfortable being asked "when did you first know?", the status is already wrong.
Amber deserves a definition too. It should mean there is a specific risk, with a named owner and a date by which it must resolve, not I feel uneasy. If you cannot write that sentence, the status is green.
A structure that works
Five parts, in this order, no longer than one screen:
- Status and date. One line. Red, amber or green, the target date, and whether it moved.
- What changed. Three bullets at most. Only genuine deltas.
- Decisions or help needed. Named person, specific ask, deadline. If there are none, write "none this week" — that is information too.
- Risks worth your attention. Two or three, each with what you are doing about it. Not the whole register.
- Detail. Everything else, below the fold, for whoever wants it.
If a reader stops after part one, they should still have the most important thing.
Cadence and audience
One report rarely serves everyone. An engineering lead and a managing director need different altitudes, and writing a single document for both produces something too vague for one and too granular for the other.
The efficient compromise is a single source of facts with two framings: the detailed version the delivery team maintains, and a short executive version derived from it. That derivation should take ten minutes, not an afternoon. If it takes longer, the underlying tracking is not structured well enough.
The test
Send the report. If nobody responds, that is not a sign everything is fine. It is a sign nobody read it.
A good status report generates replies: a question, a decision, an offer of help. Silence, week after week, means you have been writing a diary.