Joint Ventures P3: Integrated vs Non-Integrated JVs

AUTHORED BY: Batch Mewing Lawyers

PUBLISHED: 19 February 2026

In Part One of this series, we looked at what a construction joint venture is and why parties enter them. Part Two addressed how to structure and document a JV, whether incorporated or contractual. In this final piece, we turn to the delivery of joint venture works (how integrated and non-integrated JVs operate in practice) and the all-important question of who bears the risk when things go wrong.

Integrated Joint Ventures: One Team, One Delivery

An integrated joint venture is where two contractors effectively combine their teams, resources and systems to deliver a project as a single unit. There’s no meaningful separation between who is doing what e.g. personnel from both parties may be working on the same tasks, such as project engineering or site supervision. Practically, this model is often used when the contractors have similar scopes or capabilities and are joining forces to meet project demands.

Integrated JVs are commonly formed when the goal is to scale up resources or tender for projects that neither party could win alone. The delivery structure reflects that purpose: it’s unified. For all involved, this is a “one team, one dream” arrangement. But that doesn’t mean you can forget the detail.

Where both parties are operating under one banner, it’s still crucial that they align on standards, particularly around safety, quality and systems. If one JV partner is more relaxed in its approach, and the other runs a tighter ship, there needs to be a meeting of the minds early on. Any gaps in alignment can quickly cause tension once the works are underway.

Non-Integrated Joint Ventures: Distinct but Connected

By contrast, a non-integrated JV sees each party take full responsibility for delivering its own, clearly defined scope. The roles don’t overlap. One contractor might handle design while the other delivers construction. Or in lifecycle-style delivery models, one party might cover construction while the other handles operations and maintenance post-completion.

In these arrangements, each JV partner uses its own team and systems, manages its own subcontractors and is responsible for its own risk and performance. The joint venture agreement links them contractually and coordinates delivery, but in practice, the parties operate independently.

This structure is typically used when each contractor brings different strengths or specialisations to the table. Rather than blending their resources, the parties work side-by-side, each staying within their own swim lane. The advantage is that it allows for clarity. Each knows exactly what it’s responsible for, and each bears its own commercial risk. But it also requires a clear JV agreement to define scope boundaries and avoid grey areas.

So Who Bears the Risk?

The obvious question arises: what happens if something goes wrong? Say there’s a serious design flaw or a major construction defect – who wears the liability?

The starting point is that the joint venture is responsible. From the client’s perspective, particularly in unincorporated JVs, both parties are usually jointly and severally liable. That means the principal can pursue either or both JV partners for 100% of the loss, regardless of which party caused it. This risk is one of the key reasons JV partners need to document internal liability sharing in the JV agreement from the outset.

In an integrated JV, losses are typically shared between the parties in proportion to their contribution or ownership. The shared delivery model makes it difficult to allocate blame to one party, so the partners absorb the risk together. This reinforces the importance of choosing your JV partner wisely because if they underperform, you’ll share the consequences.

In non-integrated JVs, risk is more often allocated along scope lines. If one party causes the problem e.g. the design phase was poorly executed, it should bear the loss. This is usually managed through indemnities in the JV agreement, where each partner agrees to compensate the other if its actions cause them harm. In that sense, a non-integrated JV provides some protection against being dragged into problems caused by the other party’s performance.

But even with clear indemnities, the principal is unlikely to care which party is responsible internally. They’ll come after the JV, and it will be up to the partners to sort it out between themselves. This highlights the need to ensure that any indemnity or risk-sharing arrangement is backed by real commercial substance and enforceability.

Final Thoughts: Define and Align

Whether integrated or non-integrated, the delivery model of a joint venture should reflect how the work is actually going to be done and how the risk will be carried. There is no one-size-fits-all approach. But what is consistent is the need for clarity at the front end.

Documenting who does what, how decisions are made, and who wears what risk if things go sideways isn’t just good practice, it’s essential to avoiding disputes and protecting both the relationship and the bottom line. And with the scale of most JV projects, that clarity pays for itself quickly.

If you’re preparing to enter a JV, now’s the time to define your delivery model, clarify responsibilities, and align expectations before work begins. A well-structured JV can manage risk and deliver real commercial value. A poorly planned one, however, can expose parties to costly disputes and blurred accountability.

If you’d like support setting up or reviewing your JV structure, our team at Batch Mewing is here to help.

Have a question?

If you’re unsure how this applies to you, feel free to send us a message.

Related Articles

A refusing neighbour can stall a tight site fast. This piece runs through when a negotiated access deed will get you there, when section 180 of the Property Law Act might, and what a court actually expects to see before it forces the issue.

How can we help?

Whether you're facing an issue or planning ahead, we’re here to help you move forward. Share a few details using the form to get started.