Public programmes are judged twice: once in delivery, and again when someone asks why the date moved. Ministers, boards, audit, opposition scrutiny and the press do not accept “the planner’s file said so.” They need a chain from baseline to update to cause to decision. That chain is reporting that survives scrutiny.
Public money makes the finish date a public asset. Soft progress, soft data dates and decorative dashboards spend that asset quietly until the question arrives too late to answer well.
Why public reporting fails under pressure
- Stage gates exist on slides but not as predecessors in the network.
- Percent complete cannot be reconciled to remaining work.
- Different teams close on different cut-offs.
- Change is absorbed into “reforecast” without a decision record.
- The pack leads with activity volume instead of the date at risk.
Under scrutiny, those habits look like concealment even when nobody intended it. The fix is process, not better graphics.
What scrutiny-ready reporting requires
It requires an accepted baseline, a named data date, frozen progress rules, a walkable critical path, and a narrative that states what moved, why it moved, and what decision is required. Assurance then tests that product. It should not invent a second truth.
| Weak public pack | Survives scrutiny |
|---|---|
| Date moved, cause vague | Cause linked to logic and evidence |
| Many metrics, no driver | Path to the public milestone |
| Soft completes | Done criteria matching the baseline |
| Private trackers | One official network and extracts |
| Optimism before the gate | Gate status with open prerequisites |
Public dates need public definitions
“Complete,” “ready for service,” and “open” must mean the same thing in the schedule, the business case and the announcement. If commissioning or handover criteria are missing from the network, the public date is a slogan sitting on construction percent complete.
The update rhythm that holds up later
- Hold one data date for schedule, cost and the assurance pack.
- Record out-of-sequence work and remaining duration honestly.
- Write the narrative after the file calculates.
- Keep period files so last month can be compared, not overwritten.
- Show instructed change separately from delivery variance.
What senior responsible owners should ask
Ask which milestone is public. Ask whether the path to it is still the path in the file. Ask what changed since the last approved baseline, and who approved absorbing that change. If those answers need three trackers, the report will not survive the next scrutiny cycle.
Controls that protect both money and dates
Schedule integrity protects time. Consistent earned value and change control protect the money story that sits beside time. Public programmes need both on the same data date. Separate worlds create separate excuses.
EVM Solutions supports government and public infrastructure programmes with planning, controls and reporting built for assurance: clear gates, comparable updates and a narrative that can be defended. If your public date cannot be explained from the last two period files, send them. Scrutiny is easier to pass when the evidence already exists.
