RAG Status Reports Are Broken. Here's How to Fix Them.

The RAG Report That Means Nothing

Every week, in organisations across the country, project managers spend hours compiling RAG reports that nobody reads, presenting greens that aren't really green, and watching leadership teams make decisions based on information that bears little resemblance to what's actually happening on the ground.

RAG reporting — Red, Amber, Green status updates across schedule, budget, scope, and risk — is one of the most widely used project management tools in existence. It's also, in most implementations, almost completely useless. Not because the concept is wrong, but because of how it's almost universally applied.

This article explains why RAG reports so often fail to do their job, and what a genuinely useful status reporting framework looks like instead.

Why RAG Fails: The Seven Deadly Sins of Status Reporting

1. Green Until Catastrophe

The most pervasive failure mode: projects stay green until they suddenly turn red with no warning. This happens because project managers — especially in cultures with low psychological safety — are reluctant to flag amber or red status without certainty. By the time they're certain, it's too late to intervene effectively.

2. Subjective Ratings with No Anchors

What does amber actually mean? Without a shared definition, one PM's amber is another's red and a third's green. Ratings become a reflection of individual temperament and political awareness rather than objective project health.

3. RAG for Reporting, Not Decision-Making

Reports sent to a distribution list, filed in SharePoint, and never discussed are not governance tools. They're comfort blankets. Status reporting only has value if it's connected to a decision-making process — a standing agenda item where red and amber items are actively reviewed and resolved.

4. The Wrong Dimensions

Most RAG reports rate schedule, budget, and scope. These are lag indicators — they tell you what has already happened. A better framework includes lead indicators: team capacity, stakeholder engagement, dependency health, and upcoming risk triggers. By the time budget turns red, the problem started months ago.

5. No Trend Data

A single status rating tells you where a project is today. A trend tells you whether it's improving or deteriorating — which is what leadership actually needs to make decisions. Most RAG reports show no trend.

6. Narrative-Free Ratings

A red rating with no explanation of why it's red, what the impact is, and what action is required is worthless. Yet many status reports are nothing more than coloured cells in a spreadsheet.

7. No Accountability for Follow-Through

Issues raised in status reports frequently disappear into the void. Without a mechanism to track actions, decisions, and escalations from report to report, the same problems recur week after week.

A Better Approach: Reporting That Drives Action

The fix isn't to abandon RAG — it's to use it properly. Here's what a functioning status reporting framework looks like:

Define your RAG criteria explicitly

Write down, for each dimension (schedule, budget, scope, risk, stakeholder), exactly what constitutes red, amber, and green. Quantify where possible. "Amber on schedule = forecast to miss milestone by more than one week but less than three weeks." Remove the subjectivity.

Add a mandatory narrative field

Every amber or red rating must be accompanied by: the nature of the issue, the business impact if unresolved, and the proposed action (with owner and date). No narrative, no valid rating.

Include trend direction

Show whether each dimension has improved, stayed the same, or deteriorated since the last reporting period. A simple up/down/flat arrow next to the RAG colour transforms static data into a dynamic picture.

Connect reports to a governance meeting

Status reports should feed into a standing portfolio or programme review — ideally weekly or fortnightly — where amber and red items receive active discussion and action assignment. Reports without a connected governance cadence are paper exercises.

Track actions from report to report

Every action raised in a status review should be tracked to closure, with updates visible in the following report. This creates accountability and makes the status report a living management tool rather than a historical record.

The Cultural Piece

None of the above works if the organisational culture punishes honesty. If project managers know that reporting amber will result in blame rather than support, they'll keep reporting green until the wheels fall off. Leaders who want accurate project data need to actively demonstrate that early escalation is rewarded, not punished.

If your status reporting isn't giving you the visibility you need, it's worth examining both the mechanics and the culture. Our team works with SMEs to design reporting frameworks that actually function — as part of our Outsourced PMO and PMO Setup services. Get in touch to discuss your situation.