False-Green Reporting: Why Programmes Look Healthy Until They Don't

A programme can report green for weeks, then turn red when a dependency, budget or schedule issue becomes visible. The useful question is whether the warning signs were recorded but overlooked.

How RAG statuses lie

A red/amber/green status is a useful summary, but its value depends on how the team sets and reviews it.

Without shared criteria, programme managers can apply different thresholds for amber. Reviewing recorded dependencies, overdue work and open risks helps make those conversations more consistent.

The psychology of optimistic reporting

False-green reporting isn't usually deliberate deception. It's a natural consequence of three organisational dynamics:

Fear of escalation. In many organisations, reporting amber or red triggers a governance response — additional oversight, more meetings, requests for recovery plans. Programme managers learn that flagging a problem creates more work for them, not less. The rational response is to manage issues quietly and only escalate when they can't be contained.

Lack of leading indicators. Most reporting is backward-looking. It tells you what happened last week, not what's likely to happen next week. Without leading indicators — velocity trends, dependency health, resource utilisation trajectories — there's no data to challenge a green status. The PM's subjective judgement is the only signal available.

Tolerance stacking. Each level of reporting applies its own optimism bias. The task lead reports green to the project manager. The project manager reports green to the programme director. The programme director reports green to the board. At each level, minor issues get smoothed out. By the time information reaches the top, the signal has been optimised into meaninglessness.

The cost of late detection

When a programme moves from green to red without passing through amber, the recovery options are limited and expensive. Scope gets cut. Timelines get extended. Additional budget gets requested. Teams get burned out trying to recover in compressed timescales.

The cost isn't just financial. Credibility erodes. Stakeholder trust in the delivery function diminishes. The board starts asking for more reporting — which adds more overhead and makes the next false-green even more likely.

How to fix it

Better RAG reviews combine the programme manager's judgement with recorded progress, risks, dependencies and capacity indicators. Rule-based health scores give teams evidence to discuss; they do not turn a status into an objective fact.

Blue Squircle brings recorded warning signs and AI-assisted summaries into portfolio reviews. Teams can compare those signals with reported health, investigate gaps and decide whether a status change is needed.

Crucially, it also makes it safer to report amber early. When the data clearly shows a negative trend, raising it becomes a demonstration of competence rather than a confession of failure.