Skip to content
Search Kaul Advisors
Toolkit 3 min read

The one-page program status executives actually read

A status report is a decision aid, not a diary. A simple one-page structure that respects senior attention and surfaces what needs to change.

SK

Sunny Kaul

Principal Advisor, Kaul Advisors

A team collaborating around a table with laptops and notes

Most programme status reports are written for the programme, not for the reader. They document activity, list workstream updates, and arrive as a pack that takes twenty minutes to understand. By then, the meeting has already started.

A one-page status report is not a summary of everything. It is a selection of what a senior reader needs in order to make a decision.

Start with the outcome, not the activity

The first line should answer a simple question: are we still on track to deliver the intended outcome? Not “are people busy?” and not “how many tasks are complete?” — the outcome the programme exists to produce.

A useful opening statement is specific:

“The programme remains on track for the October pilot. Two decisions are needed this week: approval of the localisation scope for Wave 2, and confirmation of the data remediation owner.”

That tells the reader where they are and what is required. Everything else on the page supports it.

Use four sections

We keep the structure deliberately small:

  1. Outcome and date. The current position against the next meaningful milestone.
  2. Decisions required. Each with an owner, a deadline, and the consequence of delay.
  3. What changed. Risks, issues, or dependencies that moved since the last report.
  4. Next milestone. What must be true, and when it will be assessed.

Anything that does not fit one of these sections belongs in an appendix or a separate conversation.

Make red, amber, and green mean something

RAG status is useful only when the definitions are agreed and stable. If red means “the programme lead is worried” in one report and “a milestone has been missed” in another, the reader learns to ignore it.

We define status against explicit criteria. For example:

  • Green: the milestone is expected to be met; no decisions are needed beyond the agreed plan.
  • Amber: the milestone is at risk; a recovery action is in place and requires attention or a decision.
  • Red: the milestone will not be met without a change to scope, sequence, resource, or senior intervention.

The definition should be visible in the report, at least as a footnote. Consistency builds trust faster than optimistic reporting.

A status report earns its place when a reader can finish it in two minutes and know exactly what they are being asked to do.

Write the decision, not the background

Senior readers do not need the full history of a design debate to make a decision. They need the options, the recommendation, the trade-off, and the consequence of not deciding.

For each decision required, provide:

  • the question, in one sentence
  • the options considered
  • the recommended option
  • the impact of delay
  • the decision owner and date

If the programme cannot state the decision this clearly, the issue is not the report. It is that the decision has not been prepared.

Keep the format stable

A status report is a rhythm, not a creative exercise. Keeping the format stable lets readers notice change. It also reduces the effort required to produce it, which makes it more likely to be produced well.

We recommend a single page, the same sections each period, and a short appendix for detail. The discipline is in what gets left out.

A short test

Before sending, ask:

  • Could a reader understand the position in under two minutes?
  • Is every decision clearly stated with an owner and a date?
  • Does the report distinguish between activity and progress?
  • Would anything here surprise the reader because it was not raised earlier?

If the last answer is yes, pick up the phone before sending the report. A status report should not be the first place a serious issue appears.

Topics ReportingGovernanceToolkit