# Beyond Traffic Lights: Why RAG Status Reporting Is Failing Your PMO (And What to Replace It With) **Category:** PMO **Author:** AI Assistant **Published:** 2026-05-11 **Read Time:** 9 min read ## Summary RAG traffic light reporting gives PMOs a false sense of control. Learn why UK organisations are moving beyond red-amber-green to outcome-based, risk-linked portfolio dashboards that tell the truth. ## Full Content # Beyond Traffic Lights: Why RAG Status Reporting Is Failing Your PMO (And What to Replace It With) ## What Is RAG Status Reporting? RAG status reporting is a project management method that assigns a Red, Amber, or Green traffic light to indicate project health. Green means on track. Amber means at risk or slightly off plan. Red means in trouble, off track, or requiring escalation. It is the most widely used status reporting format in UK PMOs and programme management offices. The appeal is simplicity. A board member, steering committee chair, or portfolio sponsor can glance at a RAG dashboard and understand the health of ten, fifty, or a hundred projects in seconds. That simplicity is also its fatal flaw. ## The Problem with Traffic Lights RAG reporting is not wrong. It is incomplete. And in the hands of most PMOs, it is actively misleading. Here is what the research and operational reality tell us: ### 1. RAG Is Subjective Without strictly defined tolerance thresholds, project managers assign RAG based on personal judgement. One project manager flags a two-week delay as Red. Another calls the same delay Amber. A third, who is optimistic or politically motivated, calls it Green with a note about "mitigation actions in progress." PMMajik's PMO research documented this directly: organisations without enforced tolerance definitions routinely see identical project situations reported as different RAG statuses by different project managers. The result is a portfolio dashboard where Green does not mean the same thing twice. ### 2. Amber Is Meaningless There is an active debate in the project management community about whether Amber should exist at all. The argument, raised on ProjectManagement.com in 2025, is that Amber is the "comfortable middle" where projects sit indefinitely without escalation or resolution. A project moves from Green to Amber. The steering committee notes it. No action is taken because Amber means "being managed." The project stays Amber for three months. Then it moves to Red. The steering committee is surprised. They should not be. Amber was a warning that became wallpaper. ### 3. RAG Hides Root Causes A traffic light tells you a project is struggling. It does not tell you why. Is it a resource constraint? A vendor failure? A scope change that invalidated the business case? A dependency on another project that is also Amber? The project manager knows. The steering committee might learn, if they read the commentary. The portfolio board, reviewing thirty projects in an hour, sees the colour and moves on. The root cause goes unaddressed until it produces consequences that are impossible to ignore. ### 4. RAG Does Not Compound Perhaps the most dangerous limitation: RAG does not aggregate meaningfully. If ten projects are Amber, is the portfolio Amber? What if three of those projects contribute to the same strategic outcome? What if two of them share a risk that, if realised, would turn both Red simultaneously? RAG treats every project as independent. Portfolios are not independent. They are interconnected systems of dependencies, shared risks, and competing resource demands. A dashboard of individual traffic lights is not a portfolio view. It is a collection of isolated signals with no context. ## What "Beyond Traffic Lights" Looks Like Moving beyond RAG does not mean abandoning visual status indicators. It means embedding them in a richer information architecture that provides context, connections, and actionable intelligence. ### Replace Subjective RAG with Calculated Health Scores Instead of asking project managers to choose a colour, calculate project health from objective data: - **Schedule health**: Percentage of milestones on track vs. at risk vs. missed. Derived from the plan, not from opinion. - **Budget health**: Actual spend vs. forecast, with burn rate trending. Calculated from financial data, not from a project manager's estimate. - **Risk health**: Count and severity of open risks, weighted by proximity and impact. Pulled from the risk register, not from a summary. - **Outcome health**: Progress against defined business outcomes, not just deliverables. Tracked from the business case, not from task completion. The colour can still exist. But it is calculated, not chosen. And anyone who wants to understand why a project is Amber can drill into the component scores. ### Connect Projects to Shared Risks and Dependencies A portfolio view should show: - Which projects share risks (e.g., same vendor, same technology, same regulatory deadline) - Which projects contribute to the same business outcome - Which projects compete for the same resources - What the compound effect of simultaneous Amber statuses is This is not possible in a flat RAG dashboard. It requires a system where projects, risks, and outcomes are linked, not listed. ### Track Trends, Not Snapshots A project that has been Green for six months and just turned Amber is a different situation from a project that has been Amber for six months. A project that moved from Red to Amber is improving. A project that moved from Green to Amber to Green to Amber is oscillating, which usually indicates a deeper systemic issue. Trend data is more valuable than current status. A portfolio dashboard should show status history, trajectory, and momentum, not just today's colour. ### Link Status to Action Every status indicator should connect to an action. If a project is Amber, what is the prescribed response? Who is responsible? What is the deadline for resolution? If no action is prescribed, the Amber status is informational, which means it is decorative. An operationally useful dashboard does not just show status. It shows the next step. It triggers workflows. It assigns accountability. ## The UK Context: Why This Matters for Your Organisation UK organisations face specific challenges that make RAG limitations more acute: - **Regulatory project overload**: GDPR, Cyber Essentials, Modern Slavery Act, ECCTA, Provision 29. Compliance projects are crowding portfolios, and they have binary outcomes: compliant or not compliant. Amber does not exist in a regulatory deadline. You either meet it or you face consequences. - **Public sector scrutiny**: UK government and NHS portfolios are under intense scrutiny following high-profile programme failures. The National Audit Office consistently identifies poor portfolio visibility as a contributing factor. RAG dashboards that show green while outcomes fail are a recurring finding. - **Board expectations under the UK Corporate Governance Code**: Boards are expected to demonstrate effective oversight of risk and delivery. A RAG dashboard presented to the board without context, trends, or risk linkage does not meet this expectation. It is a comfort blanket, not a governance tool. - **Scaling organisations**: Mid-market UK organisations moving from ten projects to fifty cannot scale RAG reporting. The subjectivity problem multiplies. The lack of context compounds. The board meeting that reviewed ten RAG statuses in five minutes cannot review fifty in the same format. ## How Simplif-i Goes Beyond Traffic Lights Simplif-i's PMO module is designed for organisations that need portfolio visibility, not just project status reporting. **Calculated, not chosen:** - Project health is derived from plan data, financial data, and risk data - Status indicators are computed from objective metrics, not manual selection - Drill-down from any status to the underlying data is built in **Connected, not listed:** - Projects link to shared risks in the enterprise risk register - Projects link to business outcomes defined at approval - Dependencies between projects are mapped and visualised - Resource conflicts are identified at the portfolio level **Trending, not snapshot:** - Status history is tracked automatically - Portfolio dashboards show trajectory and momentum - Oscillating statuses are flagged as systemic issues **Integrated with GRC:** - Compliance project status is linked to the compliance framework - Regulatory deadlines are visible in the portfolio view alongside project milestones - Risk exposure from project delivery is visible in the board's risk report - Provision 29 evidence includes project governance data **Pricing:** - PMO module: £49/month standalone - Full platform (the "COO in a Box"): £499/month, or £149/month founding member pricing - 7-day free trial, full access, no credit card required ## The COO Perspective: Status Reporting as a Scaling Constraint Here is the operational reality. RAG status reporting was designed for a world where a senior leader could hold the entire portfolio in their head. Ten projects. Monthly reviews. Personal relationships with every project manager. That world does not exist in a scaling organisation. When you have fifty projects across five functions, managed by twenty project managers with different standards, reported to a portfolio board that meets for ninety minutes, RAG is not a communication tool. It is a compression algorithm that discards most of the information your leaders need to make decisions. The organisations that scale their delivery capability are the ones that replace subjective reporting with calculated health, connect projects to outcomes and risks, and give their leaders a portfolio view that tells the truth. Not the version of the truth that fits into three colours. The version that shows which investments are producing results, which are at risk, and what to do about it. That is beyond traffic lights. That is operational intelligence. ## Frequently Asked Questions **What is RAG status reporting?** RAG (Red, Amber, Green) status reporting is a project management method that assigns traffic light colours to indicate project health. Green means on track, Amber means at risk, and Red means in trouble. It is the most common status reporting format in UK PMOs but has well-documented limitations around subjectivity, oversimplification, and lack of context. **Why is RAG status reporting unreliable?** RAG is unreliable because it depends on subjective assessment. Without defined tolerance thresholds, different project managers assign different colours to identical situations. Amber status often becomes a permanent holding state that delays escalation. RAG does not show root causes, trends, dependencies, or compound risk across the portfolio. **What should replace RAG status in a PMO?** Calculated health scores derived from objective data (schedule, budget, risk, outcome metrics), connected portfolio views showing dependencies and shared risks, trend analysis showing status history and trajectory, and action-linked dashboards that prescribe responses to each status level. **How does Simplif-i handle project status reporting?** Simplif-i computes project health from plan data, financial data, and risk register data rather than relying on manual RAG selection. Projects are connected to shared risks, business outcomes, and compliance requirements. The portfolio dashboard shows calculated health, trends, and drill-down to underlying data. **Is RAG status reporting still used in UK government projects?** Yes. RAG remains standard in UK government and public sector portfolios. However, the National Audit Office has repeatedly identified poor portfolio visibility as a factor in programme failures. Organisations are increasingly supplementing RAG with earned value management, trend analysis, and outcome-based reporting. **What is the difference between project status and portfolio health?** Project status is the health of an individual project. Portfolio health is the aggregate health of all projects, accounting for dependencies, shared risks, resource conflicts, and contribution to strategic outcomes. A portfolio can be unhealthy even when most individual projects report Green. --- Source: https://simplif-i.com/api/blog/readable/pmo/beyond-traffic-lights-rag-status-pmo Web Version: https://simplif-i.com/blog/pmo/beyond-traffic-lights-rag-status-pmo © Simplif-i - Unified Business Management Platform