The pattern is familiar. A project is approved with a budget and a contingency. Updates are routine, or occasional. Then a report arrives explaining that costs have risen, contingency has been used, and council is asked to approve additional funding.
Nothing in that report is necessarily wrong. But it is the first time council has seen the problem, and the choices left are narrow: approve the money, cut scope late, or stop a project that is already half built.
The issue is rarely the quality of the people preparing the report. It is what the report is designed to show, and what triggers it.
What one recent review found
In July 2026, KPMG completed a capital project delivery review for the Town of The Blue Mountains in Ontario, presented to council as staff report ADM.26.054. Several of its findings describe a pattern many municipalities will recognize.
- Council updates “were generally prompted once the project required additional funding.”
- Council approvals “were tied to budget and funding instead of stage-gate controls or predefined reporting thresholds.”
- The program “did not have a structured change control process.”
The review recommended a consistent portfolio dashboard showing approved budget, projected final cost, variance, contingency and schedule status, along with escalation thresholds for cost, schedule, risk and contingency. The Town’s staff have said they plan to build these into a capital project reporting framework.
Commissioning that kind of review and publishing it is good governance. The findings are useful precisely because they are common.
Why updates arrive late
They are triggered by money, not by signals
If the only defined reason to go back to council is a funding request, that is when council will hear about the project. Early signs, such as contingency being used faster than work is completed, or a key milestone moving, do not have a path to council of their own.
They report what has been approved, not what is committed
Most updates show the budget, the costs to date and the contingency remaining after approved changes. As Vantage Signal has written, that contingency balance can be accurate and still overstate what is available, because change directives, pending change requests and expected changes have already committed money that the approved total does not yet show.
They describe a project that has already moved on
Reports are prepared to a cutoff date and reach council weeks later. Vantage Signal’s preliminary research on Canadian municipal capital reporting observed intervals of 29 to 64 days between a report’s information cutoff and its public review.
A report triggered by a funding request will always arrive after the decisions that created the need for it.
What a useful update shows
The Government Finance Officers Association’s best practice on capital project monitoring and reporting recommends comparing actual results with the project plan, including percent of the project completed against percent of the budget spent, contract time used, progress on key milestones, and highlighting significant changes to scope, cost, schedule or funding. In practice, a one-page update per major project can cover:
- Projected final cost: against the approved budget, not only costs to date
- Contingency: shown as both the balance after approved changes and the position after work already in motion
- Progress against spending: percent complete next to percent of budget spent
- Schedule: the baseline and current dates for the milestones that matter to the public
- Open changes: change directives, pending change requests and their expected value
- Top risks: each with an owner and what would trigger it
- The next decision: what council may be asked to decide, and roughly when
What it looks like
| Community recreation centre | Approved | Current |
|---|---|---|
| Project budget / projected final cost | $12.0M | $12.0M |
| Contingency balance (after approved changes) | $800K | $490K |
| Contingency position (after work in motion) | $800K | $190K |
| Percent complete / percent of budget spent | 55% / 61% | |
| Substantial completion | Jun 2027 | Sep 2027, under review |
| Open change directives and change requests | 7 items, ~$240K | |
| Next council decision | Possible budget amendment, Q2 2027 |
Set the thresholds before they are needed
Escalation thresholds turn “we’ll report if something comes up” into a rule everyone knows in advance. They should be set when the project is approved, scaled to its size and risk, and written down. Examples of the kind of trigger a municipality might choose:
- projected final cost moves more than a set percentage or dollar amount above the approved budget
- contingency position falls below a set share of the original contingency before a set point in the work
- percent of budget spent runs ahead of percent complete by more than a set margin
- a public-facing milestone, such as an opening date, moves by more than a set number of weeks
- a change, or a group of related changes, exceeds the authority delegated to staff
The right numbers vary by municipality and project. The point is that they exist, and that crossing one sends an update to council whether or not a funding request is ready.
Questions council members can ask at the next update
- What is the projected final cost, not only the cost to date?
- How much contingency is left after the changes already in motion?
- Is spending ahead of progress, and by how much?
- Which milestones have moved since the last update?
- What would cause staff to come back to us before the next scheduled update?
Earlier, not just more often
Vantage reads change logs, progress claims, cost reports, schedules and meeting minutes together, and produces council-ready updates that show projected cost, contingency position, schedule movement and open changes, with every figure traced to the record it came from and reviewed by an analyst. Thresholds agreed with staff flag when an update should go to council.
It does not replace staff reporting or make decisions for council. It gives staff the reconciled view they need to report early, while council still has options.
Because the most useful update is the one that arrives before the funding request.
Sources
- 1. KPMG, “Capital Project Delivery Review,” Town of The Blue Mountains, July 7, 2026, attached to staff report ADM.26.054, July 13, 2026. https://www.thebluemountains.ca/sites/default/files/2026-07/ADM-26-054-KPMG-Capital-Project-Delivery-Review.pdf
- 2. Government Finance Officers Association, “Capital Project Monitoring and Reporting,” best practice, approved 2007, updated 2017. https://gfoa.org/materials/capital-project-monitoring-and-reporting
- 3. Vantage Signal, “The Contingency Balance Is Not the Contingency Position.” https://www.vantagecri.com/resources/contingency-balance-position
- 4. Vantage Signal, “Is the Project Still Where the Report Says It Is?” https://www.vantagecri.com/signal/data/information-currency-public-capital-projects