Why Programme Reporting Often Fails to Show Project Health
A programme report can show every activity on track and still miss the fact that the project is heading for serious trouble.
Marcel Mbene, ChPP — Founder, Bold Leverage Ltd · 13 July 2026
Percentage complete is a poor proxy for health
Most programme reporting is built around percentage complete against a baseline schedule. It is easy to produce and easy to present, but it answers a narrower question than most people assume: it tells you whether activities are proceeding roughly on time. It does not tell you whether the remaining work is achievable, whether float has been consumed by unreported issues, or whether the sequence the programme assumes still reflects reality on site.
Where the gap shows up
A programme can report 60% complete while quietly relying on an assumption — an approval that has not yet been received, a piece of information that has not yet arrived, a resource that has not yet been secured — that, if it slips, invalidates the remaining 40%. Percentage-complete tracking rarely surfaces this kind of dependency risk, because it measures what has happened rather than what the remaining work depends on.
Similarly, float consumption often goes unreported until it becomes critical. A project can burn through weeks of contingency quietly, activity by activity, without a single reported delay — until the float runs out and the programme suddenly shows red across multiple fronts at once.
What better reporting looks like
Programme reporting that actually reflects project health tracks the assumptions the remaining programme depends on, not just the activities completed so far. It reports float consumption explicitly, even when no individual activity has yet slipped. And it distinguishes between activities that are on the critical path and those with genuine spare capacity, so that leadership's attention is directed at what actually threatens completion.
Our view
This is why, as part of our project management and delivery assurance work, we place as much weight on programme logic and assumption tracking as on the headline percentage-complete figure — a project that looks healthy on paper is not the same as a project that is healthy.