The Dashboard Is a Claim: Testing Programme Green Before the Board Pack

Programme dashboards are designed to reassure. A board pack arrives with a small set of colours, a milestone chart and a burn-rate line, and the sponsor is invited to take comfort from the absence of red. That comfort is often premature. In my work with UK owner-managers and programme sponsors, the most expensive reporting failures rarely begin with a dishonest dashboard. They begin with a dashboard that is technically accurate, carefully worded and several weeks behind the delivery reality it describes.

The answer is not more reporting. It is better scepticism. A sponsor does not need to become a delivery manager, but they do need to treat a green status as a claim to be tested. The following tests are practical, proportionate and suitable for the next board pack in 2026.

A green status is a judgement, not a measurement

RAG reporting compresses complex information into a colour. That compression is useful, but it hides the judgement beneath it. A programme can be green because the work is on track, or because the team has redefined the baseline, or because a critical dependency has not yet failed. The sponsor's first question should therefore be: who assigned this colour, and against what definition?

Ask for the RAG criteria in writing. If green means 'no known issues', that is a different claim from 'delivery confidence remains within tolerance'. If the criteria have changed since the last board, ask why. A colour is only comparable over time if the definition behind it is stable.

Test the milestone, not the colour

Milestones are where programmes usually reveal themselves. A dashboard may show a milestone as green because the date has not moved, but the date is only one part of the commitment. Ask what evidence supports completion: signed acceptance, tested output, a live service, a reconciled data set, or a verbal assurance from a supplier.

For the next three milestones, request the completion criteria and the current evidence position. Then ask a simple question: if the milestone date were tomorrow, what would still be missing? The answer is often more informative than the status itself.

Look also at float. A milestone can be green and still consume all of its contingency. If the plan has no float left before a fixed regulatory, contractual or operational deadline, the colour is describing the past, not the risk.

Interrogate the burn-rate story

Burn rate is a favourite dashboard metric because it looks objective. It is not. Spend to date tells you what has been consumed; it does not tell you what has been delivered. A programme can be under budget and behind delivery, or over budget because it is accelerating work that should have happened earlier.

Ask for the forecast to complete, not just the spend to date. Compare the current forecast with the approved budget and the last forecast. If the number has moved, ask what changed and whether the change was approved through change control. Repeated small reforecasts are a warning sign: they can indicate that the programme is absorbing pressure without a corresponding decision.

The more useful ratio is value delivered against money consumed. That is harder to measure, but even a rough view is better than treating a burn-rate line as proof of progress.

Ask what would change the colour

A dashboard should support a conversation about decisions, not just a review of status. The sponsor's most useful question is: what would have to happen for this green to become amber or red? If the answer is vague, the reporting is not yet decision-ready.

Ask the programme lead to name the two or three leading indicators they are watching. These might be supplier acceptance dates, vacancy rates in critical roles, test defect trends, data migration reconciliation, or the number of open decisions above a certain threshold. Leading indicators are rarely comfortable, but they are more useful than a colour that changes only after the issue has landed.

Turn the board pack into an early-warning conversation

The board pack should arrive before the meeting, not during it. Sponsors should read the narrative and the numbers together, and note where the story and the data diverge. A dashboard that says green while the narrative describes 'increased pressure' on a critical dependency is not necessarily wrong, but it deserves a question.

In the meeting, avoid asking 'are we on track?' That question invites a summary. Ask instead: 'What has changed since the last report?', 'Which assumption is most fragile?' and 'What decision do you need from this board?' These questions shift the conversation from reassurance to governance.

Finally, keep a short record of the answers. If a programme lead says a supplier dependency is stable, note the date and the evidence. If they say the milestone is green because acceptance is expected next week, note what happens if it is not. The record does not need to be elaborate. It needs to be specific enough to test at the next meeting.

The sponsor's discipline

A green dashboard is not an enemy of good governance. It is a useful summary, provided the sponsor remembers what it is summarising. The discipline is to challenge the claim without undermining the team, and to ask for evidence without demanding a second reporting layer.

For UK owner-managers, the commercial stakes are often personal. A programme that drifts quietly can consume management attention, cash and credibility long before it turns red. The sponsor who tests the green early is not being negative. They are buying options while those options are still cheap.

In 2026, the most valuable reporting improvement may not be a new tool or a longer template. It may be a shorter set of questions, asked consistently, before the colour is accepted.