RAG Status

RAG status, named for its three colors of red, amber and green, is one of the most common ways to summarize progress in project and portfolio reporting. Green means things are going to plan. Amber means there are problems or risks that need attention but can likely be managed. Red means there are serious problems that need intervention, often from senior leaders. Because the colors are widely understood, RAG reports can be read by executives with little explanation. The ratings can apply to a project as a whole or to individual dimensions such as schedule, budget, scope, risk and benefits.

The appeal of RAG status is its simplicity. A portfolio of a hundred projects can be scanned in seconds, and attention can go straight to the reds and ambers. That simplicity is also its weakness: ratings can be subjective, and project managers may be reluctant to report amber or red. For portfolio leaders and PMOs, RAG status works best when it is based on clear, agreed criteria and backed by data.

Definition of RAG Status

RAG status is a traffic-light rating system used in project, program and portfolio reporting, where red indicates critical problems requiring intervention, amber indicates problems or risks requiring attention and green indicates performance in line with plan.

Some organizations add a fourth status, such as blue for completed work or grey for work not yet started. RAG ratings are often displayed on a portfolio dashboard and are commonly informed by the project's RAID log.

Typical Meaning of Each Status

Green means the project is on track against its schedule, budget and scope, with no significant risks or issues beyond the team's control.

Amber means there are issues or risks that could affect delivery, but a recovery plan exists and the team expects to manage them, possibly with some support.

Red means the project is significantly off track, or faces issues the team cannot resolve, and needs decisions or intervention from the sponsor or senior leaders.

Some organizations also report the direction of travel, such as improving or worsening, alongside the color.

Dimensions Commonly Rated

Schedule compares progress with planned milestones and dates. It usually looks at both milestones already missed and the forecast for those still ahead.

Budget compares actual and forecast spending with the approved budget. Forecasts matter more than spending to date, since they show where the project is heading.

Scope and quality assess whether the project is delivering what was agreed to the required standard.

Risks, issues and resources assess whether threats are under control and the right people are available.

Benefits assess whether the project remains on course to deliver its expected value. An overall rating usually combines these, often using the worst individual rating or an agreed rule.

Importance of RAG Status in Strategic Portfolio Management

RAG status focuses attention. Leaders reviewing a large portfolio can see quickly where problems lie and spend their time on the projects that need it.

It creates a common language. When all projects use the same ratings and definitions, status can be compared across the portfolio.

It also supports escalation. A clear rule that red projects are reviewed by a steering committee or portfolio board makes sure serious problems reach decision makers.

RAG Status and Financial Management

Budget ratings flag projects at risk of overspending, giving finance teams an early signal to review forecasts and contingency.

Linking budget ratings to measurable thresholds, such as a forecast overrun of more than 5% for amber and 10% for red, makes them objective and comparable.

Measures from earned value management, such as the cost performance index, can be used to set budget ratings on larger projects.

Tracking how often projects move from green to red without passing through amber can reveal reporting problems that hide financial risk until it is too late.

Common Challenges

Optimism bias leads project managers to report green or amber when the situation is worse, a pattern sometimes called watermelon reporting, green on the outside and red on the inside.

Without clear definitions, different project managers interpret the colors differently, which makes comparison unreliable.

Some organizations treat a red rating as a failure of the project manager, which discourages honest reporting. Red should be seen as a request for help. Leaders set the tone through how they respond the first time a project reports red.