IPD Advice from Owners

IPD Explained: How Lean Teams Do It Differently

Integrated Project Delivery is gaining momentum among owners, contractors, and design teams who have experienced the consistent failures of traditional delivery and are looking for a model that actually aligns how the team is structured with how a project needs to be built. The premise of IPD is straightforward: bring the owner, designer, and builder into a single contract, align their financial interests around the project’s success, and create the conditions under which genuine collaboration can produce the outcomes that adversarial contracting reliably prevents.

The full definition that captures what IPD actually is: a delivery model using a single contract for design and construction with a shared risk and reward model, guaranteed costs, waivers of liability between team members, an operating system based on Lean principles, and a collaborative culture. It is often called Lean IPD to make explicit the inseparable connection between the contract structure and the Lean operating system that makes the contract structure productive.

This blog focuses on the contract, the structural foundation that makes everything else possible and on what each of its key components actually means in practice.

The Contract as Foundation

Traditional project delivery separates parties into independent entities, each responsible for their own scope, each financially motivated to protect their own margin, and each legally structured to transfer risk to someone else when things go wrong. That structure produces the behaviors it was designed to produce: siloed decision-making, protective documentation, reluctance to share information, and the defensive posture that makes genuine collaboration nearly impossible.

The IPD agreement starts from a different assumption: that the owner, designer, and builder succeed or fail together. The contract makes that assumption legally and financially real by tying them to a single dollar value with shared financial consequences. When the project wins, every party in the agreement wins. When it loses, every party bears the cost. That alignment converts the rational strategy from self-protection to collective problem-solving.

The Signatories

The IPD agreement is always signed by at least three parties: the owner, the lead designer, and the lead builder. Some owners bring additional design and trade partners into the agreement as primary signatories creating what is called a poly-party agreement while others keep the three-party structure and incorporate the Lean IPD principles into subcontracts that tie those parties to the terms of the master agreement.

A subset of the participating designers and trade contractors will agree to put their profit at risk alongside the primary signatories. These are the risk-and-reward partners, the firms whose financial outcome is directly tied to the project’s overall performance. Other trades and consultants are brought in through more traditional subcontract structures, negotiated or bid once the design is substantially complete, and paid on lump sum or time-and-material bases without the profit-at-risk component.

The distinction between risk-and-reward partners and traditional subcontractors is significant because it determines which firms have a direct financial stake in the project’s overall success. The firms that put their profit at risk are the ones who are most directly aligned with the owner’s interests and the ones most motivated to make the collaborative operating system work.

Shared Risk and Reward

The risk and reward mechanism is the financial engine of IPD. Risk-and-reward partners agree to have their costs guaranteed, they will not lose money and their profit fixed as a lump sum at the time the contract amount is negotiated. That fixed profit is then placed at risk based on the project’s financial and schedule outcomes.

If the project exceeds its budget, the risk-and-reward partners may lose some or all of their fixed profit. If all profit is lost, the owner pays at cost, covering direct labor, materials, and overhead, though sometimes with a cap so that participating firms absorb the opportunity cost of delivering the project without profit, but do not lose money. This is the protection that makes genuine risk-sharing possible rather than just risk transfer in the other direction.

If the project is delivered below its financial targets, every risk-and-reward partner receives their full fixed profit and shares in the savings. A negotiated percentage of those savings returns to the owner; the remainder is distributed among the participating firms proportionally. The better the project performs, the better every firm in the risk-and-reward pool performs. The incentive is collective and it is real.

Billing under this structure is transparent and verifiable. Design firm billing rates are separated into direct cost, overhead, and profit components typically calculated as a multiple of direct labor cost. Construction firm billings cover labor, materials, and subcontracts at direct cost plus overhead and profit percentages. All rates and overhead are subject to audit by an independent firm, which on larger projects is a significant undertaking. That audit requirement is one of the mechanisms that builds the transparency the model depends on, not because it produces trust, but because it verifies trustworthiness.

The Contract Amount and the Shared Contingency

The contract amount includes costs for design, construction, and a shared contingency that belongs to the team rather than to any individual party. The existence of a shared contingency is one of the most practically significant differences between IPD and conventional delivery. In a conventional contract, contingency belongs to whoever carries it and there is an incentive to protect it rather than deploy it collaboratively to solve problems. In an IPD agreement, contingency belongs to the project, and the team’s shared interest in project success creates the conditions under which contingency is used when and where it actually helps the project rather than when it protects an individual party’s exposure.

The Leadership Team

The IPD agreement defines a joint leadership structure called the Core Group or Project Management Team depending on the agreement form, that is responsible for delivering the project on time, on budget, and at the quality the owner requires. This leadership team includes representatives from the owner, the lead designer, and the lead builder, and may include user representatives or other risk-and-reward partners.

The joint leadership structure is one of the places where IPD is most different from conventional delivery. In a CM-at-risk or design-bid-build project, the contractor manages the project. In IPD, the project is jointly managed by parties whose financial interests are aligned to the same outcome. Decisions that would generate disputes in a conventional structure, scope transfer between firms, acceleration of one scope to protect another, value engineering that affects multiple parties are made collaboratively by people who share both the risk and the reward of getting them right.

Here are the specific barriers to collaboration that the IPD contract structure removes:

• Back charges between risk-and-reward partners are eliminated, the firms are on the same financial team.
• Scope can transfer between firms based on who can most cost-effectively deliver the work, without triggering contractual conflict.
• The traditional incentive to protect individual margin by withholding information or avoiding risk disappears when everyone’s margin is tied to the same outcome.
• Liability claims between team members are waived, removing the defensive documentation culture that consumes enormous project energy in conventional delivery.

The Contract Is Only the Beginning

The IPD agreement is a major structural improvement over conventional contracting. It is also only one of three components of genuine Integrated Project Delivery. The contract aligns incentives. It does not automatically produce the collaborative behaviors, the efficient operating processes, or the culture of trust and vulnerability that make those aligned incentives productive.

The Lean operating system, the Last Planner System, co-location, set-based design, A3 thinking, BIM, plus/delta improvement cycles is what provides the processes and tools through which the aligned team works efficiently. The collaborative culture is what determines whether those processes are practiced genuinely or performed superficially. All three components, the contract, the operating system, and the culture must work together for IPD to deliver what it promises.

At Elevate Construction, the consulting engagement model reflects exactly this three-part structure. The alignment work establishes the shared goals and operating agreements. The production system design provides the processes and tools. And the ongoing stabilization work builds the culture that makes the processes real. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The contract is where IPD starts. It is not where it ends.

On we go.

Frequently Asked Questions

What is Integrated Project Delivery and how is it different from conventional delivery?

IPD is a delivery model that uses a single contract for design and construction with shared risk and reward among the owner, designer, and builder. Unlike conventional delivery where each party is financially motivated to protect their own margin, IPD aligns all parties to the same financial outcome creating conditions where genuine collaboration is rational rather than aspirational.

Who are risk-and-reward partners in an IPD agreement?

Designers and trade contractors who agree to put their profit at risk in exchange for cost guarantees and a share of project savings. Their financial outcome is tied to the project’s overall performance, which aligns them directly with the owner’s interest in delivering the project on time, on budget, and at the required quality.

What happens if an IPD project exceeds its budget?

Risk-and-reward partners may lose some or all of their fixed profit. If all profit is lost, the owner pays for the project at cost covering direct labor, materials, and overhead so that firms do not lose money but absorb the opportunity cost of delivering a project without profit.

What is the shared contingency and why does it matter?

The shared contingency belongs to the project team rather than to any individual party. This removes the conventional incentive to protect contingency and creates conditions where it is deployed collaboratively to solve problems wherever they arise, rather than held in reserve for individual exposure.

Why is the IPD contract insufficient on its own to produce collaborative outcomes?

Because aligning incentives creates motivation to collaborate but does not produce the specific behaviors, processes, and culture that collaboration requires. The Lean operating system provides the processes; the collaborative culture provides the environment in which those processes actually work.