What is a RAG status report?

A RAG status report uses red, amber, and green labels to communicate project health, usually across schedule, budget, scope, risk, and overall status.

What does RAG stand for in project reporting?

RAG stands for red, amber, and green. Red means off track, amber means at risk, and green means on track when definitions are agreed.

What should a RAG status report include?

Include overall RAG, schedule, budget, scope, risk, evidence, owner, action, escalation rule, and review date.

Can a project be green with open risks?

Yes, if the risks are understood, owned, and manageable without escalation. If a risk threatens the plan, amber is usually more accurate.

What is the biggest RAG reporting mistake?

The biggest mistake is using colors without definitions or evidence. A color should lead to action, not hide project reality.

Back to Blog

RAG status report notifications for project health changes

RAG Status Report Guide

By Dawid Oleksiuk ScrumbuissPublished July 2, 2026Editorial policy

A RAG status report uses red, amber, and green labels to show project health. The labels are useful only when they are defined, evidence-based, and tied to action.

This guide targets RAG status report and "what is RAG in project status report" queries found in SEMrush. It supports the project status report format guide by focusing on health-color reporting.

What RAG Means

Label	Meaning
Green	The project is on track and known risks are manageable
Amber	The project is at risk but can recover with action
Red	The current plan is not realistic without a decision, change, or escalation

Some teams add blue for complete or grey for paused. If you add labels, define them before reporting starts.

RAG Template Fields

Field	What to capture
Overall RAG	Green, amber, or red
Schedule RAG	Timeline health
Budget RAG	Cost or effort health
Scope RAG	Scope stability
Risk RAG	Risk exposure
Evidence	Reason for the color
Owner	Person accountable for next action
Action	Mitigation, decision, or escalation
Review date	When status will be reassessed

RAG Example

Area	RAG	Evidence	Action
Overall	Amber	API approval may delay QA start	Escalate approval and prepare fallback
Schedule	Amber	QA start depends on approval by Friday	Review again Friday
Budget	Green	No material change in forecast effort	Continue monitoring
Scope	Green	No new unapproved requests	Keep change control active
Risk	Amber	Security review still open	Track in risk register

RAG Reporting Rules

Define red, amber, and green before the first report.
Require evidence for every amber or red rating.
Do not use green when a major decision is unresolved.
Show whether the color improved or worsened since the last report.
Connect red and amber status to escalation paths.

FAQ

Frequently
asked
questions

Unlock Success &
Power Up Your Projects

Get Started

Seeking more?Check out similar articles

Next to explore

Explore more pages to understand the product suite, common workflows, and evaluation guides.

Use cases

→

Practical workflows and examples for different teams.

Templates

→

Copy-ready templates you can adapt inside Scrumbuiss.

Compare

→

Project management software comparisons and alternatives for delivery teams.