RAG Status: What Red, Amber and Green Really Mean
RAG status is a traffic-light system that shows the health of a project at a glance using three colours Red, Amber, and Green. It turns a messy pile of updates into a single colour a busy sponsor can read in a second. Green means on track, Amber means needs attention, and Red means escalate now.
If you've seen "RAG status" in a status report, a Jira dashboard, or an Excel tracker and wondered what those colours actually signal and how someone decides which one to pick this page covers the full form, what each colour means, how to set honest thresholds, and real report examples.
What Does RAG Stand For? (The Full Form)
R = Red · A = Amber · G = Green
That's it. RAG is an acronym for the three colours in a traffic-light system used in project reporting. Some organisations call it the "RAG rating," the "RAG indicator," or simply the "traffic light" system.
A few organisations add a fourth status:
| Colour | What it signals | Typical action |
|---|---|---|
| Green | On track no intervention needed | Continue as planned |
| Amber | At risk needs attention but recoverable | Team-level corrective action |
| Red | Off track escalate immediately | Sponsor or steering committee intervention |
| Blue (optional) | Complete / delivered | Close out or archive |
| Grey / White (optional) | Not started / no update yet | Await the next reporting cycle |
The fourth colour varies by organisation. Blue for "complete" is the most common addition. Some teams use Grey for "not yet started" and White for "no update received." The core three - Red, Amber, Green - are universal.
What Does Each Colour Mean?
The colours aren't decorative. Each one signals a specific level of project health and triggers a specific kind of response.
Green - On Track
Green means scope, schedule, and budget are all healthy. No intervention is needed from leadership. The team is delivering as planned, risks are managed within the team, and there's nothing the sponsor needs to act on right now.
What Green does not mean: perfect. A project can have minor issues and still be Green, as long as those issues are being handled without escalation. Green means "no action required from above," not "nothing is happening."
Build an AI-First Career, Master the Complete Skillset
Choose from our industry-leading programs designed for career success
Modern Software and AI Engineering Program
Master full-stack development with AI integration
+1000 moreModern Data Science and ML with specialisation in AI
Advanced data science techniques with AI specialization
+1000 moreAdvanced AIML with Specialisation in Agentic AI
Deep dive into AIML with focus on Agentic systems
+1000 moreDevOps, Cloud & AI Platform Engineering
Build and manage AI-powered cloud infrastructure
+1000 moreAI Engineering Advanced Certification by IIT-Roorkee
Premier AI engineering certification from IIT-Roorkee
AI Forward Deployed Engineer Program
Full-stack engineering, production AI and client-facing consulting
+1000 moreAmber - At Risk / Needs Attention
Amber is a warning. Something is slipping or under threat a deadline is tight, a budget is creeping, a key resource is stretched but the team believes it can recover with corrective action. The problem is manageable, but it needs active attention.
The honest truth about Amber: this is where most arguments happen. Amber is the most subjective colour in the RAG system. One person's Amber is another person's Green, and another's Red. The difference usually comes down to how much risk tolerance the organisation has and how safe it feels to raise a concern. We'll tackle this in the thresholds section below.
Red Off Track / Escalate
Red means a real problem exists that the team cannot fix on its own. Deadlines, budget, or scope are genuinely threatened, and help is needed from above a project sponsor, a steering committee, or senior leadership. Red is not a failure signal; it's an escalation signal. It says: "we need decisions or resources that are outside the team's control."
What Red triggers: an immediate conversation with the project sponsor. A recovery plan. Possibly a scope cut, a budget increase, or a timeline extension. The worst thing a team can do with a Red status is sit on it.
How Is RAG Status Used in Project Management?
RAG status shows up in three main places and each serves a different audience.
In a Status Report
The most common home. A typical project status report opens with an overall RAG for the project, then breaks it down by workstream scope, schedule, budget, risk, resources each with its own RAG and a one-line commentary.
Here's what that looks like:
| Workstream | RAG | Commentary |
|---|---|---|
| Overall | Amber | Vendor delivery delayed by 2 weeks; recovery plan in progress |
| Scope | Green | Requirements locked; no scope creep this period |
| Schedule | Amber | Phase 2 milestone slipped; buffer absorbing it for now |
| Budget | Green | Within 3% of plan |
| Risk | Amber | Key resource on leave next month; backup identified |
| Resources | Green | Team fully staffed |
Example project status report using RAG ratings for scope, schedule, budget and risk
The overall RAG is usually driven by the worst workstream, not an average. If schedule is Red but everything else is Green, the overall project is Red because the thing that's broken needs the most attention.
On a Dashboard (Jira, Excel, PowerPoint)
In tools like Jira, RAG status often appears as a custom field or a coloured label on issues and epics. In Excel, it's typically done with conditional formatting cells that turn red, amber, or green based on a value. In PowerPoint steering-committee decks, it's a summary tile at the top of the slide.
Most project-management tools support RAG natively or through simple configuration. The tool doesn't matter the signal does.
Who Reads It and Why
RAG status is a communication tool. Its primary audience is people who don't have time to read the full report:
- Project sponsors use RAG to decide where to spend their attention. A Green project gets a glance; a Red project gets a meeting.
- Steering committees use RAG across a portfolio to spot which projects need intervention.
- Team leads use workstream-level RAG to flag issues early, before they become project-level problems.
- PMOs (Project Management Offices) use RAG to build portfolio dashboards and identify trends.
The whole point of RAG is speed. A sponsor looking at ten projects can scan ten colours in seconds and know exactly where to focus. That's why honest colour choices matter if the colours lie, the system breaks.
How Scaler Transformed Careers in Different Fields
Scaler learners achieved 2.5x salary growth with average post-Scaler CTC reaching ₹23L.
Google
Amazon
Microsoft
Flipkart
Adobe1200+ moreFor a closer look at what a product manager actually does day to day, including status communication and stakeholder management, see that roadmap.
How Do You Decide the RAG Colour? (Setting Thresholds)
This is the section most guides skip and the one that separates a useful RAG system from a decorative one.
Define Thresholds Up Front
The single most important thing: agree what Red, Amber, and Green mean before the project starts, not when the first status report is due.
A simple threshold framework:
| Dimension | 🟢 Green | 🟡 Amber | 🔴 Red |
|---|---|---|---|
| Schedule | Within 5% of plan | 5–10% variance | >10% or missed critical milestone |
| Budget | Within 5% of plan | 5–10% variance | >10% overspend |
| Scope | Requirements stable | Minor changes managed | Uncontrolled scope creep |
| Risk | Risks managed within team | One or more risks need escalation | Critical risk with no mitigation |
The exact percentages matter less than having them agreed in writing. When thresholds are undefined, every RAG decision becomes an argument and the loudest voice wins instead of the data.
Judge Scope, Schedule, and Budget Separately, Then Roll Up
A project can be Green on budget but Red on schedule. That's normal. The workstream-level RAGs tell the real story; the overall RAG is a summary.
The rule of thumb: the overall RAG is driven by the worst workstream, not an average. If one dimension is Red, the project is Red because that's where the attention needs to go. Averaging a Red schedule with a Green budget and calling the project Amber hides the problem.
Turn Learning into Career Growth
Avoid "Watermelon" Reporting
"Watermelon reporting" is the industry term for projects that look Green on the outside but are Red on the inside. It happens when:
- Teams feel pressure to keep everything Green so leadership doesn't panic
- Amber is treated as a failure, so people skip straight from Green to Red (or stay Green too long)
- Thresholds are vague enough that any colour can be justified
The fix is cultural, not technical. When Amber is treated as a healthy signal "we spotted a problem early and we're fixing it" teams report honestly. When Amber is treated as a failure, teams hide problems until they become emergencies.
The practical advice: make it explicitly safe to report Amber. Celebrate early warnings. Treat a project that goes Amber-to-Green as a success, not a scare. The organisations with the best RAG discipline are the ones where raising a Red is respected, not punished.
RAG Status Examples
Here are three worked examples showing the reasoning behind each colour.
Example 1: Green overall, Amber on resources
A software delivery project is on schedule and within budget. The team is fully staffed, but one key developer has given notice and leaves in three weeks. A backup has been identified but isn't fully up to speed yet.
- Overall: Green - delivery is on track today
- Resources: Amber - a known risk that needs active management
- Reasoning: the project isn't in trouble yet, but it will be if the backup plan fails. Amber on resources flags the risk early.
Example 2: Flips to Red after a vendor slip
A product launch project was Green across the board. The third-party payment gateway vendor announces a four-week delay on their API. The launch date is six weeks away. There's no alternative vendor and no way to compress the schedule enough.
- Overall: Red - the launch date is now at serious risk
- Schedule: Red - critical path is broken
- Reasoning: the team can't fix this alone. The sponsor needs to decide: delay the launch, descope the payment feature, or find a workaround. That decision is above the team's pay grade.
Example 3: Amber recovered to Green
A data migration project went Amber on budget in Month 2 a cloud provider's pricing changed and the projected overspend hit 8%. The team renegotiated the contract and optimised storage, bringing the variance back to 3%.
- Overall: Green - variance within threshold
- Budget: Green - recovered from 8% to 3%
- Reasoning: the Amber flag triggered the right conversation at the right time. The team fixed it without escalation. This is RAG working as intended.
RAG Status Template What to Include
You don't need a special tool. A RAG status report can be built in Excel, PowerPoint, Google Sheets, Jira, or even a shared document. Here's the structure:
Project header:
- Project name
- Reporting period (e.g. "Week of 1 Sep 2026")
- Project sponsor
- Overall RAG status
Workstream breakdown (one row each):
| Workstream | RAG | Commentary | Key risk / action |
|---|---|---|---|
| Scope | |||
| Schedule | |||
| Budget | |||
| Risk | |||
| Resources |
Footer:
- Key decisions needed (if any)
- Next milestone and date
- Escalations (if Red)
The value is in the structure, not the tool. Keep the commentary to one line per workstream if it needs a paragraph, it needs a meeting, not a report.
RAG status report template layout with overall status, workstream rows and next actions
FAQs
What does RAG status stand for?
RAG stands for Red, Amber, Green a traffic-light system used in project management to show the health of a project or workstream at a glance. Green means on track, Amber means at risk, and Red means off track and needing escalation. It's the most common shorthand for project health in status reports and dashboards.
What does Amber mean in RAG status?
Amber means at risk and needing attention, but still recoverable within the team. It's a warning signal something is slipping or under threat, but the team believes corrective action can fix it without escalation. Amber is the most subjective colour in the RAG system, which is why clear thresholds matter.
What are the 4 colours of RAG status?
The core three are Red, Amber, and Green. Some organisations add a fourth: commonly Blue for "complete" or "delivered," Grey for "not yet started," or White for "no update received." The fourth colour varies by organisation the core three are universal.
What is RAG status in a project status report?
It's the single colour at the top of the report showing overall project health, usually followed by a RAG per workstream (scope, schedule, budget, risk, resources). Each workstream gets its own colour and a one-line commentary. The overall RAG is typically driven by the worst workstream, not an average.
How do you set RAG status thresholds?
Agree variance limits before the project starts. For example: Green = within 5% of budget/schedule, Amber = 5–10% variance, Red = over 10% or a missed critical milestone. The exact numbers matter less than having them agreed in writing undefined thresholds turn every RAG decision into an argument.
Is RAG status the same as the AI term "RAG"?
No. In project management, RAG stands for Red, Amber, Green a traffic-light reporting system. In AI, RAG stands for retrieval-augmented generation, which is an unrelated technology. The two terms share the same acronym but have completely different meanings and audiences.
The more you practise honest, threshold-based status reporting, the more valuable you become to any team. Clear signals build trust and trust is what gets projects the decisions and resources they need.
