Programme Status Reporting: How to Make RAG Status Actually Honest

## The short answer

Good programme reporting exists to **drive decisions, not to reassure**. The most common failure is the "watermelon" report — green on the outside, red on the inside — where status reflects optimism rather than evidence. To fix it, tie each RAG rating to objective, agreed criteria; report the *trend* and the *decisions needed*, not just the colour; and make it psychologically safe to report red early. A report that never goes amber until the milestone slips is not a report, it's a liability.

## What reporting is for

Reporting has one job: give decision-makers an accurate enough picture, soon enough, to act. Everything else — the formatting, the cadence, the tooling — serves that goal. If your reports look impressive but the board is consistently surprised by bad news, your reporting is failing at its only real purpose.

## Why RAG status goes wrong

Red-Amber-Green is useful because it's instantly readable. It's dangerous because it's subjective. Left undefined, "green" means whatever the person filling it in wants it to mean — and human nature, plus the wish to avoid a difficult conversation, pulls that meaning toward optimism. The result is the watermelon: a column of green that turns red overnight when reality can no longer be hidden.

The deeper problem is cultural. If reporting amber triggers an inquisition while reporting green is rewarded with being left alone, you've trained everyone to report green. The status system then actively destroys the information it was built to surface.

## Define what each colour means

The single most effective fix is to make RAG ratings objective. Agree, in advance, what each colour signifies — for example:

- **Green** — on track to meet committed scope, date and budget with no intervention needed.

- **Amber** — at risk; a credible threat to a commitment that requires attention or a decision.

- **Red** — a commitment will be missed without intervention, or has already been.

Then anchor the rating to evidence: actuals against plan, milestones hit or missed, burn rate, open critical risks. When status is tied to facts rather than feeling, the colour becomes much harder to fudge and much more useful to read.

## Report trend and trajectory, not just a snapshot

A single colour is a point in time; decisions need direction. Always show movement:

- Was this amber last period too? (A persistent amber is worse than a fresh one.)

- Is the forecast completion date moving earlier or later each report?

- Is the risk profile growing or shrinking?

A green that has been quietly drifting toward its deadline for three reports deserves more scrutiny than a red that's already being actively recovered. Trend reveals the trajectory that a snapshot hides.

## Lead with decisions needed

The most valuable part of any programme report is the section most reports bury or omit: **what decisions does the board need to make, by when?** Status that doesn't lead to a decision is just noise. Structure your report so a busy sponsor can, in two minutes, see:

1. Overall health and trend.

2. The two or three things genuinely at risk.

3. The specific decisions or support required, with deadlines.

If a board meeting ends with information shared but nothing decided, the report has wasted everyone's time.

## Build a culture where red is safe

No reporting format survives a culture that punishes honesty. To get truthful status:

- Treat early red as good management, not failure. The person who flags a problem in month two is helping you; the one who hides it until month six is the problem.

- Separate the message from the messenger. Interrogate the situation, not the person.

- Reward accuracy over optimism. A forecaster who is reliably right is worth more than one who is reliably cheerful.

The goal is a programme where bad news travels *faster* than good news, because bad news is where the decisions are.

## Warning signs

- Status is green until a milestone is missed, then jumps straight to red.

- Reports are long on narrative and short on decisions needed.

- RAG ratings have no defined criteria.

- The board is regularly surprised.

- People privately admit the real status differs from the reported one.

At neart.ai we build enterprise-grade PMO tooling, and the pattern we see most often is reporting effort spent on presentation rather than truth. Tying status to objective data and surfacing trend and decisions — rather than a hand-picked colour — is what turns reporting from theatre into a control system.

## Practical takeaway

Define what red, amber and green actually mean, anchor each rating to evidence, and always show trend alongside the snapshot. Lead every report with the decisions the board must make and by when — and above all, build a culture where reporting a problem early is rewarded, not punished. Honest amber today beats surprise red at the milestone.