Is your project dashboard reporting progress or concealing deterioration?

Is Your Project Dashboard Reporting Progress or Concealing Deterioration?

A dashboard can remain green while the project�s forward case weakens. Percentage complete rises because activity occurred; cost and schedule appear stable after baselines are reset; risks stay amber until they materialise; benefits remain unchanged although the mechanism has failed. Aggregation turns deterioration into a smooth average.

Report three views together: original approved baseline, current forecast and actual performance. Show movement in scope, contingency, completion range and benefits, not only the latest point estimate. Separate physical output from usable capability and economic outcome. A delivered component is not progress if integration, adoption or demand makes it unable to produce the promised benefit.

Use leading evidence beneath the headline: critical-path float, unresolved interfaces, decision latency, defect discovery, supplier milestones, cost-to-complete, risk retirement and benefit assumptions. Display ranges and confidence. A stable expected date with a widening downside range is deterioration even before the central forecast changes.

The UK Project Delivery Functional Standard updated in 2025 makes portfolio, programme and project governance mandatory and covers planning, control, transition, use and disposal. That lifecycle perspective matters: reporting should follow the outcome through operation rather than declare success when project activity ends.

Protect an immutable decision history and explain every rebaseline as a change, not an erasure. Require owners to state cause, economic consequence and action. Compare forecasts with reference-class outcomes and track whether contingency is being consumed faster than uncertainty retires. A useful dashboard makes emerging bad news easier to act on than to average away.