← Insights

Projects

The one-page status report sponsors actually read

July 2026 · 6 min read

The status report is the most-produced and least-read document in project work. A sponsor gets six of them before lunch, gives each about fifteen seconds, and is looking for exactly one thing: is this project fine, wobbling, or on fire? Everything you put on the page is either serving that fifteen-second read or getting in its way.

The tool most people reach for is the RAG rating - red, amber, green. It is the right tool, and it is almost always used wrongly, in two specific ways that quietly destroy its value.

What red, amber and green should mean

A RAG rating is a decision, not a mood. Anchor each colour to an action the reader should take:

• Green - no help needed. On plan, or off plan with a credible recovery already in hand. Read and move on.
• Amber - attention needed. There is a problem the team is working, but it may need a decision, a trade-off or air cover soon. Not a crisis; a heads-up.
• Red - help needed now. A committed date, cost or scope will be missed without intervention. The reason you called the meeting.

Rated against actions, the colours become useful. Rated against feelings, everything drifts to a comfortable amber-green and the report says nothing. The discipline is to make green mean "you can genuinely ignore this" - which takes nerve, because it means owning the greens.

Rate the components, then derive the overall

Here is the failure that undoes most reports. Someone types an overall green at the top of the page, and three lines down the budget line is red and the schedule is amber. The headline and the detail disagree, the reader notices, and now they trust neither.

The fix is to stop authoring the overall rating at all. Rate the components a project is actually made of - Scope, Schedule, Budget, Risk, Resources - and let the overall be derived as the worst of them. If Budget is red, the project is red, full stop. A single red component cannot hide behind four greens, because the headline is a formula reading the lights below it, not an optimistic human summarising them.

This one change does more for a report's credibility than any amount of prose. The sponsor learns that your green means green, because they can see it could not have been fudged.

Fit it on one page

If it runs to two pages, the second one does not exist as far as a busy reader is concerned. A genuine one-pager holds only what serves the fifteen-second read plus the follow-up questions:

• The overall RAG and the five component lights, up top.
• The two or three top risks and issues - the amber and red story, in a line each.
• The key milestones and their dates, so "when" is answered.
• What got done this period and what the next period targets.

No project history, no meeting minutes, no paragraph where a sentence would do. The report is a dashboard, not a diary.

Report in the tool the room expects

A quiet friction point: the report often lives in a spreadsheet, but the steering pack is a slide deck, so someone screenshots a workbook into a slide and it looks exactly as bolted-on as it is. Keep the live report in Excel, where the RAG logic runs, and keep a matching one-page slide for the deck - the same status, presented natively in whichever tool the audience is reading. Report in their format, not the one you happen to be working in.

A status report works when the overall colour is derived from the parts, fits on one page, and means the same thing every week - so the sponsor can trust a green enough to leave you alone.

That last part is the real prize. The point of a good status report is not to be read closely; it is to earn the greens that let a sponsor not read closely - and to make the reds impossible to miss when they matter.