Most executives measure project health with a single color. Green means fine, yellow means watch it, red means intervene. It's fast to read, which is exactly why it's still everywhere. It's also a compression of a lot of information into one of three values, self-reported by the same team being measured, and it reflects a single point in time rather than a trend. The ten metrics below are what a red, yellow, or green status is usually standing in for, and tracking them directly gives an executive a sharper, earlier picture than the color alone ever will.
For a breakdown of how these numbers should be organized once you're tracking them, see our companion article on what belongs inside an executive project risk report.
In This Article
- Why RAG status alone isn't enough
- 10 metrics that actually measure project health
- An illustrative scorecard example
- Why this matters at the executive level
- Common mistakes in tracking project health
- A quick-reference tracking checklist
- Frequently Asked Questions
Why RAG status alone isn't enough
Red, amber, green (RAG) status reporting is a useful communication shorthand, not a measurement system. It's used widely across risk tracking, milestone tracking, and budget reporting because it's easy to scan.1 The trouble is what it hides: two projects can both report "yellow" for entirely different reasons and with very different urgency, and the label alone doesn't tell an executive which one needs attention first. A frequently cited critique of RAG reporting is that it represents a point-in-time snapshot rather than a trend, and that when amber becomes the default middle answer, leaders lose the signal entirely.2 The color is a summary. The metrics below are what it's supposed to be summarizing.
10 metrics that actually measure project health
1. Schedule Performance Index (SPI)
The ratio of earned value to planned value. A reading of 1.0 means the project is exactly on schedule; below 1.0 means it's falling behind. What matters most is the trend across several reporting periods, not any single reading.3
2. Cost Performance Index (CPI)
The ratio of earned value to actual cost. A CPI below 1.0 means the project is spending more than the value of the work completed so far, an early signal of budget trouble that shows up well before a formal overrun.3
3. Schedule Variance (SV)
The dollar or hour difference between earned value and planned value. Where SPI shows the rate of drift, SV shows its size, useful when comparing the scale of delay across projects of different budgets.
4. Cost Variance (CV) / budget variance
The dollar difference between earned value and actual cost. Tracked alongside percent-complete, this shows whether spend is outpacing progress well before a monthly budget close would catch it.
5. Milestone hit-rate trend
Not just whether the next milestone was hit, but the trend across the last several: are milestones increasingly landing late, on time, or early? A single missed milestone is information. A pattern is a signal.
6. Resource utilization rate
Whether the people assigned to the project are allocated at a sustainable, accurate rate, or quietly over-committed across multiple initiatives. Over-utilization is one of the more common precursors to schedule slip, and it's usually visible in a resourcing tool well before it shows up as a missed deadline.4
7. Scope change frequency
The rate of formal change requests, and separately, the rate of informal scope conversations that never become formal requests. A rising trend in either is a leading indicator of budget and schedule risk, even when each individual change looks small.
8. Open high-severity risk count and age
Not the total number of risks logged, but how many are high-severity and how long they've been open without a mitigation update. A risk that's been open and unaddressed for months carries different weight than one flagged last week.
9. Vendor and dependency responsiveness
How quickly external vendors or cross-team dependencies are closing out open items, tracked as a trend. A vendor whose response time is quietly lengthening is a leading indicator of a future delay, even when no milestone has technically slipped yet.
10. Benefits realization trend
Whether the project, if delivered exactly as currently scoped, is still on track to produce the business value it was originally approved for. A project can be on schedule and on budget while the business case behind it has quietly eroded, which is a different kind of health problem than a missed deadline.
Common mistakes in tracking project health
- Relying on RAG status as the only signal. A color is a summary, not a measurement; two "yellow" projects can carry very different levels of urgency.
- Tracking a snapshot instead of a trend. A single SPI or CPI reading tells you less than the same metric across three or four consecutive periods.
- Treating all ten metrics as equally important on every project. Smaller or lower-risk projects may only need three or four tracked closely; forcing a full scorecard on every project can create noise instead of clarity.
- Reviewing metrics only at the same cadence as formal status reports. If the underlying data changes daily but review happens monthly, drift accumulates for weeks before anyone looks.
- Counting total risks instead of high-severity, aging risks. A long risk log with nothing addressed for months is a worse sign than a short one that's actively being worked.
A quick-reference tracking checklist
- ☐ SPI and CPI reviewed as a trend across multiple periods, not a single reading
- ☐ Schedule Variance and Cost Variance tracked alongside percent-complete
- ☐ Milestone hit-rate trend reviewed, not just the most recent milestone
- ☐ Resource utilization checked for over-commitment before it becomes a missed deadline
- ☐ Scope change frequency tracked, including informal conversations that never became formal requests
- ☐ High-severity risks reviewed by age, not just by count
- ☐ Vendor and dependency response times tracked as a trend
- ☐ Benefits realization checked against current scope, not just the original business case
Where WIQRO fits into this
Tracking ten metrics by hand across a full portfolio, consistently, as trends rather than snapshots, is a real operational burden, which is part of why RAG status became the default shorthand in the first place. WIQRO reads the underlying project data on an ongoing basis and surfaces these signals as trends, with a risk score, an explanation of what changed, and a recommended next action, rather than a single color. It doesn't replace an executive's judgment about what to do with that information. It's built to make sure the information reaches them while the fix is still simple.
You can see this format directly in the free sample Executive Risk Report, or start with a focused, one-time Project Health Assessment on a single active project.
Bringing it together
A red, yellow, or green status is a useful shorthand for a conversation, not a substitute for measurement. The ten metrics above, tracked as trends rather than one-time snapshots, give an executive a sharper and earlier view of where a project actually stands, and which issue deserves attention first. The goal isn't more dashboards. It's fewer surprises.
See where your project actually stands.
Start with a focused, one-time Project Health Assessment on an active project, or review the sample report to see the format first.
Frequently Asked Questions
What is the best single metric for measuring project health?
There isn't one. SPI, CPI, and resource utilization each capture a different dimension of health, and a project can look fine on one while quietly failing on another. Most experienced executives track a small set, typically five to ten, rather than relying on a single number.
Why is red/yellow/green status reporting considered unreliable on its own?
RAG status is a useful summary, but it compresses a lot of nuance into one of three colors, is often self-reported by the same team being evaluated, and reflects a single point in time rather than a trend. Two projects can both show "yellow" for very different reasons and with very different urgency.
What is the difference between Schedule Variance and Schedule Performance Index?
Schedule Variance (SV) is the difference between earned value and planned value, expressed in dollars or hours. Schedule Performance Index (SPI) is the ratio of the same two figures, expressed as a number around 1.0. SV tells you the size of the gap; SPI tells you the rate.
How often should executives review project health metrics?
There's no universal cadence, but the underlying data usually changes daily or weekly, while most formal reporting happens monthly. Reviewing a smaller set of leading metrics more frequently tends to catch drift earlier than waiting for the next full reporting cycle.
Should every project track all 10 of these metrics?
Not necessarily. Smaller or lower-risk projects may only need three or four tracked closely. The right number depends on project size, complexity, and how much is riding on it.
1. ProjectManagement.com, "The Fallacy of Red, Amber, Green Reporting": https://www.projectmanagement.com/articles/315648/the-fallacy-of-red--amber--green-reporting
2. Eleco PM3, "Project RAG Status Meanings and Best Practice": https://eleco.com/pm3/knowledge-centre/how-many-rags/
3. Project Management Institute, "Understanding Project Health Metrics": https://www.pmi.org/learning/library/understanding-project-health-metrics-7540
4. Saviom, "Top 7 Project Metrics Every Manager Should Monitor": https://www.saviom.com/blog/top-project-metrics-you-need/
Explore WIQRO plans and pricing for teams managing one active project up to full government and enterprise portfolios.