The project that looked fine in status reports and wasn't
Published 29 October 2026
For eleven weeks the report said green. Every Friday the same four rows went to the client: design on track, build on track, content on track, launch date holding. In week twelve the launch moved by six weeks.
The client couldn't understand how a project that had been green all along was suddenly that far behind. They were right to be confused. The project hadn't gone wrong in week twelve. It had been going wrong since week four. The report just never said so.
This is an anonymised version of a project I was brought in to recover. The details are changed, but the pattern is common enough that most agency PMs will recognise some of it.
What the report showed
A product launch across four markets: a microsite, campaign assets, CRM journeys and one global launch date. The weekly status report was a tidy one page summary with a RAG status for each workstream and a short comment underneath.
Every workstream was green. The comments were variations on "progressing well" and "on track for launch". Nobody on the client side had any reason to ask a hard question.
What was actually happening
When I sat down with the team leads, a different picture came out in about an hour.
What the report said
What the team knew
Same project, same week. Week four.
None of this was hidden. Every item was known to at least one person on the project. It simply never made it onto the report.
Why the report stayed green
It wasn't dishonesty. It was mostly mechanics.
Green meant nobody had said otherwise. The PM set the status from conversations, not evidence. If no team lead raised a flag, the row stayed green by default.
The report measured activity, not progress. "Build progressing well" was true. Code was being written. It said nothing about whether the right code would be finished by the date.
Dependencies weren't on the report at all. The things most likely to move the date, legal review and the client's data feed, sat outside the agency's control. So they weren't anyone's row.
Amber felt like an admission. Several people said later they'd thought about flagging amber and decided to wait a week and see. Wait a week eleven times and you get week twelve.
What would have caught it in week four
Four changes, none of them complicated.
1. Agree what each colour means before the first report. Write the definitions at the top of the report so the team and the client read the same scale.
2. Report against milestones, not workstreams. "Market three copy approved by 14 March: legal review not booked" is much harder to dress up than "Content: on track".
3. Put dependencies on the report. Anything the plan needs from someone outside the team gets its own line, an owner and a date. If it has no date, that is its status.
4. Make amber safe. Thank people for raising it early. An amber in week four with a recovery plan is a good week. A red in week twelve is a bad quarter.
For the first change, this is the scale I now put at the top of every report:
| Status | What it means | What the client needs to do |
|---|---|---|
| Green | On track against the plan, and we can show why | Nothing |
| Amber | At risk, with a recovery plan the team owns | Be aware, no decision yet |
| Red | Will miss a date, budget or scope commitment without a change | Make a decision by a named date |
Check your own report this week
Take your latest status report and ask three questions.
- For each green, what is the evidence? If the answer is "nobody told me otherwise", it isn't green yet.
- Which dates on the plan depend on someone outside your team? Are they on the report?
- When did this project last show amber? If the answer is never, that is worth a conversation.
If the report and the project disagree, the report is the problem. Fixing it in week four costs far less than explaining it in week twelve.
A status report isn't a record of how the project feels. For the client, it is the project.
A weekly delivery review built around evidence, plus the escalation route that gets an amber in front of the right person while there is still time to act on it. Founding members get it free.
10 templates live · lifetime access · 14 day refund