RAG status reporting: useful signal or management theatre?
A practical way to define red, amber and green status, combine evidence with judgement, and stop green reports hiding late projects.
Decision this guide supports
When should status trigger attention, intervention or escalation?
Key takeaways
- RAG is a prompt for management action, not a score of how hard the team is working.
- Thresholds must be agreed before bad news arrives and paired with evidence and a recovery path.
- The overall status should represent the threat to the project outcome, not an average of coloured items.
Why RAG often fails
Red, amber and green look objective, but colour alone contains almost no information. Teams frequently use different definitions, sponsors discourage red, and project managers turn items green as soon as a recovery action is written down.
The result is status theatre: a reassuring dashboard that reports confidence rather than control. A useful status signal must be tied to agreed tolerances, observable evidence and a management response.
A practical starting convention
There is no universal set of RAG thresholds. The table below is an operating convention to tailor to your governance, risk appetite and delivery model — not an external standard.
| Status | Meaning | Expected response |
|---|---|---|
| Green | Outcome and forecast remain within agreed tolerance; no material exception needs intervention. | Continue delivery and monitor leading indicators. |
| Amber | A material threat exists, but a credible recovery within delegated authority is still possible. | Name the cause, owner, action, next evidence date and trigger for red. |
| Red | Outcome or forecast is outside tolerance, or recovery requires a decision beyond the team’s authority. | Escalate the decision, options, recommendation and consequence of delay. |
| Grey | Evidence is missing or too stale to make a responsible judgement. | Restore information flow; do not translate unknown into green. |
Use evidence first, then judgement
Automated indicators help expose variance consistently: forecast slippage, overdue milestones, unresolved critical dependencies, cost variance, defect trends or missing approvals. They are inputs, not the final answer.
A project manager then applies context. A milestone may be late but have no effect on the outcome; an apparently on-time milestone may depend on an untested assumption that makes the project amber. Record the reason for any judgement that overrides the mechanical signal.
Status sentence
Amber because [cause] threatens [outcome or milestone] by [impact]. [Owner] is taking [action]; evidence is due [date]. Escalate to red if [trigger].
Roll up significance, not colour arithmetic
A programme with ten green projects and one red project is not automatically amber, and averaging colour scores is rarely defensible. Ask whether the red component threatens a programme outcome, benefit, shared dependency, regulatory obligation or decision gate.
Roll-up rules should combine severity with relevance. A child status can drive the parent when it affects a critical path, a mandatory outcome or an agreed tolerance. Otherwise it may remain visible as a local exception without changing the parent status.
A five-step status cadence
- 1Refresh the evidence at an agreed cut-off time.
- 2Compare current forecast with baseline and tolerance.
- 3Review leading indicators and dependencies, not only completed work.
- 4Apply judgement and record the short status rationale.
- 5Assign actions or decisions, then set the next evidence date.
Anti-gaming rules
- Red describes the project condition, not the competence of the project manager.
- A recovery plan does not turn red to amber until evidence supports recovery.
- Moving a forecast date does not remove the variance from the approved baseline.
- Missing data is unknown, not green.
- The person accountable for delivery proposes status; governance can challenge it but should record any override.
- Trend matters: improving amber and deteriorating amber need different conversations.
Example: a dependency that is still technically on time
A data-migration rehearsal is due in three weeks. The date has not slipped, but the source-data owner has not approved the extraction rules and is unavailable next week. A date-only dashboard stays green.
A controlled view is amber because the unresolved approval threatens the rehearsal and the launch path. The update names the approval owner, the decision deadline, a fallback option and the point at which the launch forecast becomes red. This is the difference between recording history and managing forward.
Sources & method
This guide is RuruPilot’s practical synthesis. Definitions and established control principles are grounded in the primary sources below; examples, operating conventions and recommendations are our interpretation unless stated otherwise.
- 1APM glossary: project status report
Association for Project Management. The reporting basis for accomplishments, spending and schedule variance.
- 2Schedule Assessment Guide: Best Practices for Project Schedules
U.S. Government Accountability Office. Guidance on maintaining a credible, controlled forecast and analysing schedule risk.
Talk it through
Want to apply this to your own project?
Tell us what you are facing. We can discuss project support, practical PM training, consultancy, or how RuruPilot could support your team.
Prefer email? Write to hello@macrocyra.com.