What to do when a project has been amber for months
Amber means 'we are managing it', and it can mean that indefinitely. Here is how to turn it back into a decision.
Updated September 2026
- Ask what would have to change for it to go green, and by when. If nobody can answer in a sentence, it is red.
- Re-baseline from the current facts before deciding anything. Most long ambers are running against a plan that stopped being true.
- Separate the three failure modes: the plan was wrong, the scope moved, or the capability is not there.
- The options are always the same four. The work is pricing them honestly.
Amber is the most stable status in project reporting. It means the team is aware and managing, it does not require an escalation, and it can hold for quarters. Six steps convert it back into something decidable.
1. Ask what would make it green
One question, asked of the project manager and the business owner separately: what specifically has to be true for this to be green, and by what date?
If the answers differ, or if either is phrased as effort rather than an outcome, the status is not amber. If nobody can answer in a sentence, it is red and has been for a while.
2. Re-baseline against current facts
Most long ambers are being reported against a plan that stopped being accurate months ago. Before any decision, rebuild the plan from where the work actually is: what is genuinely complete, what is in progress, what has not started, and what has been added since.
This is uncomfortable and it is the most valuable thing you can do. It also frequently reveals that the remaining work is larger than the original estimate for the whole project.
3. Identify which failure mode you are in
Three causes, and they need different responses:
- The plan was wrong. The work was underestimated, usually because the estimate was made before the requirements were understood. The fix is a new plan, and the conversation is about money and dates.
- The scope moved. The thing being built is not the thing that was approved. The fix is a scope decision — and someone has to decide what gets cut.
- The capability is not there. The team, the vendor, or the technology cannot do the job as structured. This is the hardest to say and the most expensive to leave unsaid.
4. Check what is being deferred
Look at what has quietly moved to a later phase. If the date is being protected by pushing scope into an unfunded phase two, the project will hit its date and fail to deliver the benefit. That is a different problem from being late, and it is worse.
5. Price the four options
They are always the same:
Continue as planned — only honest if step two produced a plan you believe. Reduce scope to the original date — name exactly what comes out, and who signs it off. Extend, with the cost stated — including the opportunity cost of the team not being available for anything else. Stop — either permanently, or until a specific condition is met. Write the condition down.
Each needs a number. “Stop” in particular is usually cheaper than the accumulated cost of a project that limps for another year.
6. Change how it is reported
Whatever is decided, the reporting has to change, or you will be here again. Status that comes up through the delivery team will be optimistic under pressure — not dishonestly, that is how confidence works. A second line of sight to the executive accountable for the outcome is what makes bad news arrive early enough to be useful.
The practice behind it.
Want someone independent to look?
Bring the plan, the status packs and the change log. We will tell you which of the four options is actually available.
