The success of a construction project delivered under a traditional model, such as a stipulated-price contract awarded to a general contractor under a design-bid-build approach, depends largely on having a complete and thorough design in place before the tender is issued. Contractors can then assess the scope of the work, evaluate the associated risks, and plan their schedule and construction methods accordingly before submitting a stipulated price.
However, when unexpected conditions arise on site, experience shows that the change management mechanisms built into lump-sum contracts can push the parties into an adversarial position—and derail the project in the process. In the event of a dispute, each party will attempt to convince the other party, or the consultant, of the merits of their position and the impact of the change on the contract schedule and price. Furthermore, a dispute may force one party to absorb some of the costs in the interim, which damages relationships and increases the likelihood of litigation.
Collaborative contracts, and in particular the Integrated Project Delivery (IPD) model outlined in the CCDC 30 standard form contract, offer a different approach. The central idea is to move away from the adversarial dynamic that (too) often characterizes traditional contracts, and to ensure that every party has a stake in the project’s success. In other words, if the project is completed on time and within budget, everyone reaps the rewards. Conversely, if the project fails, each party bears its share of the loss.
The IPD model achieves this by uniting the owner, consultants, and contractor as a single integrated team from the outset. Team members jointly plan and design the project, openly share information about the work ahead, identify potential issues and gaps, and collaborate to resolve them. They agree on a framework for sharing risks and rewards and commit to limiting legal disputes to a defined set of circumstances.
What is a collaborative construction contract?
The key difference in collaborative delivery models is how the project team is structured. Early in the process, the owner selects a team of consultants and contractors with whom they will collaborate on planning, design, constructability, and value optimization to meet the project’s budget, schedule, and quality objectives.
Broadly speaking, collaborative contracts are based on a few key elements:
- Integrated team: The main parties are involved from the project’s earliest stages. This allows risks to be identified early on, solutions to be proposed and the scope to be adjusted before costs are set in stone.
- Shared risks and rewards: The owner and the design-construction team share risks and gains, usually through a target price mechanism and a shared risk pool.
- Joint decision-making: Major decisions are made by shared governance bodies, with each party represented, to maximize the success of the project rather than the success of any one party.
- Open and transparent communication: The contracts include formal information-sharing obligations designed to reduce blind spots, misunderstandings and ultimately, legal disputes.
- Waiver of claims: Except in specified circumstances, the parties waive the right to pursue claims against one another for most issues arising from contract performance.
These are significant changes. Implementing a collaborative approach requires industry players to set aside their sometimes adversarial instincts and engage with the project as true partners in a spirit of transparency.
CCDC 30: The standard form IPD contract
The CCDC 30 is a standardized, multiparty contract developed by the Canadian Construction Documents Committee (CCDC) for projects delivered under the Integrated Project Delivery (IPD) model. It is designed for projects where the parties want to formalize a structured, collaborative approach with shared governance and a pricing structure based on cost reimbursement with a target price.
Under this model, multiple parties—the owner, the consultant, the contractor, and other IPD participants—enter into a single contract rather than a web of bilateral agreements. CCDC 30 addresses scope allocation, payments, changes, conflict management, termination, insurance and contract security, and liability allocation.
The pricing structure is cost plus with a target price. The design-construction team’s profits are allocated to a risk pool that remains at risk until mutually agreed upon project objectives are met. The contract also establishes the management structure for an IPD project, including the senior management team, project management team, and project implementation teams.
What does an IPD project look like in practice?
A project delivered under CCDC 30 is generally divided into four main phases, each with its own responsibilities and key decisions.
- Validation phase
In the validation phase, the project management team analyzes the site, technical data, and owner requirements. The team then prepares a validation report that establishes the base target cost, risk pool, project milestone schedule, and contract tasks matrix. This report must be approved by the owner. Until that approval is given, the parties retain the right to withdraw from the contract. - Design/procurement phase
The design/procurement phase begins once the validation report is approved. This phase is aimed at creating additional value through the optimization of systems, construction methods, life-cycle costs, and functionality. The team collaborates on design development, permitting, early procurement of critical items, and establishing the final target cost while updating the risk pool allocation. - Construction phase
Once the design has advanced sufficiently, a notice to proceed is issued and construction begins. The design/construction team completes the detailed design, retains subcontractors and suppliers, performs the work, and oversees testing, commissioning, and system startup. Then they deliver as-built drawings, manuals, warranties, and other required documents to the owner. At the end of this phase, the project management team must certify substantial performance, and an initial risk pool payout may be made. - Warranty phase
The warranty phase begins once substantial performance has been certified. The design/construction team corrects any deficiencies identified by the owner. A final inspection is conducted before the warranty period expires. The final risk pool payout is made once any outstanding deficiencies have been corrected.
Payment mechanisms, risk pool, and profits
The pricing structure for projects delivered under CCDC 30 is cost plus with a target price. In practice, the owner reimburses the design/construction team for all eligible actual costs—direct costs supported by documentation and certain indirect costs—according to the terms established by the project management team during the validation phase.
Each team member’s anticipated profits are allocated to a shared risk pool, which is funded in proportion to each party’s contribution. The pool remains at risk. If actual costs exceed the target price, the risk pool absorbs the difference. If savings are achieved, the pool may be distributed according to pre-established terms. Payouts are made at defined project milestones and at the close of the warranty phase based on collective performance.
This mechanism incentivizes the parties to optimize the project as a whole rather than maximize their individual margins while making the financial consequences of their decisions highly visible.
Waiver of claims between the parties
The CCDC 30 claims waiver stands out for how broadly it applies among IPD team members. Generally, the owner, consultant, contractor and other IPD participants waive the right to bring claims against one another for damages arising from the performance of the contract. However, there are certain defined exceptions.
These exceptions include claims related to a party’s wilful default, express warranty obligations, amounts due, and substantial defects or deficiencies that could not reasonably have been discovered before the end of the warranty phase. The contract also includes a waiver of indirect and consequential damages, such as lost profits, lost revenue, and lost business opportunities.
This waiver is designed to limit litigation between contracting parties and encourage the resolution of problems internally through the governance bodies established under the contract.
The role of technology: BIM and collaborative tools
Technology is essential to the collaborative approach. Building Information Modelling (BIM) provides a centralized platform where project data is updated in real time and accessible to all parties.
BIM allows for early detection of design clashes, scenario simulation, lifecycle cost analysis, and detailed progress tracking. This helps reduce errors, rework, and the risk of claims. When combined with project management software and cloud-based communication tools, BIM reinforces transparency and decision traceability, as well as the team’s ability to make informed decisions quickly.
Traditional contracts vs. the CCDC 30: Key differences
| Aspect | Traditional model (stipulated price, DBB) | CCDC 30 collaborative model (IPD) |
| Contract structure | Separate contracts between the owner, consultant, and contractor, creating multiple chains of liability. | A single, multiparty contract between the owner, consultant, contractor, and other key participants. |
| Risk allocation | Risks are largely transferred to the contractor, creating an inherently adversarial relationship. | Risks and rewards are shared through a target price and risk pool. |
| Pricing mechanism | Stipulated price or unit prices, with change orders for scope changes and unforeseen conditions. | A cost-plus contract with a target price, where the profits are placed at risk in a shared pool. |
| Claims and disputes | Potential for claims to multiply between parties when problems arise. | Mutual waiver of most claims among team members, with limited exceptions. |
| Governance | Segmented decision-making, siloed responsibilities, and communication that can operate in isolation. | Shared governance bodies (senior management team, project management team, and project implementation teams) and joint decision-making. |
| Project culture | Protection of contractual position and risk management primarily through transfer. | Collaboration, transparency, and team-based problem solving. |
Benefits, limitations, and questions to consider before using IPD
When properly implemented, a CCDC 30 collaborative contract can:
- bring the parties together as an integrated team, ensuring they all have a stake in the project’s success;
- drive optimization of planning and design;
- reduce unforeseen issues and problems during construction;
- reduce the number of claims; and
- foster better integration of constructability, operations, and maintenance considerations from the earliest project phases.
However, this delivery model is not right for every project. A stipulated-price contract may be the better fit for straightforward project types with limited technical complexity and a well-developed design.
Before opting for IPD, carefully assess the nature of the work and the project’s risk profile—particularly regarding planning, design, and execution—to determine if the project would benefit from a collaborative delivery model.
Early legal advice can help structure supplementary conditions, clarify roles, and establish governance processes that maximize the odds of success, whether the project is delivered under IPD or a traditional stipulated price model. Reach out to our Construction and Infrastructure team to discuss your options.
