
January 7, 2026


Integrated project delivery (IPD) promises all the things that multi-GC construction projects need.
Better alignment, fewer surprises, and shared accountability.
But, in practice, many IPD projects fall short of that promise. Not because the method itself is broken; it’s because few have the technical systems to support IPD.
This guide will break down the integrated project delivery methodology: what it is, who it’s best suited for, how it’s commonly implemented, and how joint ventures can set up an IPD project that’s successful and sustainable.
Integrated Project Delivery, a methodology spearheaded by Lean Construction, is a project delivery approach where the owner, architect, contractor, and trade partner enter into a single, multi-party agreement.
Instead of optimizing single contracts, it’s a shared system of:
The whole idea is to replace clunky handoffs with early collaboration, especially during preconstruction when design decisions have the greatest cost impact.
In traditional delivery models (design-bid-build, CM at risk, and even many design-build arrangements), misalignment is structurally embedded.
Designs progress before cost is fully understood, contractors price risk late, and owners absorb the consequences. Each party may be acting logically on their own, but it’s a team effort, and without shared visibility and accountability, the system fails.
James Pease, the VP of UCSF Health Capital Projects, say this very issue resulted in over $50M dollars in inconsistencies, double-ups, and unnecessary items for his capital projects.
“On large projects, where we’re compiling estimates from over 100 different companies, consolidating everything into one system is a nightmare," James says.
IPD removes the isolation because design, estimating, and constructability advance together.
For joint ventures specifically, this shift is significant. Key trade work is looped in early, project data is shared, and cost validation happens as the design develops.
Integrated project delivery is a methodology built for projects where misalignment would be especially costly, such as:
The joint venture piece is especially significant.
The average cost overruns of megaprojects involving multiple GCs is around 80%, with schedule slippages of 20 months.
These ghastly numbers aren’t by a single bad decision or even a lack of effort on the part of folks involved. They’re caused by all the fragments that come with outdated methods.
IPD gives JV teams a new way out…
It’s another Monday, but for an IPD partner it doesn’t start with reconciling spreadsheets. They revisit their shared cost model, agreed upon assumptions, and project targets with confidence that it’s aligned with all the folks at different firms. (How refreshing!)
In practice, here’s how it works.
Under IPD, JV partners agree to develop and maintain a single, shared cost model during preconstruction; rather than each firm carrying its own estimate and reconciling differences later.
What this looks like in practice:
This alone eliminates a major source of friction in JV projects: late discovery that partners were pricing the same scope differently.
Jennie Dorcy, a preconstruction solutions engineer with years of experience filing lien claims, says it best: “Payment crises don’t start with a bad check. They start with ambiguous scopes and speculative contingencies.”
IPD is designed to prevent exactly that: assessing risk early.
What it looks like:
IPDs create clear guard rails: who decides what, when, and with whose input during preconstruction. This helps you from defaulting to the loudest or most risk-averse partner in the room.
Effective IPD JVs establish:
Pro tip: Using a cloud-based preconstruction platform over a desktop tool is the ultimate collaboration hack.
In many projects, key trades don’t meaningfully weigh in until pricing is already underway.
In an IPD model, trade partners are brought in while the design is still taking shape. They review layouts and are given the opportunity to flag constructability issues before drawings are finalized.
Instead of estimating based on assumptions, trades price work based on how they would actually build it.
So, now you want to integrate IPD on your next project.
It can start to be implemented in part or in whole (any effort towards more collaboration early is a good start!) but, at Ediphi, we’ve built a platform that can get you all the way there on your next project.
Here are the key features you can use.
The entire point of integrated project delivery is early and easy collaboration. This is what the cloud does for you.
A real life example: Hensel Phelp’s precon runs through the cloud and a senior estimator on their team tells us that he finds himself opening his estimate multiple times a day to add bits of detail as they come up; something he was never able to do when it took 5-10 minutes to get into his estimate via VPN…
This now makes everyone’s lives easier. Partners estimate side-by-side in one system from a shared database with version control and audit logs that keeps costs aligned through the whole planning process.
This is what turns IPD from theory to practice.
Cloud databases make everything visible and in Ediphi your data is stored in something we call the Unit Price Catalog.
Every line item is tied to a standardized name, unit of measure, and historical pricing so all JV partners reference the same data instead of reconciling conflicting numbers later. Costs and line items can be bundled together in any way that makes the most sense to different partners and clients.
Colby Ajoku, Director of Integrations at Ediphi, has led the charge in building what he considers to be the ultimate “open platform cloud solution for JVs”.
“At Ediphi, we can steer the ship in any way you need to go,” he says, “If client A comes and wants a particular use case, something proprietary and specific, and client B wants to hand select something else, we have enough tools in our tool belt to get it done.”
If you have specific data needs for your next project, talk to us — we can build it.
Big projects often involve dozens of evolving estimates in each design stage, from concept to final GMP.
Milestones is your filing cabinet; a central estimate dashboard where every partner can see 1) the current estimate and 2) all of its prior context for the full picture story of an IPD project.
%202.gif)
👉 Learn how to build your first Milestone here.
Excel won’t (and shouldn’t) be replaced — forcing teams to abandon it entirely creates unnecessary resistance — but we do need to improve our relationship with it.
With your collaborative environment set up, you can push final bids into Excel-based reports that auto-update.
Ediphi’s Last Mile Excel integration gives JVs flexibility to:
“Preconstruction is [often] left with figuring out [a lot] of information in the last mile, putting together our bids from trade partners and our numbers. Ediphi is the next generation of estimating platforms and the Excel Add-in is a snappy workflow.” — Kyle Bonde, Senior Estimator at Hensel Phelps
It’s proven to be a huge time-saver on enterprise-level projects, not to mention a more accurate way to compile reports at the last mile of a JV project.
👉 See how it works with this demo video from one of our customers.
Integrated project delivery works, but, as an industry, we need to move away from managing in silos, building designs we can’t afford, and reacting too late.
If you’re ready to make IPD practical on your next joint venture project, we’d love to show you how teams are using Ediphi to bring shared visibility, real collaboration, and early cost control into preconstruction.
Talk with our team or book a demo to see what IPD looks like when the systems finally match the intent.