BW-201b · Module 2

Status Reports That Do Not Get Ignored

4 min read

The status report is the most frequently written and least frequently read document in professional life. This is not coincidental. Most status reports are written by and for the writer — they document activity, demonstrate diligence, and create a record of effort. They are not written for the reader's needs. The reader needs to know two things: is the project on track, and do they need to do anything? A status report that does not answer both questions in the first paragraph has failed its core purpose.

The status report that gets read is the one that makes the executive's job easier. It tells them what they need to know quickly, flags what requires their attention specifically, and does not bury the problem in paragraph seven of a document they stopped reading at paragraph two.

Do This

  • Open with the overall status signal: on track, at risk, or delayed — one word or phrase
  • Follow with a single sentence on the most significant development since the last report
  • Flag any item requiring executive action explicitly — never bury it
  • Provide the detail in a structured section after the headline, for readers who need it

Avoid This

  • Open with a narrative of all activities completed since the last report
  • Bury the risk or problem in the middle of a paragraph after extensive context
  • Use identical language in consecutive reports — readers will stop reading if nothing changes
  • Write a status report without knowing what question the executive is trying to answer

The RAG system — Red, Amber, Green — is the most useful structural shorthand in status reporting. Every major workstream gets a color: Green (on track), Amber (at risk, monitor), Red (delayed or blocked, action required). The executive reads the RAG summary first. If everything is green, the report is informational. If anything is amber or red, the executive knows immediately where to focus. The narrative detail fills in the why and the what next.

The RAG system only works if the writer uses it honestly. A report where everything is perpetually green is a report the executive will stop trusting. When amber turns red without having been amber first, the executive is right to ask why they were not warned earlier. Status integrity — the willingness to report problems as problems when they are still amber — is the single most important quality in a status reporter.

One structural note: the status report should have a consistent format across every reporting cycle. Headers, sections, and the RAG summary should appear in the same place every time. Consistency allows the executive to scan quickly — they know where to look for the headline, where to find the actions required, and where the detail lives. Format variation forces the executive to orient from scratch each time. Orient them once, through consistent format, and then let the format become invisible.