Master Service Agreements: Key Clauses & Exit Routes for New Zealand Businesses

Master service agreements can save a lot of time, but they also create long-term risk if you sign them too quickly. Founders often accept the supplier’s standard terms without checking the liability cap, assume a statement of work will fix missing commercial details, or rely on verbal promises about service levels and cancellation rights that never make it into the contract. That is usually where disputes start.

If your business works with ongoing service providers, consultants, software vendors, agencies, or enterprise customers, the master agreement usually sets the rules for every future project. A small drafting issue at the start can affect pricing, IP ownership, confidentiality, data handling, payment disputes, and your ability to walk away later. Here’s what this guide answers: what master service agreements actually cover, which legal issues New Zealand businesses should check before you sign, the common drafting mistakes to avoid, and the exit routes that matter when the relationship stops working.

Overview

A master service agreement, often called an MSA, is a framework contract that governs an ongoing services relationship. It does not usually describe every task in detail. Instead, it sets the base legal terms, while individual projects, work orders, or statements of work sit underneath it.

For New Zealand businesses, the main value of an MSA is consistency. The main risk is that a bad framework gets repeated across every job under it.

• Who the parties are, and which related entities can use the agreement
• How services will be scoped through statements of work, work orders, or change requests
• Pricing, invoicing, payment timing, and what happens if a project changes
• Service levels, acceptance criteria, milestones, and remedies for delay or poor performance
• Who owns existing intellectual property and who owns new work created under the agreement
• Confidentiality, privacy, and data security obligations, especially where customer or employee information is involved
• Warranties, indemnities, liability caps, and any exclusions of loss
• Term, renewal, suspension, termination, and post-termination handover obligations
• Dispute resolution, notice requirements, and governing law

What Service Agreements Cover

A master service agreement should set the legal ground rules for the whole relationship, not leave key rights to assumption. If the contract is vague on the basics, each new project becomes harder to manage.

The framework and the project documents

Most MSAs work as a two-layer arrangement. The MSA contains the general legal terms, and each statement of work sets out the specific services, fees, timing, deliverables, and practical requirements for a particular job.

This matters because businesses often sign a short statement of work first and only later realise the master terms override it. Before you sign, check the order of precedence. If the MSA says it wins wherever there is inconsistency, then a project-specific promise may not help you unless the statement of work clearly overrides the general clause.

Scope of services

The scope needs to be specific enough that both sides can tell what is included, what is excluded, and what counts as a change. A vague scope is one of the fastest ways to end up in a billing dispute.

Good service documentation usually deals with:

• the exact services or deliverables
• milestones and target dates
• what the customer must provide
• dependencies on third parties or systems
• acceptance testing or sign-off steps
• the process for extra work and change requests

If you are the customer, be careful about clauses that let the provider substitute materials, reduce features, or alter the delivery approach without your approval. If you are the provider, make sure your obligations depend on the customer giving timely access, approvals, and information.

Pricing and payment mechanics

The contract should say more than just the headline fee. Businesses get caught when the commercial model is clear in principle but messy in practice.

Check whether the agreement covers:

• fixed fees, time-based fees, retainers, or usage-based charges
• when invoices can be issued
• how quickly invoices must be paid
• whether disputed amounts can be withheld
• when expenses can be charged and what evidence is required
• what happens if the customer delays the project
• annual fee increases or indexation

Before you accept the provider’s standard terms, look for automatic fee uplifts and broad rights to charge for any work said to be outside scope. Those clauses often sound harmless until the first variation lands.

Service levels and performance standards

If continuity matters, the agreement should define what acceptable performance looks like. This is especially relevant for managed services, IT support, software implementation, outsourced operations, and agency retainers.

A useful MSA may deal with uptime targets, response times, resolution times, reporting, escalation paths, service credits, and the difference between a minor issue and a material service failure. If those standards are missing, it becomes much harder to prove breach later.

Intellectual property rights

IP ownership is one of the most negotiated parts of master service agreements. The right answer depends on the type of service and what each side brings to the project.

Most contracts should separate:

• pre-existing intellectual property owned by each party before the agreement
• new material developed specifically for the customer
• general know-how, tools, templates, and methodologies used across clients
• licences needed so each party can use the work as intended

A common founder mistake is assuming payment automatically transfers ownership of all deliverables. It often does not. Some providers only grant a licence. Others transfer ownership but keep rights in their underlying tools and code libraries. The contract drafting needs to match the deal you actually expect.

Confidentiality, privacy, and data handling

If either side will access sensitive business information, customer details, or employee records, the MSA should do more than include a short confidentiality clause. The Privacy Act 2020 may also be relevant where personal information is collected, used, stored, or disclosed in the course of the services.

Before you sign, clarify:

• what information is confidential
• how it can be used
• who within each business can access it
• whether subcontractors can access it
• what security steps are required
• what happens to information at the end of the agreement
• whether offshore storage or processing is permitted

Privacy obligations are especially important if the provider handles customer support, payroll, CRM data, analytics, or any platform that stores personal information.

Warranties, indemnities, and liability allocation

This section decides who carries the risk when things go wrong. It deserves real attention before you sign a contract.

Warranties are promises about quality, authority, compliance, or performance. Indemnities shift specific losses from one party to the other, often for IP infringement, confidentiality breaches, privacy breaches, or third party claims. Liability clauses then try to limit exposure through caps and exclusions.

In New Zealand, these clauses also need to be read in the broader legal context. Depending on the arrangement, statutes such as the Consumer Guarantees Act 1993 and the Fair Trading Act 1986 can affect how services are described and supplied. Business-to-business contracts may limit some statutory protections if the legal requirements are met, but that should be handled carefully and drafted properly.

Legal Issues To Check Before You Sign

Before you sign, make sure the contract reflects the real operational and legal risk in the relationship, not just the sales process that got you there. The most useful contract review is not about spotting legal jargon, it is about testing what happens when the project slips, data is mishandled, or the relationship ends badly.

Does the contract match your buying or delivery model?

An MSA should fit the way the services will actually be delivered. If your business expects flexible project work, a heavily locked-in managed services template may be a poor fit. If you are buying mission-critical support, a lightweight consulting agreement may leave too much open.

Ask practical questions:

• Will work be ongoing or project-based?
• Will there be multiple statements of work over time?
• Are affiliates allowed to place orders under the same MSA?
• Can subcontractors be used, and if so, on what conditions?
• Does the customer need approval rights over key personnel?

Are the termination rights workable?

Your exit route should be clear before the relationship begins. Many businesses focus on onboarding and pricing, then realise too late that the contract is hard to unwind.

Key termination issues include:

• termination for convenience, and whether notice or break fees apply
• termination for material breach, including cure periods
• termination for insolvency or change of control
• suspension rights for non-payment or security concerns
• what happens to active statements of work when the MSA ends
• transition assistance, handover of materials, and return of data

If the provider is deeply embedded in your systems or customer delivery, termination rights are not enough on their own. You may also need a clear exit plan, handover obligations, cooperation commitments, and continued access to records for a short period after termination.

How do liability caps actually work?

A liability cap only helps if you understand what it covers. This is where founders often get caught.

Check:

• whether the cap applies per claim, per year, or in total
• whether fees paid under one statement of work or under the whole MSA set the cap
• which claims sit outside the cap, such as confidentiality breaches, unpaid fees, fraud, IP infringement, or privacy breaches
• whether indirect or consequential loss is excluded, and how broadly that is drafted

If your business could suffer a significant operational loss from failure of the services, a cap linked only to one month of fees may be unrealistic. If you are the provider, unlimited exposure can also be commercially dangerous and may not match your insurance obligations or cover.

Does the contract deal with statutory risk properly?

Service contracts should not be drafted as if the parties operate in a legal vacuum. Marketing claims, service descriptions, privacy statements, and service quality obligations can all affect risk.

For example, if a provider promises outcomes it cannot control, the wording may create both contractual risk and Fair Trading Act issues. If personal information is involved, the parties should allocate responsibility for privacy compliance, data breach notification cooperation, and security expectations. If the arrangement is truly business-to-business and the parties intend to contract out of parts of the Consumer Guarantees Act, the clause must be drafted carefully and used in the right context.

Who owns what at the end?

Exit disputes often turn into IP and data disputes. Before you rely on a verbal promise, make sure the written terms answer the end-of-relationship questions.

That includes:

• whether the customer receives final source files, records, credentials, reports, or working papers
• whether the provider must delete or return confidential information and personal information
• whether any licences continue after termination
• whether unpaid fees affect handover rights
• whether the customer can keep using partially completed work

If you need a smooth transition to a new provider, spell that out early. A short exit assistance clause can make a major practical difference later.

Common Service Agreement Mistakes

Most MSA problems do not come from obscure legal rules. They come from ordinary commercial assumptions that never made it into the drafting.

Signing the master terms and planning to fix everything in the statement of work

This is common and risky. If the MSA contains broad disclaimers, weak termination rights, or a supplier-friendly liability cap, a later statement of work may not fix the issue unless it expressly overrides the master terms.

Before you sign, work out which points belong in the framework itself and which can safely sit at project level.

Leaving scope too open

An unclear scope creates disputes over timing, change requests, and fees. Businesses often think flexibility is helpful, but vague drafting usually benefits the party with more leverage once the work has started.

If something is essential, write it down. If something is excluded, write that down too.

Relying on a liability cap without reading the carve-outs

A cap can look commercially acceptable until the exceptions swallow the rule. Some contracts carve out so many categories that the provider still carries near unlimited risk, or the customer still has little meaningful protection where it matters most.

Read the cap together with the indemnities, exclusions, and insurance position.

Ignoring the contract hierarchy

MSAs often sit alongside proposals, order forms, service descriptions, technical schedules, and policies. If the hierarchy is unclear, there is room for argument about which document controls.

The agreement should state the order of precedence clearly. That reduces the chance of a sales document or online policy overriding negotiated terms by accident.

Forgetting practical exit steps

Termination wording is not enough if the provider holds your data, manages your systems, or controls client-facing channels. The contract should deal with what happens in the last 30 to 90 days, not just the legal right to terminate.

Good drafting often includes:

• handover timeframes
• format requirements for returned data
• knowledge transfer obligations
• continued cooperation at agreed rates
• revocation of access credentials
• deletion confirmation where appropriate

Treating boilerplate as harmless

General clauses can affect real money and control. Renewal provisions, notice rules, assignment rights, audit rights, publicity permissions, and dispute resolution steps all matter in practice.

For example, an automatic renewal clause can lock you into another term if you miss a narrow notice window. An assignment clause may allow your counterparty to move the contract to a different group company or buyer without your approval.

Overlooking the business structure and signing party

The party named in the MSA should match the business that will actually perform or receive the services. Startups and growing SMEs sometimes contract under one entity while another entity invoices, holds the IP, or employs the delivery team.

That mismatch can create enforceability problems and confusion over liability. Before you sign, confirm the legal entity names, NZBN details if used in the paperwork, and whether any parent company guarantee is needed.

FAQs

What is the difference between a master service agreement and a statement of work?

An MSA sets the overall legal terms for the relationship. A statement of work deals with a specific project, deliverables, timing, and fees under that framework.

Can a New Zealand business terminate a master service agreement for convenience?

Only if the contract allows it. Some MSAs include termination for convenience on notice, while others lock the parties in for a minimum term or require payment of committed fees.

Do master service agreements need to include privacy clauses?

If the services involve personal information, privacy clauses are usually essential. The contract should address permitted use, security, breach cooperation, subcontractors, and return or deletion of information.

Who owns intellectual property created under a service agreement?

Ownership depends on the wording. Some agreements transfer ownership of project deliverables to the customer, while others leave ownership with the provider and grant a licence instead.

Are liability caps enforceable in New Zealand service contracts?

They often are, but the result depends on the drafting, the facts, and any relevant statutory limits. The real question is whether the cap is clear, commercially sensible, and aligned with the risks each party is taking on.

Key Takeaways

• A master service agreement is a framework contract, so problems in the core terms can affect every future project under it.
• Before you sign, check the scope, pricing model, service levels, IP ownership, confidentiality, privacy obligations, liability clauses, and document hierarchy.
• Exit routes matter from day one, including termination rights, handover obligations, data return, and transition assistance.
• Common mistakes include relying on verbal promises, assuming statements of work will fix weak master terms, and overlooking liability carve-outs.
• New Zealand businesses should also consider statutory issues, including fair trading, privacy, and any valid business-to-business contracting out provisions where relevant.
• A well-drafted MSA should reflect the real commercial deal and the practical way the services will be delivered and unwound.

If you want help with liability caps, termination rights, IP ownership, privacy clauses, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.