The Contract Is the Biggest Risk on Your Project
After 20 years of watching infrastructure projects succeed and fail — across rail corridors in Ontario, highway rehabilitation programs for MTO, transit station delivery at Metrolinx, and now the Saudi construction market — I keep returning to the same conclusion: the single biggest factor in project outcome is how the parties agreed to work together before a single shovel hit the ground.
Not the engineering. Not the workforce. The contract. Specifically, whether the contract aligns the financial interests of all parties around a shared outcome, or pits them against each other in a zero-sum game that guarantees adversarial behaviour when risks materialize.
CMAR: Construction Manager at Risk
CMAR is the model I managed hands-on during the Bowmanville Train Line Extension — one of Canada’s largest progressive contract programs at $2 billion.
The mechanics are two-phased. In Phase 1, the owner selects a Construction Manager based on qualifications and fee — not lowest bid. The CM joins during design and contributes constructability reviews, cost estimating, value engineering, schedule development, risk identification, and procurement planning. This is where the value of early contractor involvement is created: field knowledge that shapes design decisions before they become expensive to change.
In Phase 2, when the design reaches sufficient maturity (typically 60-90% complete), the CM and owner negotiate a Guaranteed Maximum Price. The GMP is built on open-book cost data — the CM’s actual cost of the work, plus a fixed fee (typically 3-8%), plus shared contingency. If the project comes in under GMP, the savings are shared. If it exceeds GMP, the CM absorbs the overage. This pain/gain structure fundamentally realigns the contractor’s incentive — from maximizing change orders to finding efficiencies.
Alliance Contracting
Alliance contracting takes the collaborative principle further than CMAR. All parties — owner, designer, and contractor — operate as a single entity under a unified agreement with a shared risk/reward pool. There is no claims process. No disputes mechanism in the traditional sense. If the project loses money, everyone loses. If it makes money, everyone benefits.
Australia has the most mature Alliance contracting practice in the world, developed over three decades for complex infrastructure — remote resource projects, tunnels, bridges, and social infrastructure. The model produces exceptional outcomes when the parties are genuinely committed to the collaborative culture it requires. When they are not — when a party enters Alliance contracting with a traditional contractor mindset — the model fails spectacularly because there is no claims mechanism to fall back on.
Progressive Design-Build (PDB)
Traditional Design-Build selects a single entity (designer + contractor) on a competitive basis at a fixed price, giving the owner a single point of accountability for design and construction. PDB retains the single-entity accountability but changes the selection and pricing approach entirely.
Under PDB, the design-builder is selected on qualifications and approach — not price. Scope, design, and cost are then developed collaboratively between the owner and design-builder through a structured process, with the price not locking until the design is sufficiently mature to price reliably. This eliminates the design compression that characterizes traditional Design-Build, where the winning team is often selected before the design is developed enough to price accurately.
Early Contractor Involvement (ECI)
ECI is the most accessible entry point into progressive contracting for owners who are not yet ready for CMAR or Alliance. Under an ECI arrangement, the contractor is engaged under a separate preconstruction agreement — before the main construction contract is signed — to provide constructability input, cost advice, schedule development, and procurement planning.
The preconstruction agreement defines what the contractor will deliver, at what fee. At the conclusion of preconstruction, the owner decides whether to negotiate a construction contract with the ECI contractor or proceed to competitive tender. The knowledge developed during ECI informs whichever path is chosen.
Integrated Project Delivery (IPD)
IPD is the most ambitious and least widely adopted of the progressive models. It combines a multi-party contract — owner, designer, and contractor as parties to a single agreement — with financial incentives tied directly to project performance against shared targets.
Each party’s profit is at risk against the project’s performance. Exceptional performance produces shared gain. Poor performance produces shared pain. The alignment is total. So is the organizational and cultural commitment required to make it work.
IPD has seen its most successful adoption in healthcare construction in the United States, where the complexity of hospital delivery programs and the long-term owner relationships with design and construction partners create conditions the model needs. In infrastructure delivery, it remains emerging.
Choosing the Right Model
The question I am most often asked is: which progressive model should I use? The answer is always: it depends on your project, your organization, and your market conditions. None of these models is universally superior. Each requires specific conditions to perform. The coming weeks will develop a framework for making that choice in the GCC context.