Consortium Agreements In New Zealand: Key Legal Considerations

Teaming up with other businesses can be one of the fastest ways to win bigger projects, access specialist skills, and spread risk - especially if you’re a small business competing against larger players.

In New Zealand, one common way to do this is through a consortium arrangement, typically documented in a consortium agreement. But while the commercial upside can be huge, the legal details matter (a lot). If the agreement is vague, you can end up wearing another party’s mistakes, fighting over who owns the work, or getting stuck in a project you can’t exit cleanly.

Below, we’ll break down what a consortium is, when a consortium agreement makes sense, and the key legal issues to think about so you can collaborate confidently - and stay protected from day one.

What Is A Consortium (And When Do You Need A Consortium Agreement)?

A consortium is a group of separate businesses (and sometimes individuals) that work together to deliver a project or pursue a commercial opportunity.

Consortiums are especially common where:

• The scope is too big for one supplier to handle alone (e.g. major infrastructure, government procurement, large IT builds).
• Different expertise is required (e.g. one party supplies software, another does implementation, another handles ongoing support).
• A tender requires capacity (financial, staffing, qualifications, experience) that a single small business can’t demonstrate on its own.
• Risk needs to be shared (e.g. performance risk, delivery timelines, cost blowouts).

A consortium agreement is the contract that sets out how consortium members will work together. In plain terms, it answers:

• Who’s doing what?
• Who’s getting paid what (and when)?
• Who is responsible if something goes wrong?
• Who owns the IP and project materials?
• How do decisions get made?
• How do you resolve disputes and exit the relationship?

Even if you “trust the other parties” (or you’ve worked together before), it’s still worth documenting the arrangement properly. Big projects have a way of creating pressure - and pressure is where misunderstandings turn into disputes.

How Is A Consortium Different From A Partnership Or Joint Venture?

This is a common point of confusion, and it matters because the legal consequences can be very different.

A Consortium

A consortium is generally a collaboration arrangement where each member remains a separate business, and the consortium agreement sets the “rules of engagement” for the project.

Depending on how it’s structured, a consortium can be:

• Non-incorporated (more common): the consortium is just a contractual arrangement between members.
• Incorporated: members set up a special purpose vehicle (a company) to contract and deliver the project.

A Partnership

A partnership often involves carrying on business in common with a view to profit. Partnerships can arise intentionally or accidentally - sometimes people behave like partners without realising it, and then find out later they’ve created partnership-like liabilities.

If you’re not trying to form a partnership, your consortium agreement should be careful about:

• how the relationship is described (and what it is not), and
• who has authority to bind who.

When you do intend to operate as partners more broadly, it’s usually cleaner to use a Partnership Agreement rather than relying on a consortium agreement format.

A Joint Venture

A joint venture is a broader concept where two or more parties collaborate on a project or venture, sometimes via a contract and sometimes via a shared entity.

In practice, a consortium arrangement can be a type of joint venture - but the key is that your documents must match what you’re actually doing.

If you’re unsure what structure fits your deal (and what risks come with it), getting advice early can save a lot of pain later - especially before you submit a tender or sign with a principal.

Key Clauses To Include In A Consortium Agreement

A good consortium agreement isn’t just “nice to have” - it’s the thing that helps keep the project running when timelines slip, costs blow out, or the customer changes the scope.

Here are the clauses we’d usually expect to see (tailored to your project and industry).

1. Parties, Purpose, And Scope

Start with the basics:

• Who the consortium members are (legal names, NZBN/company numbers where relevant).
• The project purpose (e.g. submit a tender, deliver a contract, build and maintain a product).
• Scope and deliverables for each member (what each party will provide, and what is out of scope).

This is where vague wording causes disputes. If two members assume the “other party” is handling something (like project management, customer reporting, compliance documentation, insurance certificates), it becomes a problem fast.

2. Lead Contractor / Consortium Manager (And Authority)

Many consortiums have a lead member who:

• submits the tender,
• acts as the primary contact with the principal/customer, and
• coordinates delivery across consortium members.

Your consortium agreement should spell out:

• what the lead can decide alone,
• what requires unanimous approval or a steering committee vote, and
• whether the lead can sign variations, accept milestones, or agree to penalties (and whether that binds everyone else).

If you don’t manage authority clearly, you risk one member agreeing to something that increases everyone’s workload or liability.

3. Roles, Resourcing, And Subcontracting

Small businesses often join consortiums because they bring specialist people or equipment. Make sure the agreement deals with:

• minimum resourcing commitments (and what happens if a key person leaves),
• whether subcontracting is allowed (and if it needs approval), and
• quality and performance standards each member must meet.

If the project involves hiring staff specifically for delivery, your internal documents also need to be aligned (for example, your Employment Contract should clearly cover duties, confidentiality, and ownership of work product where appropriate).

4. Payment, Cost Sharing, And Cashflow

Money is where good relationships go to die - not because anyone is dishonest, but because expectations weren’t aligned.

A consortium agreement should set out:

• pricing model (fixed price, time and materials, milestone-based, hybrid),
• who invoices the principal (lead vs each member),
• how members get paid (direct pay, pass-through, or internal invoicing),
• what happens if the principal doesn’t pay (often a negotiated point: do members share the bad debt, or does the lead carry it?),
• how variations are priced and approved, and
• expense rules (travel, subcontractors, tools, admin, insurance).

If the lead is collecting all revenue and distributing to members, you’ll want strong reporting and audit rights so payments are transparent.

5. Liability Allocation And Indemnities

This is one of the most important legal sections of any consortium agreement.

You’ll usually want to cover:

• who is responsible for what losses (e.g. delays caused by one member, defective work, IP infringement, privacy breaches),
• indemnities (a promise to reimburse another party for certain losses),
• liability caps (where appropriate), and
• insurance requirements (public liability, professional indemnity, cyber, contract works - depending on the project).

One key question is whether liability to the principal is joint and several (meaning the principal can sometimes pursue one member for 100% of the loss) or whether each member is only liable for their own portion. The answer will depend on the head contract and how the consortium is structured.

Because this area is so fact-specific, it’s worth getting the consortium agreement reviewed alongside the head contract before you sign anything.

6. Intellectual Property (IP) And Confidentiality

IP gets messy quickly in collaborations, especially where each member brings “background” materials and then produces new “project” outputs.

A strong consortium agreement will usually address:

• Background IP: what each member already owns before the project, and what licences are granted to use it.
• Project IP / Foreground IP: what gets created during the project, and who owns it.
• Customer deliverables: what rights the customer receives (ownership vs licence, and whether it’s exclusive).
• Restrictions on reuse: whether a member can reuse templates, code, designs, or documents in future projects.
• Confidential information: what must be kept confidential and how it can be shared within the consortium.

If you’re sharing sensitive information (commercial, technical, or customer data), a standalone Non-Disclosure Agreement can also be useful at the negotiation stage, before the full consortium agreement is finalised.

7. Governance, Decision-Making, And Deadlocks

Consortiums need a practical way to make decisions without everything grinding to a halt.

Common options include:

• a steering committee with one representative from each member,
• weighted voting (e.g. based on contribution), or
• unanimous consent for “reserved matters”.

Reserved matters might include:

• pricing changes or tender submissions,
• accepting scope variations,
• changing key subcontractors,
• material changes to timelines, and
• any decision that increases liability exposure.

Also plan for deadlocks. If you don’t, you can end up in an expensive stalemate mid-project. A deadlock clause might include escalation to senior management, mediation, or an agreed tie-break mechanism.

8. Exit, Termination, And Replacement Of Members

It’s uncomfortable to talk about break-ups at the start - but it’s exactly when you should do it.

A consortium agreement should cover:

• when a member can exit (if at all),
• termination rights for breach or insolvency,
• what happens to work-in-progress and project IP on exit,
• handover obligations (so the customer isn’t left stranded), and
• whether the remaining members can replace the exiting party (and on what terms).

If there is a special purpose company involved, you’ll also want to align this with your ownership documentation (for example, a Shareholders Agreement and possibly a Company Constitution) so the “project reality” matches the shareholding and control mechanics.

Legal Risks Small Businesses Should Watch For In Consortium Arrangements

Consortiums can create fantastic growth opportunities - but for small businesses, the risk is often that you’re committing to obligations that feel “big business” in scale.

Here are some common risk areas to watch closely.

Accidental Liability For Another Member’s Mistakes

If the head contract makes consortium members jointly responsible, a failure by one party can become your problem even if you delivered your part perfectly.

That’s why it’s important to:

• review the head contract carefully before it’s signed, and
• ensure the consortium agreement back-to-backs liability internally (so, as far as possible, the party who causes the loss carries it).

Misaligned Scope (And Scope Creep)

In big projects, scope changes are normal. If you don’t have a clear variation process, you can end up doing extra work without being paid - or being blamed for refusing to do unpaid work.

Make sure your consortium agreement deals with:

• who can approve variations,
• how pricing changes are handled, and
• what happens if the principal “directs” work informally (e.g. by email or in meetings).

IP Leakage Or Losing Control Of Your Know-How

When you contribute specialist methods, templates, or software, you want to deliver the project - not accidentally give away the thing that makes your business valuable.

Clear IP clauses help avoid:

• a customer claiming ownership of your pre-existing tools, or
• a consortium member reusing your materials outside the project without permission.

Privacy And Data Responsibilities

If the project involves handling personal information (customers, end users, employees, patients, students - depending on the industry), your consortium may have obligations under the Privacy Act 2020.

Practically, this might mean:

• agreeing who is collecting data and who is processing it,
• setting security standards, and
• planning how you’ll manage a data breach.

It’s also a good idea to align what you tell people externally in your Privacy Policy with what you’re actually doing inside the consortium.

Choosing The Right Structure: Contract-Only Vs Special Purpose Company

There isn’t a one-size-fits-all approach. The “right” consortium structure depends on the project size, how the principal wants to contract, and the risk profile.

Option 1: Contract-Only Consortium (Unincorporated)

This is usually faster and cheaper to set up. Each member stays as-is, and the consortium agreement governs the relationship.

Pros:

• Less set-up and admin overhead
• Flexible for one-off projects
• No need to create and maintain a separate entity

Cons:

• Liability allocation can be more complex (especially if the head contract is joint and several)
• Payment flows and reporting can become messy
• Harder to present a single “face” to the principal if they want one contracting party

Option 2: Special Purpose Company (Incorporated Consortium)

Here, members create a new company to contract with the principal and deliver the project.

Pros:

• Clear contracting party for the principal
• Potentially cleaner risk containment (depending on guarantees and the head contract)
• Easier to manage project finances through one entity

Cons:

• More legal and accounting set-up
• You’ll need governance and ownership documents aligned with the project
• Directors still need to understand their duties and personal exposure where guarantees apply

If you’re setting up a special purpose company, make sure the internal documents (shareholding, voting rights, funding obligations, exit mechanics) align with the commercial deal. Otherwise, you can end up with control disputes mid-project.

Key Takeaways

• A consortium agreement is the key contract that sets out how collaborating businesses will deliver a project, share revenue, manage risk, and make decisions.
• Consortiums are common for larger tenders and multi-skill projects, but they need clear documentation to help avoid disputes over scope, payment, and responsibility.
• Your consortium agreement should clearly cover roles, authority (especially for a lead contractor), pricing and payment flows, IP ownership and licensing, confidentiality, and dispute/exit processes.
• Liability is a major issue - you’ll want the head contract and consortium agreement to work together so each member carries (as far as possible) the risks they control.
• If personal information is involved, make sure your consortium arrangement aligns with obligations under the Privacy Act 2020, including security and breach response responsibilities.
• Depending on the project, you may choose a contract-only consortium or set up a special purpose company - but either way, the documents should match the commercial reality.

Tip: This article provides general information only and doesn’t take into account your specific situation. If you’d like advice on your consortium structure, the head contract, or a consortium agreement tailored to your project, it’s best to speak with a lawyer.

If you’d like help drafting or reviewing a consortium agreement (or you’re about to sign a head contract and want to understand the risks), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.