RAG Status

RAG status is a simple way to signal the health of a project or its parts using three colors borrowed from traffic lights, which is why the acronym stands for Red, Amber, Green. Green means an item is on track, proceeding as planned with no significant concerns. Amber, sometimes called yellow, means it is at risk, showing warning signs or minor problems that need attention before they worsen. Red means it is in serious trouble, off track, blocked, or facing issues that threaten its delivery. The power of RAG status is compression: a report covering many workstreams, tasks, or objectives can be scanned in seconds, because the colors tell a reader immediately where things stand and where to look. It turns a wall of detail into a glanceable summary, which is why it is a staple of project dashboards, portfolio reviews, and status meetings across organizations.

The value of RAG status is that it directs attention. A leader reviewing a dozen initiatives does not need to read every line; the reds and ambers show where to focus, and the greens can be trusted or spot-checked. It creates a shared shorthand across a team, so everyone means roughly the same thing by a red or an amber, and it forces the person reporting to make a judgment, to declare, in effect, whether something is fine, wobbling, or failing. That judgment is the point. A status update that hides trouble in paragraphs is easy to skim past, but a red flag is hard to ignore. Used honestly, RAG status surfaces problems early, while there is still time to act, rather than letting them stay buried until a deadline is missed.

RAG status is one of several ways to summarize health, and it helps to see how it differs from the alternatives. Compared with a plain narrative status, RAG adds a categorical judgment, the color, on top of the words, so a reader gets the verdict before the detail. Compared with a numeric score or a percent-complete figure, RAG is coarser but clearer about health rather than progress: a task can be ninety percent complete and still be red if the remaining ten percent is blocked, because RAG reports risk to the outcome, not just distance traveled. Some teams extend RAG with extra colors, blue for complete, or split amber into amber-green and amber-red for finer grades, but every added shade trades simplicity for nuance, and the strength of RAG is precisely that it is simple enough to read instantly.

The other systems it is often confused with are progress bars and confidence ratings. A progress bar answers how far along something is; RAG answers whether it is healthy, which is a different question, since fast progress toward the wrong place is still trouble. A confidence rating expresses how sure someone is of an outcome; RAG expresses the state of the item now. The clearest way to keep RAG useful is to define what each color means for your context and apply it consistently, so a red always signals the same severity. Without shared definitions, one person's amber is another's red, and the colors stop being a reliable signal. RAG's whole advantage, a fast, common language for health, depends on everyone using the colors the same way.

Using RAG status well depends almost entirely on honesty and consistency. Define what green, amber, and red mean for your project before you start, so the colors carry a shared, specific meaning rather than a vague vibe, and apply those definitions the same way every period. Report the true color, not the comfortable one. The temptation to keep an item green to avoid a difficult conversation is exactly what makes RAG fail, because a status that never shows red hides the problems it exists to surface. Pair each amber or red with a short explanation and a next step, since a color alone says something is wrong but not what to do about it. And revisit the statuses regularly, because health changes, and a RAG report is only useful if it reflects the current state rather than last month's.

The failures are mostly failures of candor and discipline. Watermelon reporting, green on the outside, red on the inside, where teams mark items green to avoid scrutiny, quietly defeats the whole purpose and lets trouble grow unseen. Undefined or inconsistent colors, where amber means different things to different people, drain the signal of meaning. Colors with no accompanying explanation leave a reader knowing something is off but not why or what to do. And treating RAG as a one-time snapshot rather than a living indicator lets the report drift out of date. The discipline is to define the colors, report them honestly even when the news is bad, back each warning color with a reason and an action, and keep the status current, so RAG remains the fast, trustworthy health signal it is meant to be.

RAG status — Red, Amber, Green traffic-light flags — compresses project health into a glanceable signal, with green on track, amber at risk, and red in serious trouble.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where rag status is a core concern: