Delivery field notes
What should red, amber and green mean on a status report?
Define RAG status by the decision a sponsor needs, not task counts: written criteria, baseline against forecast, a worked report and how a status turns amber.
A green status can hide a late project
A fictional team reports "eight of ten tasks complete" and marks the project green. The two remaining tasks include the acceptance test that controls the go-live date, and the test environment is not ready. The report is accurate. It is also misleading, because eight completed tasks say little about whether the date still holds.
The problem is not the colour. It is that nobody wrote down what green means, so each project lead decides by feel. Feel tends towards green. Nobody enjoys being the red project in the steering meeting, and "we'll catch up" is easy to believe two weeks before a deadline.
Define each colour by what the sponsor must do
A useful RAG scale describes the action the reader should take, not the mood of the team. One well-tested example comes from the UK government's major projects portfolio. In its 2025–26 annual report, the National Infrastructure and Service Transformation Authority describes an Amber rating as meaning that delivery appears feasible but significant issues exist, requiring management attention. At the end of March 2026, 58% of the portfolio's projects were rated Amber, 15% Green and 18% Red, with 9% exempt.
Two things stand out. Amber is defined by what management must do, which is to pay attention, not by a percentage of tasks done. And most large projects sit there. An Amber rating is the normal state of a complex project with honest reporting, not a failure.
For a team-sized project, write the definitions down before the first report:
| Colour | Definition (example) | What the sponsor does |
|---|---|---|
| Green | The forecast meets the baseline for date, cost and scope; no issue needs a decision above the project | Reads and moves on |
| Amber | The forecast misses the baseline, or will without action, and the team has a credible recovery inside its authority | Watches the named recovery action and its deadline |
| Red | The forecast misses the baseline and recovery needs a decision outside the team's authority: money, scope or date | Makes the decision in the report, or sets a date to make it |
With these definitions, colour becomes a short form of a question. Red means "we need you to decide something". That framing makes Red easier to report, because it asks for help instead of confessing failure.
Show the baseline and the forecast side by side
The baseline is the date, cost and scope that were approved. The forecast is the current best estimate. Every status report should show both, every time.
Teams that move the baseline whenever the forecast slips make variance disappear while the commitment quietly changes. If a baseline change has been approved, record it with the date and who approved it, and keep the original visible. NASA describes earned value management as a way to integrate scope, schedule, cost and risk into one view of performance. You do not need full EVM to borrow the principle: performance is always measured against an approved plan, never against the latest guess.
A worked report
The project below is fictional: an office move with a building-access system to install before staff arrive.
Project: Office move and access control Report date: 14 Nov
Overall: RED (decision needed by 18 Nov)
Baseline Forecast Variance
Go-live date 2 Dec 16 Dec +2 weeks
Cost €84,000 €91,500 +€7,500
Scope As approved As approved none
Why: The card-reader supplier has not confirmed delivery. Without readers,
installation cannot start, and the building will not open to staff.
Options:
A. Wait for supplier: go-live 16 Dec, no extra cost, staff work remotely
for two more weeks.
B. Rent temporary readers: go-live 2 Dec, +€7,500 rental and fitting.
Rental firm needs a decision by 18 Nov to hold stock.
Recommendation: B. Two weeks of remote working affects 140 staff and
the lease on the old office ends 5 Dec.
Decision needed from sponsor: approve €7,500 for option B by 18 Nov.
If no decision by 18 Nov: option B expires; we proceed with A.The report leads with the colour and the decision, gives the numbers before the story, and says what happens if the sponsor does nothing. The task list, if anyone wants it, goes in an appendix.
Compare this with a typical green report for the same week: "Good progress: 8 of 10 tasks complete. Supplier chasing ongoing. On track." Every sentence is defensible, and the sponsor learns about the problem on 1 December.
Agree the tolerances up front
Written definitions need numbers to work. Agree with the sponsor, at the start, how far the forecast can drift before the colour changes: for example, up to five working days or 3% of budget stays green, up to fifteen days or 10% is amber, and anything beyond, or any change to scope or acceptance, is red. The exact thresholds matter less than having them. Without numbers, every amber is a negotiation; with them, the colour follows from the forecast, and the conversation moves to what to do about it.
How a project turns amber or red
Projects rarely jump from green to red. They drift, and the drift is visible in the report if you look for it:
- The forecast moves but the colour does not. If the forecast date changed in two consecutive reports and the colour stayed green, the definition is not being applied.
- "Chasing" appears twice. An unconfirmed dependency mentioned in two reports is a risk with a date on it. Name the date by which it must be confirmed.
- Completed tasks rise while the critical path does not move. Activity is not progress. Ask which remaining task controls the finish date.
- The decision request disappears. If last week's report asked for a decision and this week's does not mention it, find out whether it was made.
A short weekly self-check helps: would the sponsor be surprised if they knew what I know? If yes, the colour is wrong.
Common objections
"Red will cause panic." Red with a clear decision and a deadline causes a decision. Red discovered late causes panic.
"Our organisation punishes red." Then agree the written definitions with the sponsor first. A sponsor who signed off "Red means we need your decision" is far less likely to treat red as blame.
"We should report percent complete." Report it if it helps, but never let it set the colour. Ten percent of the tasks can hold ninety percent of the risk.
Running the status meeting
A good report changes the meeting. With written definitions and a decision at the top, the review can follow a simple order:
- Red items first. For each, the sponsor hears the decision needed and the deadline, asks questions, and decides or sets a date to decide.
- Amber items next. For each, confirm the recovery action, its owner and the date it must work by. If that date has passed without success, the item turns red now, in the meeting.
- Green items last, by exception. Ask one question: has the forecast moved since last time? If not, move on.
This order spends the meeting's time where decisions are needed. It also changes behaviour over a few weeks. Project leads learn that a clear red with an option gets a quick decision, while a vague green that turns red late gets an uncomfortable conversation.
Keep a simple record of decisions made in the meeting, with dates. When a project later asks why the budget changed, the record answers in a line, and the sponsor sees that their decisions were carried through.
Try it on your next report
Take your most recent status report and spend fifteen minutes on it:
- Write the baseline and the forecast for date and cost on the same line.
- Check the colour against the written definitions above. Does it change?
- Name the one dependency most likely to move the finish date, and the date by which it must be confirmed.
- If the colour is amber or red, write the decision you need, from whom and by when, and what happens if nobody decides.
The status report template has the same structure ready to fill in, and the delivery check helps you test whether the forecast is credible.
To practise writing a status update a sponsor can act on, try the open exercise Multi-country supplier transition: status report.
Sources
Method background
These sources provide general background. The worked examples and worksheets are original Response Shift teaching material; the organisations do not endorse this product.
