IPD Contracts UK: Collaborative Construction Guide
We're not a law firm — we help you find the right legal support. For advice on your situation, speak to a legal adviser or find a solicitor.
If you work in construction or commission building projects, you have probably noticed how traditional contracting arrangements can pull teams in different directions. Designers, contractors and specialists each protect their own position, and the client is left picking up the pieces when things go wrong.
Integrated Project Delivery, usually shortened to IPD, takes a different route. It brings the client, design team and construction team into one commercial arrangement where success or failure is shared by everyone at the table. In this guide I want to unpack how IPD contracts actually work in practice, what makes them different from the JCT or NEC forms most UK projects rely on, and where they sit within the wider procurement toolkit. I will also flag the practical issues you should think through before deciding whether this route suits your project.
What this document is
An Integrated Project Delivery contract is a multi-party agreement that binds the client, lead designer, main contractor and often key specialist trades into a single commercial relationship. Rather than the client holding separate contracts with each discipline, the core team signs up to one document with shared goals, shared financial outcomes and shared decision-making.
The concept originated in North America but has gained traction in the UK, particularly on complex projects where collaboration is essential. Key features usually include open-book accounting, a target cost that the team works to collectively, a pain-share and gain-share mechanism that links everyone's profit to project performance, and a waiver of most inter-party claims.
Early involvement of the construction team during design is central, so that buildability, cost and programme are tested before the design is locked in. The NEC4 Alliance Contract, published in 2018, is the most well-known UK form that follows these principles, although bespoke IPD agreements are also used.
IPD is not a silver bullet, but where the project is complex, the team is capable and the client is engaged, it can produce markedly better outcomes than traditional procurement.
How to use this document
- Assess whether IPD is right for the project. Not every scheme suits this model. IPD tends to work best on complex, high-value projects where design uncertainty, interface risk or programme pressure would cause friction under a traditional contract. Simpler projects with well-defined scope may be better served by standard JCT or NEC options.
- Select the right partners early. Because the whole team signs one contract, partner selection matters more than price on day one. Look at track record on collaborative projects, cultural fit, financial stability and the individuals who will actually be on site. A weak link in an integrated team affects everyone's outcome, so due diligence here pays off later.
- Agree the commercial model and target cost. The team needs to establish a target cost, the cost components that are reimbursable, the profit and overhead percentages, and how pain and gain are shared if the outturn cost lands above or below target. This is usually done through open-book workshops, not a competitive tender.
- Set up governance and decision-making. IPD contracts typically create a project board or alliance leadership team with representatives from each party. Decisions are made by consensus where possible, with escalation routes if agreement cannot be reached. Clear terms of reference, meeting cadence and authority levels should be written into the contract.
- Build in continuous performance management. Shared KPIs, regular cost and programme reporting, lessons-learned sessions and a clear dispute avoidance process keep the alliance on track. The best IPD projects treat the contract as a live framework for collaboration rather than a document that sits in a drawer until something goes wrong.
Common questions
Q How does an IPD contract differ from a standard JCT contract?
A JCT contract is a bilateral agreement between the employer and contractor, with separate appointments for designers. An IPD contract is a multi-party agreement that ties the client, designers and contractor into one commercial relationship with shared risk and reward. The JCT allocates risk to specific parties, whereas IPD spreads risk and incentivises the team to solve problems collectively rather than argue about whose contractual responsibility it is.
Q Is the NEC4 Alliance Contract an IPD contract?
The NEC4 Alliance Contract, published in 2018, follows IPD principles closely. It is a multi-party agreement with a shared target cost, pain-share and gain-share mechanisms, and collaborative governance. It is probably the closest standard-form option available in the UK for parties wanting a ready-made IPD-style contract, although some clients still prefer a bespoke agreement drafted around their specific project.
Q Who carries the risk on an IPD project?
Risk is shared across the integrated team rather than allocated to one party. If the project comes in under the target cost, the savings are shared through the gain-share mechanism. If it overruns, the team collectively absorbs some or all of the pain, up to agreed caps. This structure encourages joint problem-solving but requires careful drafting so that parties understand their exposure before signing.
Q Does an IPD contract prevent disputes entirely?
No, but it can reduce the frequency and severity of disputes. Most IPD contracts include waivers of claims between alliance members except in limited circumstances such as wilful default or insolvency. Combined with collaborative governance and early issue resolution, this tends to keep disagreements out of formal adjudication or litigation. Issues still arise, and the contract needs clear escalation and dispute avoidance procedures.
Q Are IPD contracts suitable for public sector projects?
They can be, and several UK public sector bodies have used alliance-style contracts on infrastructure and regeneration schemes. Procurement rules still apply, so the selection process needs to be structured to comply with public contract regulations. The collaborative nature of IPD can sit comfortably with public sector objectives around value for money and social value, provided the governance is robust.
Q What are the main risks of using an IPD contract?
The main risks are cultural rather than legal. If any party approaches the project with a traditional adversarial mindset, the model struggles. Other risks include weak target cost setting, poor open-book discipline, and insufficient investment in governance. Insurance can also be more complex because traditional professional indemnity and construction all-risks policies were not designed around shared liability arrangements.
Q Can small or mid-size projects benefit from IPD?
IPD is often associated with major projects, but scaled-down versions of the approach can work on mid-size schemes where collaboration matters. For smaller projects, the administrative overhead of a full alliance contract may outweigh the benefits, and a collaborative form like NEC4 Option C with a partnering overlay might be a more proportionate choice.
Sources
This guide is based on primary UK law and official guidance.
- Official SourceNEC4 contract suite (NEC official site)neccontract.com
- Official SourceJCT contracts overviewjctltd.co.uk
- Official SourceConstructing Excellence (collaborative working resources)constructingexcellence.org.uk
Legal disclaimer
This article is for general information only. It is a tool to help you find your way — not legal advice, and not a substitute for speaking to a qualified adviser about your situation.