Status Reports Executives Actually Read: What Good Looks Like vs What Bad Looks Like
Project status reports have a reputation problem. Programme managers spend hours producing them. Executives spend seconds glancing at them before setting them aside. The problem is not usually that executives are too busy — it is that most status reports are structured for the people who write them, not the people who need to act on them. A good status report answers the questions an executive is actually asking: Is this on track? What do I need to decide or approve? What will stop us if we do not act? A bad status report answers questions no executive asked and buries the answers to the ones they did. The contrast below makes the distinction concrete.
What Good Looks Like
Leads with the summary decision or action needed, not a project history. The very first sentence or table answers: is this on track, off track, or at risk? If the executive reads nothing else, they know the most important thing.
Uses a consistent RAG (Red / Amber / Green) status with a clear definition. Red means action is needed now. Amber means there is a developing risk that requires attention. Green means on track. The definitions are set once and applied consistently — they do not change based on political pressure.
Flags risks before they become issues. A good status report surfaces emerging risks with a probability and impact assessment and proposes mitigation actions. It does not wait until the risk has become a problem to mention it.
Compares to the original baseline, not just to last period. "We completed 12 tasks this week" is meaningless without context. "We are three days behind the baseline schedule due to a delayed vendor approval, and we plan to recover through parallel testing in week 14" gives an executive what they need.
Fits on one page or one screen. Executives do not have time to read four-page reports. If your report requires four pages to convey its essential content, the essential content has not been identified.
What Bad Looks Like
Opens with project background that was relevant at kickoff six months ago and has not changed since. The executive already knows why the project exists.
Lists 20 activities completed this week with no indication of whether any of them matter to the schedule, budget, or scope. Outputs are not outcomes. A list of completed tasks is a timesheet, not a status report.
Buries problems in passive voice and optimistic framing. "Some challenges were encountered with the vendor delivery schedule that the team is working to address" means the vendor is late and the team does not have a plan yet. Say that.
Has no clear "so what." A status report that delivers information without a recommended action, a decision needed, or a risk to watch puts the cognitive burden entirely on the executive to figure out what to do with it.
Changes format from week to week, making trends impossible to track. Consistent format over time means the executive can spot a change from last week's status at a glance. Format instability means they start from scratch every time.
One Test to Apply Before You Send
Hand your draft status report to someone who has not worked on the project. Ask them two questions: What is the most important thing happening with this project right now? What, if anything, do they need to do about it? If they cannot answer both questions within 60 seconds, the report needs to be rewritten. A status report that requires context to interpret has failed at its primary job.
XNM helps public-sector and capital-project teams build effective programme and project delivery practices, including governance, reporting, and stakeholder communication frameworks. Reach out to XNM's program & project delivery advisory team to strengthen how your projects communicate upward.