
A project status is a one word answer to a long question: is this project going to deliver what was promised, on time and on budget? Most teams answer it with a color. Red, amber, or green is quick to read in a meeting, which is why RAG status shows up in almost every project report. It is also easy to get wrong, because the color is usually picked by the person running the project, on gut feel, at the moment they least want to raise an alarm.
This guide covers the common project statuses and what each one means, how RAG status works, and how to calculate it from hours, budget, and schedule data so the color reflects the project rather than the mood. There is a worked example, a set of thresholds you can adapt, and a short section on why so many projects report green until the week they turn red.
What is project status?
Project status is the current state of a project measured against its plan: how far along the work is, whether it will finish on time, whether it will stay within budget, and what is getting in the way. A useful status has two parts, a label or color that can be read at a glance and a few lines that explain it. The label tells a stakeholder where to look, and the explanation tells them what to do about it.
Status is different from progress. Progress is how much work is done, for example 45% of tasks complete. Status compares that progress with where the project should be by now. A project 45% complete is on track if the plan said 45% by this week, and in trouble if the plan said 60%. Our guide on how to track project progress covers the measuring side in detail.
Common project statuses and what they mean
Most organizations use a short, fixed list of project statuses so that reports from different teams can be compared. Names vary, but the set usually looks like this:
| Status | What it means | Typical action |
|---|---|---|
| Not started | Approved but no work logged yet | Confirm start date and resources |
| On track | Schedule, budget, and scope are within agreed limits | Keep reporting as planned |
| At risk | A limit is close to being missed, but recovery is still possible | Name the risk, the owner, and the recovery step |
| Off track | A limit has been missed and the plan no longer holds | Escalate and agree a new plan or baseline |
| On hold | Work is paused by decision, not by delay | Record the reason and the date to review |
| Completed | Deliverables accepted and work closed | Run a short review and archive |
| Cancelled | Stopped before completion | Record why and what was spent |
RAG colors cover the middle three. Green is on track, amber is at risk, and red is off track.
What is RAG status?
RAG stands for red, amber, green, the colors of a traffic light. As project status colors, green means the project is on track, amber means it needs attention, and red means it is in serious trouble. Some organizations use yellow instead of amber, and some add further colors; one PMI paper describes blue for excellent performance and orange between yellow and red (PMI).
A well documented public version comes from the UK government, which rates every project in its Government Major Projects Portfolio on a five point Delivery Confidence scale. Its Delivery Confidence Guide for Review Teams defines the levels this way:
| Rating | Official definition (excerpt) |
|---|---|
| Green | “Successful delivery of the project/programme to time, cost and quality appears highly likely” |
| Amber/Green | “Successful delivery appears probable. However, constant attention will be needed” |
| Amber | “Successful delivery appears feasible but significant issues already exist requiring management attention” |
| Amber/Red | “Successful delivery of the project/programme is in doubt with major risks or issues apparent in a number of key areas” |
| Red | “Successful delivery of the project/programme appears to be unachievable” |
The portfolio figures show how the ratings fall in practice. At the end of March 2026, 15% of UK major projects were rated green, 58% amber, and 18% red, with 9% exempt from rating, according to the National Infrastructure and Service Transformation Authority. In that snapshot, most major projects were amber, so an amber rating on its own is normal rather than a sign of failure.
How is RAG status calculated?
There is no single formula. The UK definitions above describe confidence, not numbers, and most organizations set their own thresholds. What makes a RAG status trustworthy is that the thresholds are agreed before the project starts and checked against data, not chosen afterward.
A practical approach is to rate three dimensions separately and let the worst one set the overall color:
| Dimension | What to compare | Example thresholds |
|---|---|---|
| Schedule | Work completed vs work planned by today, and milestone dates | Green: up to 5% behind. Amber: 5 to 15% behind. Red: more than 15%, or a key milestone missed |
| Budget | Hours or cost spent vs the value of work completed | Green: up to 5% over. Amber: 5 to 15% over. Red: more than 15% over |
| Scope and quality | Unapproved changes, open defects, acceptance issues | Green: none material. Amber: changes or issues with a plan. Red: changes or issues with no plan |
The thresholds in the table are examples to adapt, not a standard. A fixed price client project may need tighter budget limits than an internal one, and a project with a hard launch date may treat any milestone slip as red.
For schedule and budget, the cleanest comparison uses earned value: the planned share of the budget for the work actually completed. It separates “we spent a lot” from “we spent a lot and got little done,” which a simple spend versus budget check cannot do. Unapproved changes are covered in our guide to scope creep.
Worked example: setting RAG from project data
The figures are illustrative. A 12 week project has a budget of 600 hours. At the end of week 6, the plan says 300 hours of work should be done. Time tracking shows 360 hours logged, and 45% of the work is complete.
A manager looking only at the calendar might call this project amber or even green: it is week 6 of 12, and nearly half the work is done. The hours do not back that up. At the current rate, the project will need about 800 hours instead of 600 (360 hours for 45% of the work). The red status should start that conversation now, while there are still six weeks to act.
Why projects stay green until they turn red
Project managers have a name for a report that is green on top and red underneath: a watermelon project. Writing on ProjectManagement.com, Bart Gerardi describes them as projects “green on the outside while being red on the inside,” and explains why they happen: once red becomes “an invitation for an executive to dig into a project,” few people “want to declare that their project is red, even if it truly is on fire” (ProjectManagement.com).
The fixes are mostly about process:
- Agree thresholds in advance. If amber starts at 5% over budget, nobody has to argue about it later.
- Base the color on data. Hours logged against tasks and estimates are harder to explain away than a feeling.
- Make amber safe. If amber triggers support instead of blame, people report it earlier.
- Show the trend. A project that moved from green to amber this week needs different attention than one that has been amber for two months.
RAG status in agile
Agile teams do not usually track a fixed baseline, so schedule and budget thresholds need different inputs. Common choices are progress toward the sprint goal, the trend in the release burndown, and how much of the planned capacity has been used. A sprint that is halfway through its days but has finished a quarter of its committed work is amber; a release whose remaining backlog clearly exceeds the time left is red.
It works the same way as in a traditional project. Agree what each color means at the start, then let the data set it.
Reporting project status
A good project status report fits on one page. It shows the overall color and the color for each dimension, a few lines on what changed since the last report, the main risks with owners, and any decisions needed from the reader. If you need a starting point, use our project status report template. For choosing the numbers behind the colors, see our guide to project management KPIs.
Good project status management also keeps meetings short. Spend project status meetings on amber and red items, and give green projects a line in the report rather than time on the agenda.
Tracking project status in actiTIME
For project status tracking, actiTIME connects the time your team logs with the plan, which is the data a trustworthy status needs.
- Tasks have estimates, deadlines, and custom workflow statuses, in a list or on a Kanban board.
- The Estimated vs. Actual Time Report shows which tasks run over and by how much.
- Time, cost, and billing budgets on customers, projects, and tasks show a progress bar that turns red when the budget is exceeded.
- The Reports Dashboard shows trends in real time widgets, so you can see a project drifting before the next status meeting.
FAQ
What does RAG mean in a status report?
RAG stands for red, amber, green. Green means on track, amber means at risk and needing attention, and red means serious problems that need escalation or a new plan.
What is RAG status in a PMO?
In a project management office, RAG status is the common scale used to compare many projects in one portfolio view. The PMO usually defines the thresholds so that every project manager rates the same way, and reviews amber and red projects first.
How is RAG status calculated?
By comparing schedule, budget, and scope against thresholds agreed in advance, rating each one, and taking the worst as the overall status. Earned value, the planned budget for the work actually completed, gives a more reliable schedule and budget comparison than spend alone.
What are the different project statuses?
The most common set is not started, on track, at risk, off track, on hold, completed, and cancelled. On track, at risk, and off track correspond to green, amber, and red.
What is the difference between amber and red?
Amber means problems exist but can be fixed within the current plan. Red means the current plan will not deliver, and the project needs a decision: more time, more money, less scope, or a new baseline.
Let the data pick the color
A project status is only as good as the evidence behind it. Agree what green, amber, and red mean before work starts, measure schedule and budget against earned value, and report the trend along with the color. Done this way, a red status shows up while there is still time to act on it.
To see the real status of your projects, start a free trial of actiTIME. It runs for 30 days with every feature included, and afterward you can keep the permanent free version for teams of up to 3 users.




