TL;DR
RAG status (Red, Amber, Green) is the most widely used project health signal in enterprise portfolios. It is also one of the most inconsistently applied. Without a defined, enforced standard for what each colour means, RAG becomes a subjective judgment that varies by PM, by project type, and by how close the next steering committee is. The fix is a structured RAG definition framework applied consistently across every project in the portfolio and enforced as a governance control, not a self-assessment.
Every portfolio dashboard has them. Green circles. Amber triangles. Red squares. Arranged neatly across a grid of programs and projects, giving the impression of a governed, visible, well-understood portfolio. Then someone asks a simple question in the steering committee: “What does green actually mean on Project C?”
- The PM says: on track for the milestone.
- The PMO Director says: within budget tolerance.
- The Sponsor says: No escalated risks.
- The CFO says: delivering against the approved business case.
They are all describing different things. And all of them are technically correct, because nobody ever defined what green means.
That is the RAG status problem in enterprise project portfolios. It is not a data problem. It is a definition problem.
Why RAG Status Fails as a Governance Signal
RAG status was designed to give busy executives a fast, reliable signal about project health. In principle, it is an excellent idea. In practice, it has three structural failure modes that undermine its value.
1: No shared definition
In most organizations, RAG status is self-assessed by the PM who owns the project. Green means the PM believes the project is healthy. Amber means the PM is concerned. Red means the PM is willing to flag a problem publicly, which, given organizational dynamics, happens far less often than the data would warrant.
Without a defined standard specifying exactly what triggers each colour, two PMs managing projects with identical risk profiles will report different RAG statuses based on personal judgment, risk tolerance, and political context.
2: Status optimism bias
When RAG is self-reported and tied to perception of PM performance, the incentive structure pushes toward green. A PM who reports red is inviting scrutiny. A PM who reports green, even when amber is more accurate, defers that scrutiny to the next review cycle.
This is not dishonesty. It is a rational response to an ambiguous system with no enforcement mechanism.
3: Temporal drift
Even when a RAG definition exists, it often reflects the project’s status at a specific point in time rather than its trajectory. A project can be green today, on milestone and on budget, while trending toward amber or red based on resource pressure, dependency risk, or scope changes that have not yet materialized in the numbers.
A status colour that reflects where a project is, rather than where it is heading, is a lagging indicator masquerading as a leading one.
A RAG status without a definition is not a governance signal. It is a mood indicator with a colour scheme.
“The ultimate purpose of collecting the data is to provide a basis for action or a recommendation.”
What Each Colour Should Actually Mean
The fix is not a new tool. It is a defined standard applied to every project in the portfolio, without exception, and enforced as a governance control rather than a self-assessment.
Here is what a structured RAG definition framework looks like across four assessment dimensions:
| Assessment Dimension | GREEN | AMBER | RED |
|---|---|---|---|
| Schedule | Milestone delivery within 5% of planned timeline | 6–15% behind planned timeline, recovery plan in place | 15%+ behind planned timeline or no credible recovery plan |
| Budget | Spend within 5% of approved forecast | 6–15% variance, documented and approved | 15%+ variance or unapproved overrun requiring escalation |
| Risk | No open risks above Medium rating | One or more High risks open, mitigation active | One or more Critical risks open or mitigation not yet defined |
| Dependency | All dependencies on track or resolved | One dependency at risk, contingency identified | One or more dependencies failed, downstream impact confirmed |
Portfolio RAG is the most conservative dimension that applies.
This is the rule that most organizations miss. If a project is Green on schedule, Green on budget, Green on risk, but Amber on a dependency, the portfolio status is Amber. The most conservative signal governs. Not an average. Not a majority. This single rule eliminates the most common form of status gaming: a PM who buries a dependency risk in a footnote while reporting overall green.
The Trajectory Rule: Where Is This Project Heading?
A static RAG status tells you where a project is. A trajectory indicator tells you where it is going. Good portfolio governance requires both.
When you combine status with trajectory, the signal becomes far more actionable:
Key Insight
A green and deteriorating project often deserves more attention than an amber and improving one, and this is exactly what traditional dashboards fail to show.
This combination changes how leaders prioritize attention. A green but deteriorating project often deserves more focus than an amber but improving one. Without trajectory indicators, that distinction is invisible on the dashboard.
The Governance Rules That Make RAG Credible
A RAG definition framework only works if it is enforced. Three governance rules convert RAG from a self-assessment into a governance instrument.
1: RAG is calculated, not declared
Status colours should be generated automatically by the system based on actual project data, including schedule variance, budget variance, open risk ratings, and dependency status. Manual entry by the PM should be avoided. Where it is unavoidable, the system must require the PM to select a reason code that aligns with the defined threshold criteria.
2: Amber requires a recovery plan. Red requires an escalation
A project cannot remain Amber for more than one review cycle without a documented recovery plan attached to the project record. Similarly, a project cannot be Red without triggering an automatic escalation notification to the PMO Director and Sponsor. These are governance rules enforced by workflow, not optional recommendations.
3: The PMO audits RAG accuracy quarterly
Once per quarter, the PMO Director reviews a sample of Green projects against objective schedule, budget, and risk data. Projects where the objective data would generate a different RAG status than reported are flagged, and the PM must reconcile the difference. This is not punitive. It is the audit function that makes the entire RAG system credible and trustworthy.
Before and After: What Credible RAG Status Looks Like
- Project 10% behind schedule: Without a standard, the PM reports Green and notes, “We’ll catch up in the next sprint.” With defined thresholds, the system calculates Amber and requires a recovery plan within five days.
- Critical dependency delayed: Without a standard, the PM reports Green and mentions the dependency in notes. With thresholds, the portfolio automatically shows Amber, surfacing the dependency risk to the PMO.
- Budget 8% over forecast: Without a standard, the PM reports Green, claiming “within contingency.” With thresholds, the system calculates Amber and requires documented approval.
- Open critical risk with no mitigation: Without a standard, the PM reports Amber, saying, “We’re monitoring it.” With thresholds, the system calculates Red and triggers automatic escalation to the Sponsor.
- Project Green but slipping week on week: Without a standard, there is no signal; status remains Green. With thresholds, a trajectory indicator shows Green but deteriorating, flagging the need for early attention.
This shift is not about introducing pessimism into portfolio reporting. It is about replacing subjective optimism with objective thresholds so that Green always means the same thing, regardless of which PM reports it.
See Portfolio-Wide RAG Governance in Action
Quick Audit: Is Your RAG Status Trustworthy?
| # | Question | Yes | No / Partial |
|---|---|---|---|
| 1 | Does your organization have a written definition of what triggers Green, Amber, and Red — for each assessment dimension? | ||
| 2 | Is RAG status calculated from objective project data, not self-assessed by the PM? | ||
| 3 | Does a single Amber dimension — even if all others are Green — trigger an Amber portfolio status? | ||
| 4 | Does an Amber status automatically require a documented recovery plan within a defined window? | ||
| 5 | Does your portfolio dashboard include trajectory indicators — not just static status colours? |
Three or more “No / Partial” answers mean your RAG status is a mood indicator, not a governance signal. The colours look like data.
RAG status (Red, Amber, Green) is a traffic-light system used to communicate project health across schedule, budget, risk, and dependency dimensions. It is designed to provide executive stakeholders with a fast, reliable signal on portfolio health. Without defined thresholds for each colour, however, it becomes a subjective self-assessment that varies by PM and consistently overstates project health due to optimism bias and political incentives
Because it is self-reported without defined thresholds. When each PM decides what green means based on personal judgment, two projects with identical risk profiles can report different colours. The result is a portfolio dashboard that looks consistent and isn’t, and executive decisions are made on the basis of status colours that mean different things from project to project.
Amber should be triggered by any of the following: schedule variance of 6–15% against the planned timeline with a recovery plan in place, budget variance of 6–15% with documentation, one or more High-rated risks open with active mitigation, or one dependency at risk with a contingency identified. The most conservative dimension governs; if any one dimension is Amber, the project status is Amber regardless of the others.
A trajectory indicator shows the direction a project is heading, improving, stable, or deteriorating alongside its current RAG status. A green project that is deteriorating week on week deserves more attention than an amber project that is recovering. Without trajectory indicators, static status colours hide that distinction and give executives a false sense of stability in projects that are quietly heading toward escalation
Quarterly RAG audits compare self-reported status colours against objective project data, schedule variance calculations, budget variance reports, open risk ratings. Projects where the objective data would generate a different status than the one reported are flagged for reconciliation. The audit function is what makes RAG trustworthy without it, the definition framework exists but is not enforced.
