Permission to Play: Before the First Shovel Hits the Ground
- Audiit
- Mar 4
- 7 min read
How Canadian Infrastructure Projects Win or Bleed
At 6:12 a.m., the superintendent is already on site, looking at a crew that’s ready to work - but not sure what they’re working on first because the latest drawing revision never made it into the site package. At 9:08 a.m., the project controls lead is trying to reconcile three “current” schedules - each with different logic, different percent completes, and a different story about float. At 4:41 p.m., an executive reads one line in a project brief and feels the blood drain from their face: “Owner is requesting supporting schedule change rationale with the next update.”
That moment, when the conversation shifts from “we’ll catch up” to “prove it,” is where many infrastructure projects quietly cross from the winning side to the losing side.
Because in modern Canadian infrastructure delivery, the schedule and the records aren’t just planning tools. They’re contract artifacts. They’re cash-flow levers. And increasingly, they’re the difference between an issue being a manageable change order or a reputational, legal, and financial event.
The uncomfortable truth: most megaprojects don’t fail with a bang - they drift
Industry research keeps repeating the same message: big projects routinely miss cost and schedule expectations, often by uncomfortable margins. McKinsey has cited research estimating that 98% of megaprojects suffer cost overruns greater than 30%, and 77% are at least 40% late - a brutal baseline for anyone who thinks “we’ll figure it out later” is a strategy.
Bent Flyvbjerg’s work on megaproject performance highlights another recurring pattern: misinformation (or self-delusion) about costs, schedules, and risks is a root cause of overruns and delays - meaning the failure often starts as a narrative problem long before it becomes a construction problem.
“Permission to play” is no longer just about pre-qualification - it’s about proof.
A growing number of owners and agencies treat schedule discipline and documentation as non-negotiable. Some bid and contract environments now expect not just a schedule update, but a history of changes and supporting narratives. The audit trail shows whether your plan is stable, logical, and credible over time.
Plain-English translation: If you can’t explain your schedule changes, you can’t control your risk. And if you can’t control your risk, the market will price you accordingly - or screen you out entirely.
What “good” looks like on Canadian infrastructure projects
Good doesn’t mean “no problems.” It means issues surface early, are quantified quickly, and are resolved with a defensible record. Here’s what best-in-class delivery tends to look like across the project lifecycle:
1) A contract-grade baseline (not a “nice-to-have” Critical Path Method (CPM) file)
Contract-grade baseline schedule: logic-driven, realistic, aligned to procurement and access constraints.
Resource profile/histogram supports the baseline: planned crews/equipment are realistic and sufficient to hit milestones (peaks and assumptions documented).
The Work Breakdown Structure (WBS) aligns with the scope, estimates, procurement, and construction packages.
Constraints are visible and justified (permits, utility relocations, material lead times).
2) Change control that connects field reality to commercial reality
Request for Information (RFIs), design revisions, access constraints, and utility conflicts are tied to schedule impacts as they happen - not months later.
Every schedule revision has a rationale, and impacts are traceable to events.
Rolling 3-4-week lookahead (field plan) updated weekly and tied back to the schedule of record; constraints and crew commitments are captured and escalated.
If time is impacted, notice and Extension of Time (EOT) requests follow the contract procedure - supported by time impact analysis and contemporaneous evidence.
3) Subcontractor integration is engineered, not hoped for
Infrastructure projects don’t get delayed by “the schedule.” They get delayed when trade partners and systems vendors are working on conflicting plans, and nobody owns the integration story. (If that sounds familiar, keep reading - because a Canadian inquiry spelled out exactly how that ends.)
4) Records are treated like project assets
Meeting minutes, directives, notices, daily reports, submittals, inspection results, and correspondence are not “project noise.” They’re the evidence layer that protects:
entitlement (time and cost), cash flow, and credibility.
In practice, that evidence layer becomes the monthly controls package that owners, contract administrators, and (if it comes to it) adjudicators actually read:
Schedule update of record (versioned) plus a plain-English narrative: what changed, why, and what moved on the critical path.
Schedule change log (milestone moves, plus reasons, plus supporting references).
Planned vs actual plus variance reporting (schedule/cost and earned value, where used).
What “not so good” looks like (the slow drift you feel… before you can prove it)
This is the danger zone: the project is still moving, but the management system is lying - often unintentionally. Updates happen late, are rushed, and logic breaks quietly. Forecast dates “improve” without any corresponding recovery plan. Schedules are revised, but nobody can clearly explain why - or what changed in the critical path. The project team relies on email and spreadsheets to track obligations and decisions. The claims strategy becomes “we’ll reconstruct the story later.” That last one is where a lot of Canadian projects get hurt - because Canadian construction law is increasingly built to move disputes faster.
What failure looks like in Canada: when the law and the contract take over
Failure isn’t only a blown budget. In infrastructure, failure is often the moment your project loses legal defensibility. In Ontario, the Construction Act has made “speed” a feature of dispute resolution. Ontario’s Bill 216 received Royal Assent in 2024 (Statutes of Ontario 2024, chapter 20) and amended the Construction Act in multiple ways, including changes touching prompt payment and adjudication.
A key shift for infrastructure teams: adjudication is more accessible, and the window to start it is longer. Bill 216’s explanatory notes describe changes that, among other things, broaden adjudication availability and introduce 90 days to refer a dispute tied to completion/abandonment/termination triggers (unless parties agree otherwise).
Plain-English translation: Your dispute may not be “over” when the work is done. If your closeout mindset is “archive the mess,” you’re walking into adjudication or litigation without armour.
Deadlines in construction law are unforgiving
Ontario construction lien rules revolve around strict time triggers - miss them and rights can expire. Bill 216’s explanatory notes point to lien expiry timing linked to the “60th day” after certain triggers.
Notice deadlines can be just as unforgiving. Many contracts require written notice within a defined window to preserve entitlement - including Extension of Time (EOT) requests and delay claims.
Plain-English translation: If your project records aren’t organized around triggers, notices, and dates - including lien deadlines and EOT notice windows - you’re not just messy - you’re exposed.
Contract modernization is also raising the bar on clarity
The Government of Canada, through Public Services and Procurement Canada (PSPC), has been modernizing solicitation and contractual documentation. As of June 2024, PSPC solicitations follow a modernized approach under the Contract Modernization Initiative, with an intent to expand this approach across Government of Canada solicitations over time.
For construction, PSPC notes that the modernized contract model is not yet available - but the modernization direction still signals a broader market expectation: clear obligations, clearer enforcement, and fewer places to hide behind ambiguity.
Real Canadian examples: what winning looks like vs. what losing costs
Winning example: Canada Line (Vancouver) - schedule and budget credibility becomes reputational capital
In 2009, the Government of Canada’s announcement about Canada Line service included a quote stating the project was completed ahead of schedule and within budget. That “ahead of schedule, within budget” line is more than a brag. It’s a business outcome:
stronger public trust, easier stakeholder alignment, and a track record that reduces friction on future work.
Losing example: Ottawa LRT (Stage 1) - when integration and schedule credibility collapse
The Ottawa Light Rail Transit (LRT) Public Inquiry’s Executive Summary and Recommendations described a system handed over after a delay of approximately 16 months, with reliability issues and derailments, followed by multimillion-dollar litigation.
It also highlighted integration problems, including subcontractors working to conflicting schedules. It criticized the practice of communicating dates with no realistic hope of achieving them - a credibility failure that amplified public frustration and pressure.
In other words, when owners, primes, vendors, and operators aren’t aligned - and when schedule messaging becomes storytelling instead of forecasting - the project doesn’t just slip. It loses trust. And trust is expensive to buy back.
A 2026 reminder in Ontario: the Eglinton Crosstown finally opens
Ontario announced that the Eglinton Crosstown LRT would begin operating under the Toronto Transit Commission (TTC) on February 8, 2026, and TTC service information reflects a phased opening.
This is not a comment on any one party’s performance. It’s a market reminder: when opening dates repeatedly move, schedule credibility becomes a public and political asset - not just a project management detail.
The business upside of doing it right
When infrastructure organizations approach projects “correctly” (technically, commercially, and legally), the benefits compound:
Financial: fewer rework cycles, fewer disputed changes, more predictable cash flow, and reduced claims costs.
Commercial: higher win rates because owners trust your controls, not just your price.
Reputational: confidence with lenders, regulators, partners, and the public.
Operational: faster decision cycles because the “single source of truth” actually exists.
Strategic: the ability to scale a portfolio without scaling chaos.
The damages when you don’t: what to expect when corners get cut
This is what organizations typically absorb when best practices, statutory requirements, or contract obligations aren’t met:
Liquidated damages and back-charges (where applicable)
Withheld payments / delayed payments because documentation is deficient
Adjudication/litigation costs and management distraction
Lost lien rights and lost leverage (if deadlines aren’t managed)
Rework and safety exposure when “schedule pressure” overrides quality control
Reputational damage that reduces future bid competitiveness
How Audiit helps you move from the losing side to the winning side
Audiit’s value isn’t “more project management.” It’s project delivery confidence - turning schedules, commercial obligations, and records into a defensible system that works at project, program, and portfolio scale.
What that looks like in practice
Schedule Change Log + version history so every update has a traceable rationale (not tribal memory).
Baseline integrity plus resource profile/histogram so the schedule is buildable, not just logical.
Contract obligation and notice/EOT tracking tied to real project events (not inbox archaeology).
Record retention that’s adjudication-ready: organized, searchable, time-stamped, and consistent.
Planned vs actual plus variance reporting (schedule/cost and earned value, where used) so leadership sees drift early and disputes resolve faster.
Portfolio visibility, Enterprise Project Portfolio Management (EPPM), so executives see early risk signals before the market.
Leading a portfolio with recurring overruns?
Book a working session with Audiit on EPPM governance + project controls standardization.
Comments