Red Amber Green Is Useless Unless Someone Owns Amber

Every project on the report is amber. It has been amber for two months. Nobody has done anything about any of it, and the report goes out again next week looking exactly the same.

Red amber green status works only when three things are written down: what each colour means in plain terms, who is required to act on each one, and how long a project may stay amber before it automatically becomes red. Without the third rule, amber becomes a comfortable parking space where projects go to avoid attention, and the whole system reports nothing.

Why amber is the broken one

Red is uncomfortable, so people avoid it. Green invites questions if things later go wrong, so people avoid that too. Amber is safe. It says "some concerns", which is true of everything and commits nobody.

The result is a report where almost everything is amber, which carries the same information as a report where everything is blank. Meanwhile the two projects that are genuinely in trouble are hidden among the twenty that are basically fine.

Define the colours by action, not by feeling

Most definitions are written in adjectives. "Green: on track. Amber: some risk. Red: significant issues." Everyone reads those differently.

Define them by what happens next instead.

• Green. No help needed. The owner reports at the normal cadence and nobody else does anything.
• Amber. The owner has a specific problem, has a plan, and needs a decision or a resource from someone named. That named person is expected to respond within a stated time. A review that has sat untouched for days is a classic amber, and the fix there is structural.
• Red. The owner does not have a plan, or the plan needs something beyond their authority. This triggers a session with the people who can change scope, date or resourcing.

Written like this, the colour is a request rather than a mood. You can tell whether it is right by asking one question: what is somebody meant to do about it.

Somebody has to own amber

This is the rule most status systems miss. Green owns itself and red escalates automatically. Amber sits in between and gets nobody.

Name the person who owns amber. Usually a programme lead or a delivery manager. Their job is not to fix everything, it is to make sure every amber has a named blocker, a named person who can clear it, and a date by which it will be cleared or turn red.

Give them a small standing slot each week to go through the ambers. Fifteen minutes is often enough, and it sits neatly alongside the twenty minute board cleanup on the same afternoon. What matters is that somebody looks at every one of them, every week, with the authority to ask why it is still amber.

Put a clock on amber

Decide how long a project may stay amber. Two weeks is a common choice and the exact number matters less than having one.

At the limit, one of two things happens. It goes green because the problem was solved. Or it goes red, which means the current approach did not work and the people who can change scope, date or resourcing get involved.

That is the whole mechanism. It sounds harsh and it is actually kind, because it means somebody with more room to move gets involved before the situation is unrecoverable. Teams that hold projects at amber for a quarter are usually protecting people from a conversation that would have helped them in week three.

The status meeting that follows

With those rules, the reporting meeting changes shape.

Green projects get named and skipped. Amber projects get one question each: what is the blocker, who is clearing it, by when. Red projects get real time, because there are only ever a few of them. If there are many, the team has started more than it can finish, which is a work in progress problem rather than a reporting one.

If your meeting is spending equal time on everything, the colours are not doing their job.

Two habits to watch for

Watermelon reporting. Green outside, red inside. It happens when reporting red has been punished before, even mildly. If you want honest colours, the response to a red has to be help arriving, consistently, or you will not see another one.

Colour by seniority. Someone senior looks at the report and asks for a colour to be changed without the underlying situation changing. Once that happens twice, the report is a negotiation and nobody trusts it again.

Both come from the same place. The colour is a signal for getting help. Treat it as a scoreboard and people will manage the scoreboard instead of the work.