All news

Projects

Ontario's Move to Alliances and Progressive Design-Build Changes How Delay Is Attributed

The province's largest programs are being let as alliances and target-price progressive design-build rather than fixed-price P3s, shifting the question from who caused the delay to how the parties agreed to share it.

September 4, 2026 · Ontario, Canada

The delivery model on Ontario's major transit work shifted decisively through 2026. Metrolinx signed a target price agreement of roughly $4.32 billion for the Ontario Line's Pape tunnel and underground stations under a progressive design-build structure. Infrastructure Ontario closed the Yonge North Subway Extension stations, rail and systems procurement as an owner-formed alliance across three packages, drawing eleven submissions, with award expected in 2027. GO Expansion civil work is now being let through alliance contracts. On the Hazel McCallion Line, an existing fixed-price P3 was restructured mid-build into an alliance for the remaining construction, which the parties describe as resolving their commercial disputes.

That is a real transfer of risk back to the public owner, and it changes the shape of a delay analysis. Under a fixed-price contract the question is largely who caused the delay and whether notice was given. Under an alliance or a target-price arrangement, entitlement runs through an agreed cost model, a pain and gain share, and gates at the end of a development phase. Delay still has to be measured, but the measurement feeds a commercial mechanism rather than a claim against a counterparty.

Two consequences follow. The records that matter expand: open-book cost data, development phase deliverables and gate decisions join the schedule as part of the evidentiary record. And separating packages — particularly where design and systems integration sits in a commercial package of its own — creates interface risk between alliance participants that nobody's fixed price absorbs.

These models reward the same controls discipline as any other, applied earlier. The integrated schedule, the interface register and the change record have to exist during the development phase, because that is when the target price is being set.

What we recommend

  • Build the integrated schedule and interface register during the development phase, before target price is agreed.
  • Treat open-book cost data and gate decisions as part of the delay record.
  • Assign an owner and a date to every interface between alliance participants.

Commentary prepared by Elite Analytics Inc. for general information. It is not legal advice.

Contact

Have a project, a schedule or a claim to talk through?

Tell us what stage you are at. We will tell you plainly what the records support and what we would do next.