The decision
What is needed, from whom, by when, with the options and their consequences. This goes at the top because it is the purpose of the report. If nothing needs deciding, one sentence says so — and the report may be short.
Control & Reporting
Status reports that trigger decisions instead of colouring traffic lights.
A report that triggers no decision has no purpose. It costs the time of those who write it and of those who read it.
TopicReporting and governance
Reading timeapprox. 6 minutes
For whomProgram leadership, PMO, steering committee
Last updatedJuly 2026
In brief
Four questions, one page, named addressees.
An effective status report answers four questions: What has changed since the last report? What is at risk as a result? Which decision is needed now, by whom, by when? And what happens if that decision is not taken?
Everything else — progress bars, traffic lights, effort figures — is evidence, not message. Evidence belongs in the appendix. If the four questions do not fit on one page, it is not the page that is too small but the statement that is not finished.
Why traffic lights decide nothing.
Traffic lights are popular because they reduce complexity to a colour. That is precisely their problem: they convey a judgement without the information that led to it. An amber field does not tell a board what to do. It only says that someone is worried.
On top of that comes a social mechanic that renders every traffic-light landscape useless over time. Reporting red has consequences: follow-up questions, attention, occasionally blame. Amber has hardly any consequences. So amber is reported until it can no longer be sustained — and the jump from amber to red then happens at a point when room for manoeuvre is gone. Anyone who sees many weeks of amber and then suddenly red is not seeing a risk but a reporting system.
The solution is not to ban traffic lights. It is to tie the colour to a statement: every deviation from green needs one sentence stating which decision or which support would resolve it. That turns a mood into a task.
How to build a page that actually gets read.
Order by benefit to the reader, not by how things arose in the project.
The change
What has changed since the last report? Only changes, no repetition of what is already known. A report that consists eighty per cent of the previous one stops being read after two editions.
The exposure
What is put at risk by this change — deadline, scope, cost, quality? Including the point from which the exposure can no longer be averted. That deadline is the most important figure in the report.
The evidence
Progress, metrics, test results, effort. Important for traceability, unsuitable as an opening. Whoever puts the evidence first loses attention before the message.
Wording risks so that someone acts.
Most risk wordings in project reports are useless because they describe states instead of effects. "Resource bottleneck in team B" is not a risk but an observation. A risk that triggers action contains five elements:
- Trigger. What would have to occur? Observable, not assumed.
- Effect. What consequence would that have, expressed in deadline, scope, cost or quality — not in "delays".
- Deadline. By when is it still avoidable? Without this, every risk is equally urgent and therefore none is.
- Owner. Who owns the mitigation, by name.
- Need. What does this owner need that they cannot provide themselves? That is precisely the board's job.
- Cross-check: if a reader cannot say what to do after reading the risk, it is not yet a report but a worry.
Different readers, different reports.
A common mistake is trying to serve everyone with one document. A steering committee, a program leadership and a delivery team need different information, and merging them means none of the three finds what they need.
What works in practice is three levels from one source. For the steering committee: decisions and exposures, one page, monthly or as occasion demands. For program leadership: dependencies, progress per sub-area, open points, weekly. For the teams: the working board they use anyway, daily.
What matters is that the upper levels arise out of the lower one and not alongside it. If a report is produced in addition to the work, it drifts away from reality — and in a particular direction: it becomes more optimistic.
Four mistakes that make a report ineffective.
Report without an addressee
If it is not clear who reads this report and what they are meant to do with it, it is written for everyone and useful to no one. Every report needs a named addressee and a purpose.
Past instead of outlook
Reports that mainly list what has been completed create satisfaction without any steering effect. The valuable part lies ahead of the reporting date, not behind it.
Smoothing on the way up
Every reporting level that summarises statements has an incentive to phrase them more mildly. Across three levels a hard problem becomes an observation. Remedy: pass figures and deadlines through unchanged, and mark assessment separately.
No follow-up on decisions
If a report asks for decisions but nowhere records which were taken and which remained open, the format loses its effect. A short list of open decisions with dates is enough — its mere existence creates movement.
Do you report a lot and decide little?
Describe your committee structure and today's reporting route to me. You will get an assessment of which level needs which report — and which one can be dropped.
Discuss your project