What decision-grade executive reporting looks like

Most status reports describe. Decision-grade reports decide.

There is a category of status report that is comprehensive, accurate, and largely useless for executive decision-making. It describes what happened last week. It lists the activities completed. It notes that several meetings took place. It mentions that a risk was discussed. It does not make clear what action — if any — is required from the reader.

Decision-grade reporting is different. It is structured around the question: what does this senior stakeholder need to know and do as a result of reading this report? If the answer is nothing, the report has not earned its audience's time.

The four elements of decision-grade reporting

1. A clear RAG status with meaning

RAG status — Red, Amber, Green — is only useful if the criteria are defined and consistently applied. A report where Green means "broadly fine from where I'm sitting" and Amber means "I wanted to flag this but didn't want to go Red" is not a control tool. It is a comfort signal.

Decision-grade reporting defines what each RAG status means in this delivery context. What threshold triggers an Amber? What is the escalation expectation when something goes Red? The criteria should be agreed with senior stakeholders at the start of the programme, not invented retrospectively to justify the current status.

2. Risks that require action

A risk section that lists every risk in the RAID log is not decision-grade. Most risks at any given point do not require executive attention. What decision-grade reporting surfaces is the subset of risks that are above escalation threshold, have changed status since the last report, or require a decision or resource from the reader.

The framing matters too. "Supplier X has not committed to a date for the network upgrade" is more actionable than "Risk R12 — supplier dependency — probability Medium, impact High." Senior stakeholders respond to plain language, not risk matrices.

3. Decisions needed

This is the section most often missing from status reports. If a senior stakeholder reads a report and does not know whether they need to make a decision, approve something, or escalate something, the report has failed its primary function.

A decision-grade report makes this explicit: "The following decisions are required before [date]." It names the decision, the options if relevant, and the consequence of not deciding. This is uncomfortable to write — it requires the PM to be explicit about what they need from senior stakeholders — but it is exactly what makes reporting useful.

4. A reliable forward look

Decision-grade reporting is as much about what is coming as what has happened. A forward look section — covering the next two to four weeks — should identify upcoming milestones, known risks that are approaching their trigger dates, decisions that will be required, and any dependencies that are currently unresolved.

The forward look is where senior stakeholders can intervene before problems become crises. A report that only describes the past leaves no room for proactive governance.

What decision-grade reporting is not

It is not long. A well-structured decision-grade report should be readable in full in five minutes. If it takes longer, it is not structured correctly. Length is not a proxy for quality in executive reporting.

It is not always comfortable to write. Being explicit about risks, decisions needed, and forward problems requires the PM to be honest with senior stakeholders. Reports that soften every message are not decision-grade — they are relationship management.

It is not the same format for every audience. A report for a programme board has different requirements from one for a steering group or an IT director. The underlying discipline is the same; the format should be calibrated to the audience.

The test

A simple test for whether a report is decision-grade: read only the executive summary and the decisions-needed section. If a senior stakeholder could make every required decision without reading the rest of the report, the structure is correct. If the decisions cannot be found without reading the full document, the report is not yet decision-grade.