What Is A Teaming Agreement? (2026 Updated)

When you’ve found a big opportunity but you can’t (or don’t want to) deliver it alone, teaming up with another business can be the difference between winning the work and missing out.

That’s where a Teaming Agreement comes in. It’s a practical contract used when two (or more) parties agree to work together to pursue and/or deliver a project - usually before you have a longer-term arrangement in place.

This guide is current as at 2026 and reflects what we’re seeing in modern procurement and commercial projects (including collaborative bids, cross-industry partnerships, and projects involving data, IP, and subcontracting). We’ll break down what a teaming agreement is, when you should use one, what it should include, and how to avoid the common traps.

What Is A Teaming Agreement?

A Teaming Agreement is a contract between two or more parties who intend to collaborate on a specific opportunity - commonly a tender, proposal, grant application, client pitch, or major project delivery.

It usually covers two stages:

• Pre-award (bid stage): you agree how you’ll work together to prepare the bid, who contributes what, and who “owns” the proposal materials.
• Post-award (delivery stage): if you win the work, you agree (at least at a high level) how the project will be delivered, who contracts with the customer, and how responsibilities and revenue are split.

In plain terms, it’s the “rules of the road” for your collaboration - so nobody is guessing what was agreed after you’ve already put time, money, and reputation on the line.

Is A Teaming Agreement Legally Binding In New Zealand?

It can be, yes - but it depends on how it’s drafted.

Some teaming agreements are written to be fully binding (for example, obligations around confidentiality, exclusivity, intellectual property, cost-sharing, and dispute resolution).

Others are a mix: they make some parts binding, while treating other parts as “in-principle” only (for example, a future intention to negotiate a subcontract). That can be a sensible approach, but you need to be careful - because a vaguely drafted “we’ll negotiate later” clause can turn into a major risk if the relationship breaks down.

Teaming Agreement vs Joint Venture vs Subcontractor Agreement

These arrangements are related, but they’re not the same thing.

• Teaming Agreement: commonly used early - to pursue an opportunity together and set expectations, often before the final delivery contracts are signed.
• Joint Venture: a deeper collaboration (sometimes with a new entity or shared governance). If you’re weighing structures, the difference between a joint venture vs partnership is often a good place to start.
• Subcontractor Agreement: used for delivery, once the head contractor has the job and is engaging the other party to perform services. In many projects, the teaming agreement is a stepping-stone towards a Sub Contractor Agreement.

A teaming agreement is especially useful when the opportunity is time-sensitive and you need to align quickly, without committing to a full joint venture structure.

When Should You Use A Teaming Agreement?

If you’re thinking “do we really need a contract for this?” - you’re not alone. But in practice, a teaming agreement is most useful in situations where:

• You’re bidding for work together (government tenders, corporate RFPs, panels, or large private contracts).
• You’re combining capabilities (e.g. one party has the technical capability, the other has the customer relationship, licences, or delivery footprint).
• You’re sharing confidential information (commercial pricing, client lists, methodologies, product roadmaps).
• You’re producing IP together (proposals, designs, prototypes, software, content, data sets).
• You need clarity on who is “prime” (who contracts with the customer and who takes legal responsibility for delivery).

It’s also helpful where there’s an “awkward middle stage” - you’re not ready for a long-form contract yet, but you’ve moved beyond a handshake.

A Quick Example (Why This Matters)

Imagine you’re a software provider and you team up with a consultancy to respond to a major RFP. You do most of the technical solution and pricing model. They submit the bid, win it, and then decide to deliver with another vendor.

Without a teaming agreement covering exclusivity, use of materials, and what happens if the bid is successful, it can be hard to protect your position - and even harder to prove what was agreed.

What Should A Teaming Agreement Include?

There’s no “one size fits all” teaming agreement, because the right terms depend on your project, risk profile, and bargaining power.

That said, most well-drafted teaming agreements cover the following key areas.

1) The Purpose And Scope Of The Collaboration

This section spells out what you’re teaming up to do. For example:

• preparing and submitting a tender response
• building a prototype for a pitch
• delivering a defined scope of services if the bid is successful

Clarity here helps prevent scope creep (and the classic “I thought you were doing that” problem).

2) Roles And Responsibilities

This is where you allocate who does what. A practical way to do it is to attach a short schedule that covers:

• bid writing and management
• technical solution design
• pricing and commercials
• customer presentations
• implementation and delivery tasks
• account management and reporting

If your arrangement involves a “prime contractor” and one or more supporting parties, you’ll also want to document how decisions are made, who communicates with the customer, and who has authority to submit documents on behalf of the team.

In some cases, parties also sign an Authority to act form so it’s clear who can represent the group in the bid process.

3) Exclusivity (Or Non-Exclusivity)

One of the most important commercial points is whether the parties are exclusive to each other for the opportunity.

Exclusivity can protect you from being “used” for your expertise and then replaced - but it can also restrict your ability to pursue other work.

Common approaches include:

• Full exclusivity: neither party can team with others for the specific opportunity.
• Limited exclusivity: exclusivity applies only to a defined scope (e.g. a specific customer or tender reference).
• Non-exclusive teaming: parties can still work with others, but must manage conflicts and confidentiality carefully.

If exclusivity is included, it should have clear timeframes (for example, ending when the tender outcome is announced, or after a set negotiation period).

4) Confidentiality And Information Handling

Teaming often involves sharing sensitive commercial information. Your teaming agreement should cover:

• what information is confidential (and what isn’t)
• how it can be used (often “only for the purpose” of the bid/project)
• who it can be shared with (staff, subcontractors, advisors)
• security expectations (especially where data is exchanged digitally)
• what happens on termination (return or destruction of information)

Sometimes a separate NDA is signed first, but a teaming agreement usually needs its own confidentiality clause too - because the collaboration is broader than a simple information exchange. If you’re also using a standalone NDA, it’s worth making sure the documents don’t conflict.

5) Intellectual Property (IP) Ownership And Licensing

IP is one of the most common pain points in teaming arrangements.

At a minimum, you should cover:

• Background IP: what each party brings in (tools, templates, code, methodologies, branding).
• Project IP: what’s created during the bid and/or delivery (proposal content, solution designs, work product).
• Who can use what: permissions to use each other’s materials for the opportunity, and whether ongoing use is allowed.

For example, you might allow the other party to use your proposal materials only for that bid, and only if you remain part of the delivery team.

If you expect to transfer ownership of IP, or if one party is commissioning the other to create materials, you may also need a separate IP transfer or licensing document. In many collaborations, an IP assignment (or a licence) is what properly “moves” IP rights.

6) Commercials: Fees, Revenue Share, And Bid Costs

A teaming agreement should set expectations around money early, even if some details are still subject to negotiation later.

This section might cover:

• who pays bid costs (and whether costs are capped)
• how bid costs are approved (so you don’t get surprise invoices)
• how revenue will be split if the bid is successful
• whether there are referral fees or margins on subcontracted work

If you’re not ready to lock in final pricing, you can still include a process (for example, “parties will agree a pricing schedule in good faith within X days of award”). The key is to avoid leaving the most important commercial issues completely open-ended.

7) Contracting Model: Who Signs With The Customer?

This is a big one - because it affects risk and control.

Common models include:

• Prime and subcontract: one party signs the customer contract, and the other delivers under a subcontract.
• Separate contracts: both parties contract directly with the customer (less common, but can happen).
• Joint venture contracting: a JV entity (or incorporated JV) contracts with the customer (more complex).

If you’re the subcontractor, you’ll usually want clarity on what terms you’ll be asked to accept later - because the head contract can impose serious obligations (timelines, indemnities, service levels, liability).

Even if the teaming agreement doesn’t include the final subcontract, it should state the intended contracting structure and what happens if the parties can’t agree the downstream documents.

8) Liability, Indemnities, And Risk Allocation

Teaming agreements often include at least a baseline position on risk, such as:

• each party is responsible for its own acts and omissions
• limits on liability (where appropriate)
• indemnities for specific risks (e.g. IP infringement, confidentiality breaches)

If the project is high value, or if you’re working in regulated environments (health, finance, education, critical infrastructure), it’s worth getting this part properly tailored - because a vague clause can create unexpected exposure.

9) Term, Termination, And What Happens After

Teaming agreements should cover how long they run for and how they end, including what happens if:

• the bid is not successful
• the customer changes scope
• one party wants to exit early
• there’s a breach (e.g. confidentiality, non-solicitation)

Importantly, it should also state which clauses survive termination (confidentiality, IP, liability, dispute resolution).

10) Dispute Resolution And Practical Problem-Solving

Even when everyone has good intentions, issues can come up quickly under tender timeframes.

A simple dispute resolution pathway can help keep things from escalating, such as:

• good faith negotiation between project leads
• escalation to directors
• mediation
• court proceedings as a last resort

It’s also common to specify New Zealand law and jurisdiction, especially where one party is overseas.

What Are The Common Risks If You Don’t Have A Teaming Agreement?

A surprising number of collaborations start with “we’ll sort it out later”. The problem is that later usually arrives when the stakes are high - like when you’ve just won a contract, deadlines are tight, and everyone’s under pressure.

Here are some of the most common risks we see when there’s no teaming agreement (or when it’s too vague).

Confusion Over Who Owns The IP

Without clear IP terms, you can end up in disputes over whether:

• proposal materials can be reused
• solution designs belong to the “prime” or the creator
• one party can keep using the other party’s tools after the relationship ends

That’s not just a legal issue - it can affect your ability to work with future clients.

One Party “Goes Around” The Other

This can happen in a few ways:

• the prime cuts the supporting party out after the bid is won
• a supporting party approaches the customer directly
• a party uses the other’s confidential pricing to compete

Strong confidentiality, exclusivity (where needed), and non-solicitation terms can reduce this risk significantly.

Misaligned Expectations On Price And Delivery

You might assume a 50/50 revenue split, while the other party assumes you’re being paid a fixed subcontract fee.

Or you might assume you’ll lead delivery, while the other party assumes you’re only assisting.

A teaming agreement won’t solve every commercial disagreement, but it makes the key assumptions visible early - when you can still renegotiate or walk away.

Unexpected Legal Exposure

If you’re not clear about who contracts with the customer, you might accidentally take on obligations you didn’t price for (for example, warranties, service levels, or broad indemnities).

And if the arrangement involves personal information (for example, customer data in a shared system), you’ll also need to think about privacy compliance under the Privacy Act 2020. In many online or tech-enabled projects, a Privacy Policy and proper data-handling terms aren’t optional - they’re part of running a credible, compliant operation.

How Do You Set Up A Teaming Agreement The Right Way?

If you’re about to enter a teaming arrangement, it helps to treat it as a business project in its own right. A bit of structure early on can save you a lot of stress later.

Step 1: Get Clear On The Commercial Goal

Start by aligning on the basics:

• What opportunity are you pursuing?
• Who is the customer and what’s the timeline?
• Who is the prime (if any)?
• What does success look like for each party?

If the parties don’t share a similar view of what the collaboration is meant to achieve, the legal document won’t fix that.

Step 2: Identify The “Non-Negotiables” Early

Each party should know what they need to protect. Common non-negotiables include:

• ownership of background IP
• exclusivity (or freedom to pursue other work)
• minimum scope of work on delivery if the bid is successful
• limits on liability
• who controls the customer relationship

Putting these on the table early keeps the negotiation focused and practical.

Step 3: Make Sure Your Teaming Agreement Matches The “Next Document”

A teaming agreement usually sits alongside (or leads into) other contracts, such as:

• a subcontract
• a services agreement
• a joint venture agreement
• a heads of agreement or term sheet

For example, if the intention is prime-and-subcontract, it’s smart to sanity-check the teaming agreement against what your downstream subcontract will likely look like, including deliverables and payment triggers.

If you’re already using a broader Service Agreement template for delivery work, the teaming agreement should be consistent with it (or at least not contradict it).

Step 4: Don’t Ignore The “People And Process” Side

Even in a business-to-business project, people issues matter. Consider adding practical process terms like:

• weekly bid meetings and who attends
• approval steps for pricing and final submission
• how you’ll handle customer questions during the tender period
• who keeps records of decisions (this can be crucial later)

These aren’t “legal niceties” - they’re often what keeps the collaboration running smoothly.

Step 5: Get It Properly Drafted (Templates Can Miss The Real Risk)

It’s tempting to grab a generic template, especially when tender deadlines are tight.

But teaming agreements are rarely generic in practice. The risky parts (IP, exclusivity, downstream contracting, and liability) depend heavily on what you’re actually doing and where the commercial leverage sits.

A lawyer can help tailor the document so it reflects your real deal and still remains workable - not overly complicated.

Key Takeaways

• A teaming agreement is a contract that sets the rules for collaborating on a bid and/or delivering a project, especially where you’re combining capabilities to win work.
• Teaming agreements can be fully binding or partly binding, but the drafting needs to be clear so you don’t end up with uncertainty around “agreements to agree”.
• Good teaming agreements usually cover roles and responsibilities, exclusivity, confidentiality, IP ownership and licensing, commercial terms, contracting structure, liability, and termination outcomes.
• Common risks without a teaming agreement include IP disputes, being cut out after the bid is won, misaligned pricing/delivery expectations, and unexpected legal exposure.
• If the collaboration involves customer data or shared systems, you should also think about privacy compliance under the Privacy Act 2020 and having the right policies and contractual protections in place.
• Because teaming arrangements often lead into more formal delivery contracts, it’s worth getting the agreement tailored to your project rather than relying on a generic template.

If you’d like help drafting or reviewing a Teaming Agreement (or the downstream subcontract and delivery contracts), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.