Progressive Design-Build Is Having a Moment. The Contract Still Matters.

There is a reason progressive design-build is getting so much attention in Canada right now. 

Traditional project delivery asks parties to make some of their biggest commitments when they know the least about the project. Scope is still developing. Design questions remain unresolved. Pricing assumptions are being made. Risks are being allocated before everyone fully understands what those risks will look like in practice. 

Progressive design-build tries to change that. 

The Canadian Construction Documents Committee has now formally entered the conversation with the release of CCDC 32 – 2026 Progressive Design-Build Contract, the first standardized CCDC contract for this delivery model. It is accompanied by CCDC 33, which governs the relationship between the design-builder and its consultant.   

The significance is bigger than two new contract forms. 

Progressive design-build reflects a broader shift in how the industry is thinking about project risk: what if the parties spent more time understanding the project together before locking themselves into the price and risk allocation that will govern construction? 

What actually makes it “progressive”?

Under CCDC 32, the project is divided into two phases. 

During the first phase, the owner and design-builder work through project development. The design-builder develops the design and performs other project-development services before committing to a stipulated price for completion of the project in Phase 2.   

That distinction matters. 

In a traditional design-build arrangement, much of the commercial bargain is established at the outset. Progressive design-build deliberately postpones some of that commitment so the parties can develop the project together first. 

Design can advance. The owner’s requirements can become clearer. Costs can be tested. Schedule assumptions can be examined. Risks that looked theoretical during procurement can become much more concrete. 

Only then does the project reach the point where the parties decide whether they are prepared to move into the construction phase. 

CCDC’s own materials describe mechanisms including project gates, early works and “off-ramps,” with the Final Project Proposal playing a critical role in determining the transition between project development and construction.   

There is an obvious attraction to that model. 

There is also an important misconception to avoid. 

Collaboration doesn’t eliminate risk 

A more collaborative delivery model does not mean the contract becomes less important. 

Arguably, it becomes more important. 

Progressive design-build changes when important decisions are made, but the parties still need to know how those decisions will be made, who is responsible for what happens during the development phase, how early work is authorized, how costs are treated, what information the owner must provide, what happens when assumptions change, and what happens if the parties cannot ultimately agree on the Final Project Proposal. 

That last point deserves particular attention. 

The entire model anticipates that the parties may spend significant time and money developing a project together before the final construction bargain is settled. If they cannot reach that bargain, everyone needs to understand the consequences. 

What gets paid? 

Who owns or can use the design? 

What happens to work already procured or performed? 

What obligations survive? 

Can the owner take the developed project elsewhere? 

Those aren’t peripheral legal questions. They are part of the commercial architecture of the delivery model. 

Other Canadian construction-law commentary on the newly released form has similarly noted that CCDC 32 provides a standardized starting point, but does not remove the need for parties to confront difficult commercial issues or consider project-specific supplementary conditions.   

The contract needs to match the behaviour 

There is another risk with collaborative contracting that has less to do with the form itself. 

You cannot put a collaborative contract around a project and assume the project will become collaborative. 

The people administering it still matter. 

If information is withheld, decisions are delayed, budgets are treated defensively, risk registers become exercises in protecting positions, or the parties revert to traditional adversarial behaviour as soon as something goes wrong, the promise of the delivery model begins to disappear. 

That is why progressive design-build requires more than selecting CCDC 32 during procurement. 

It requires the owner, design-builder, consultants and project team to understand the model they have actually agreed to administer. 

The contract needs to be reflected in the project’s decision-making, documentation, communication and governance from the beginning. 

Why this matters now 

The release of CCDC 32 is significant because standardization makes progressive design-build more accessible. 

Until now, Canadian parties interested in progressive design-build have often had to create heavily bespoke contractual frameworks. A recognized CCDC form gives the industry a common starting point and common language. 

And there is clearly interest. CCDC describes progressive design-build as growing in popularity and added additional 2026 seminars after demand for its initial sessions. Industry reporting on the national CCDC roadshow similarly described strong attendance as owners, contractors, consultants and other stakeholders sought to understand the new model.   

That doesn’t mean every project should become progressive design-build. 

It does mean owners, contractors and consultants should understand why the model is gaining traction and what changes when they use it. 

The most interesting part of progressive design-build isn’t that price is established later. 

It’s the idea behind it: some project risks are better understood before they are allocated. 

Giving the project team an opportunity to develop the design, test assumptions and understand risk before making the final construction commitment can create a much better foundation for the project. 

But the value of that process depends on the contract actually supporting it, and on the people administering the contract understanding what they agreed to do. 

Progressive design-build gives the parties more room to figure things out together. What they do with that room is what will determine whether the model actually works. 

This publication has been prepared for general information only and does not constitute legal advice or create a solicitor-client relationship. No reader should act or refrain from acting on the basis of any information included herein without seeking appropriate legal or other professional advice based on their particular circumstances. LEGALLY BUILT accepts no responsibility for any loss or damage that may arise from reliance on the information contained in this publication.