Governance Scenario
Standard 1.1 · Financial Oversight and Accountability
The Project Nobody Flagged
By Synnovate · Published 2026 · Governance Scenario
The Situation
The athletics facility had been approved at $4.2 million. The latest report to the board showed costs at $4.1 million - on track. What the report did not show was that two significant scope changes had been agreed at site level, that the contingency fund had been drawn down to 12% of its original value, and that the head of operations had sent three emails in the previous month asking for guidance that had not been formally replied to.
The chair found out at a community event, from a parent who sat on the building committee. The figure she heard was $5.7 million.
The room where the board next met was not a comfortable one. Nobody had lied. Nobody had hidden anything deliberately. But the board had been reporting on a project that was no longer the project it had approved.
Provocations
- "A board that only knows what it is shown cannot govern what it cannot see."
- "Reporting systems that track budget against original approval miss the most important question: is the scope still what was approved?"
- "The gap between what a project manager reports and what a chair hears at a community event is always a governance gap."
- "Contingency funds drawn down in silence represent risk transferred without consent."
Considerations
Capital projects create specific governance challenges that routine financial oversight is not designed to catch. The board approved a budget. The project is delivering within that budget - technically. But the scope has changed and the risk profile has shifted substantially without the board being asked to consider it.
Budget-against-approval reporting tells the board whether the project is spending within limits. It does not tell the board whether the project being built is still the project that was approved. These are different questions, and only one of them is typically asked.
Good capital project oversight requires regular reporting on scope, not just cost. Every change to what is being built should be treated as a governance decision. The threshold for escalation should be defined at the outset: any scope change above a certain value, or any drawdown of contingency below a certain level, triggers a formal board conversation.
The unanswered emails from the head of operations are worth examining. When people in operational roles stop receiving responses to risk-related questions, they often stop raising them. The silence becomes the governance.
Platforms like Loom provide structure for attaching project communications and scope change records to board documents, so trustees have the full picture - not just the summary. The gap between what the board knew and what the chair heard at a community event was entirely avoidable.