Integrated Project Delivery (IPD) is the most powerful — and most demanding — of the delivery models. Its multi-party relational contract, shared risk/reward pool, and collaborative governance pay off only when a project actually needs that collaboration. This article sets out the conditions under which IPD is the right call for a healthcare project, the conditions under which a lighter model is the better fit, and the trade-offs an owner accepts when choosing it.

IPD earns its overhead only when complexity and interdependence are high

IPD carries real setup cost: a negotiated multi-party agreement, an early-formed team paid before scope is fixed, a co-located big room, and the organizational change management to make shared governance work. That overhead is justified when the project is complex enough that tight, continuous collaboration prevents more waste than the structure costs.

A useful rule of thumb: the more interdependent the building systems and the more uncertain the program at the outset, the more IPD's continuous-collaboration model returns on its investment. Healthcare projects sit naturally at the high end of both axes:

• Systems interdependence — acute-care space stacks mechanical, electrical, plumbing, medical-gas (NFPA 99), low-voltage, structure, and specialized clinical equipment into tight floor-to-floor heights. A change in one trade cascades into the others. Continuous trade-partner coordination (which IPD institutionalizes) resolves these clashes earlier and cheaper than sequential design-bid-build.
• Program uncertainty — when clinical operations, equipment selections, or even the service-line mix are still being decided, the design must absorb change. IPD's early involvement of constructors and key trades lets the team price and absorb that change as it lands, rather than re-pricing through change orders.
• Regulatory density — FGI Guidelines space/clearance requirements, ASHRAE 170 ventilation, NFPA 101 life safety, NEC 517 (NFPA 70) health-care wiring, and AHJ/state plan review (e.g., HCAI/OSHPD in California, or the state department of health elsewhere) all constrain the design simultaneously. Having design, construction, and key trades solving these constraints together reduces the late surprises that drive rework.

Where complexity and uncertainty are both low — a straightforward fit-out, a repeat prototype, a tenant-improvement clinic with stable scope — the collaboration dividend is small and IPD's overhead is hard to recover.

The owner must be able and willing to participate, not just procure

IPD is not a model an owner can buy and step back from. The relational contract makes the owner a governing member of the project — typically a voting seat on the project management team and the senior management team — with continuous decision-making responsibility through design and construction.

IPD is a good fit when the owner organization can supply:

• An empowered, decisive owner's representative who can attend big-room sessions, make timely decisions, and bind the institution. Slow or ambiguous owner decisions starve the collaborative process and erode the very advantage IPD is meant to deliver.
• Real clinical-user engagement. Healthcare design lives or dies on input from the people who will work in the space — nurses, physicians, infection preventionists, facilities, sterile-processing, imaging, and biomed staff. IPD's integration of users into the team is a strength only if the institution actually frees those users to participate.
• Executive sponsorship for a relational, trust-based way of working. Shared risk/reward, open-book costs, and waived inter-party liability are a cultural shift. Without leadership backing, the organization tends to revert to adversarial, claims-oriented behavior the contract was designed to remove.

When the owner is set up to transact rather than collaborate — a thin project team, procurement-driven culture, a board that wants a fixed price before design begins — a more transactional model (DBB or CMAR) aligns better with how the institution actually behaves.

A capable, IPD-experienced market is a precondition, not a nice-to-have

IPD depends on a small set of partners who can operate inside a relational contract: open-book accounting, joint target-value design, profit placed at risk in a shared pool, and decision-by-consensus governance. That capability is unevenly distributed.

Favorable conditions:

• A local pool of architects, constructors, and key trade partners with genuine IPD experience (not just collaborative-sounding marketing). The estimating, cost-modeling, and BIM coordination discipline that IPD assumes is a learned competency.
• Sureties, insurers, and lenders comfortable with the structure. Multi-party agreements, waived liability among members, and (sometimes) project-specific or IPD-specific insurance products require a financing and bonding environment that will support them. Where the surety/insurance market resists, the structure gets watered down to the point of losing its value.