What Is A Master Services Agreement? (2026 Updated)

If you’re doing ongoing work for clients (or engaging suppliers to support your business), it’s normal to feel a bit uneasy about where the “rules” of the relationship actually sit.

Maybe you’ve been sending quotes and invoices, or relying on email chains that say “sounds good” - and it’s worked so far. But as projects stack up, timelines tighten, and money gets bigger, those informal arrangements can get risky.

A Master Services Agreement (often called an MSA) is one of the simplest ways to put solid legal foundations under a working relationship, without having to renegotiate the same terms every single time.

This guide is updated for current NZ business practice, including how MSAs are commonly used with digital services, contractors, and subscription-style work - so you can stay protected from day one.

What Is A Master Services Agreement (MSA)?

A Master Services Agreement is a contract that sets the ground rules for an ongoing services relationship between two parties (usually a service provider and a customer).

Think of it as the “main umbrella agreement”. It usually covers the key legal and commercial terms that shouldn’t change from project to project, such as:

• who is responsible for what (and what happens if something goes wrong)
• how payment works (even if pricing varies per project)
• how intellectual property is handled
• confidentiality obligations
• liability limits
• how disputes are handled
• termination and exit rules

Then, each time you do a specific piece of work, you attach a Statement of Work (SOW), work order, or schedule that sets the project-specific details (scope, deliverables, pricing, milestones, timeframes).

This structure is popular because it reduces back-and-forth and keeps your terms consistent - especially if you have repeat clients or recurring engagements.

Common Examples Of When An MSA Makes Sense

You might consider an MSA if you:

• provide services that are repeated across multiple projects (e.g. marketing, design, IT, consulting, recruitment)
• do ongoing support/retainer work with changing tasks each month
• have multiple people in a client’s organisation requesting work (and you want a consistent legal framework)
• engage subcontractors and need reliable processes and protections
• deliver services using third-party tools or platforms (where privacy, security, and liability need to be managed carefully)

And if you’re in a situation where you’re balancing multiple legal documents, it can also help to compare an MSA to a more general Service Agreement, depending on how often the work changes and how you prefer to structure your scope.

How Is An MSA Different From A Statement Of Work (SOW) Or Service Agreement?

This is where a lot of businesses get tripped up - not because it’s complicated, but because people use the terms interchangeably.

In plain English:

• MSA: the ongoing “rulebook”
• SOW: the specific job details for this project
• Service Agreement: often a single agreement that combines the rules + the job details in one document

Master Services Agreement Vs Statement Of Work

An MSA should ideally stay stable over time. The SOW can change every time you take on new work.

A good way to think about it is:

• The MSA says how you work together.
• The SOW says what you’re doing this time.

This is also why getting the SOW right matters. If the scope is vague, you can end up doing “just one more thing” forever, and it becomes hard to charge for variations.

Master Services Agreement Vs Service Agreement

A standard service agreement might be enough if:

• you only do one-off projects
• your scope and deliverables are clear and unlikely to change
• you don’t expect repeat engagements (or if you do, they’re rare)

But if you’re doing ongoing work, an MSA can save time and reduce risk because you don’t need to renegotiate the core clauses every time a new project kicks off.

If your work is more technical (like IT support, managed services, or SaaS-related services), you might also find you need an MSA that aligns with an IT Services Agreement approach - especially around availability, outages, and responsibility for third-party systems.

What Clauses Should A Master Services Agreement Include?

Every business is different, but most MSAs in New Zealand include a set of core clauses that act like your “default settings”.

Here are the key sections you’ll usually want to consider.

1. Scope Framework And How SOWs Are Approved

Your MSA should explain:

• how a new SOW is created and approved (e.g. signed, accepted by email, accepted via portal)
• what happens if there’s a conflict between the MSA and the SOW (usually the SOW prevails for scope/pricing, but the MSA prevails for legal terms)
• who can authorise work on the customer’s side

This is one of the easiest places for misunderstandings to happen - especially when different team members give instructions.

2. Fees, Invoicing, And Payment Terms

This section commonly covers:

• how fees are calculated (fixed fee, hourly, retainer, usage-based)
• when you invoice (upfront, milestone, monthly)
• payment timeframes
• late payment interest and recovery costs (if applicable)
• expenses and third-party costs

Even if your pricing changes per project, the MSA can still set the framework, with each SOW plugging in the numbers.

3. Intellectual Property (IP) Ownership And Licensing

IP is a big deal in services agreements because “who owns what” isn’t always obvious.

An MSA should clearly address:

• pre-existing IP (what you already own before the project starts)
• new IP created during the services (does the client own it, do you own it, or is it licensed?)
• tools and templates (e.g. your internal frameworks, reusable code, design systems)
• deliverables (what exactly the client receives and in what format)

For many service providers, the realistic goal is: the client gets what they need to use the deliverables, while you still protect your reusable know-how so you can keep operating and scaling.

4. Confidentiality

Most clients will expect confidentiality, and many service providers need it too (for pricing, methods, and trade secrets).

Your confidentiality clause should cover:

• what counts as confidential information
• how it can be used (only for the purposes of performing the services)
• exceptions (e.g. already public, independently developed)
• how long confidentiality obligations last

Sometimes confidentiality is handled through a standalone Non-Disclosure Agreement, but an MSA typically builds it in so you’re covered across the whole relationship.

5. Privacy And Data Handling (If You Touch Customer Or User Data)

If your services involve collecting, storing, accessing, or processing personal information (even incidentally), you should take privacy seriously from day one.

In New Zealand, the Privacy Act 2020 sets out how organisations must handle personal information. An MSA may need to deal with practical points like:

• what personal information will be handled during the services
• security expectations (access controls, encryption, breach response)
• where data is stored (including offshore storage)
• who is responsible for privacy compliance tasks
• how privacy breaches are managed (including notification obligations)

If your business collects personal information directly (for example via your website or platform), having a properly drafted Privacy Policy is usually part of your overall legal foundations too.

6. Warranties And Compliance With NZ Law

MSAs often include promises (warranties) about service quality, skill, and compliance.

Depending on your business and the customer, it may also refer to compliance with laws like:

• Fair Trading Act 1986 (advertising and representations must be accurate and not misleading)
• Consumer Guarantees Act 1993 (if your customer is a consumer - not always the case in B2B)
• Health and safety obligations (particularly if you work onsite)

These clauses matter because a contract doesn’t exist in a vacuum - your real-world obligations under NZ law still apply.

7. Liability, Indemnities, And Risk Allocation

This is usually the part people skip past - until something goes wrong.

MSAs often cover:

• limits on liability (e.g. a cap tied to fees paid)
• exclusions of certain losses (like indirect or consequential loss)
• indemnities (for example, if one party breaches IP rights or privacy obligations)
• insurance requirements (where relevant)

The goal is to clearly allocate risk so you’re not unintentionally taking responsibility for things you can’t control (like the customer’s systems, third-party platforms, or decisions made using your deliverables).

8. Termination And Exit (Including What Happens To Work In Progress)

An MSA should set clear rules for ending the relationship, such as:

• termination for convenience (if permitted)
• termination for breach
• notice periods
• what happens to unpaid invoices
• handover obligations (if any)
• return or deletion of confidential information

Without a solid exit clause, it can be hard to enforce payment, protect your IP, or control the handover process.

Why Do Businesses Use Master Services Agreements?

Most businesses don’t use an MSA because they want more paperwork. They use it because they want less friction and fewer surprises.

Here are some of the most common reasons an MSA is worth considering.

It Saves Time On Repeat Work

Once the main terms are settled, you can start new projects quickly by issuing a new SOW.

This is especially helpful if you’re scaling and want a consistent contracting process your team can follow.

It Reduces Scope Creep

Scope creep usually isn’t malicious. It tends to happen when:

• deliverables weren’t clearly defined
• sign-off points weren’t agreed
• “small extras” keep getting added without a variation process

A good MSA + SOW structure makes it much easier to point to the agreed scope and manage variations fairly.

It Helps You Manage Legal Risk Across Multiple Projects

Imagine you do three projects for the same client over 12 months, and a dispute arises on the third one.

If you’ve been contracting differently each time (or not at all), you may find:

• your liability terms are inconsistent (or missing)
• IP ownership is unclear across deliverables
• confidentiality expectations were never actually agreed

An MSA helps reduce that uncertainty by applying consistent terms to each project.

It Can Make Your Business Look More Established

For many clients, having a clear MSA signals professionalism and maturity.

It shows you’ve thought about issues like confidentiality, IP, payment, and disputes - which can make it easier to win larger work and build longer-term relationships.

Common MSA Pitfalls (And How To Avoid Them)

MSAs are powerful, but they’re not magic. A poorly drafted MSA (or one that’s copied from overseas or pulled from a template) can create just as many problems as having no contract at all.

Here are a few common pitfalls we see.

Using A Generic Template That Doesn’t Match Your Service Model

Templates often:

• assume a different legal system (for example US-style indemnities and definitions)
• don’t reflect NZ consumer and fair trading obligations
• include unrealistic promises (like guaranteed outcomes)
• fail to address how you actually deliver services (especially for digital work)

It’s usually better to have an MSA drafted (or at least reviewed) so it matches your real-world process.

Leaving The SOW Too Vague

If the SOW doesn’t clearly describe what you’re doing, you may struggle to enforce:

• payment for additional work
• deadlines that depend on client inputs
• acceptance and sign-off milestones

Even a short SOW should be specific about deliverables and assumptions.

Not Aligning Your MSA With Your Other Legal Documents

Your MSA doesn’t exist in isolation. Depending on your business, it may need to align with:

• your general customer contract terms
• your Terms of Trade (especially if you sell mixed goods/services or trade with different customer types)
• your subcontractor or contractor agreements
• your internal policies (like privacy and information security)

Misalignment can create confusion about which document applies - and that’s where disputes can start.

Not Thinking Through IP When You’re Using Contractors

If you’re delivering services using contractors (designers, developers, consultants), you need to make sure your contractor arrangements deal properly with:

• IP created during the work
• confidentiality
• privacy and data access

In many cases, that means having a proper Contractor Agreement in place so you can actually pass IP rights to your customer (if that’s what you’ve promised in your MSA).

Key Takeaways

• A Master Services Agreement (MSA) sets the overarching rules for an ongoing services relationship, while Statements of Work (SOWs) set the project-specific scope, pricing, and deliverables.
• MSAs can save time and reduce risk by keeping consistent terms across multiple projects, especially for repeat clients and retainer-style work.
• A well-drafted MSA usually covers payment terms, confidentiality, privacy and data handling, intellectual property, termination, and liability allocation.
• In New Zealand, your MSA should be consistent with key obligations under laws like the Privacy Act 2020 and the Fair Trading Act 1986, rather than relying on overseas templates.
• Vague SOWs and misaligned documents are common pitfalls - clear scoping and consistent contract structure help prevent scope creep and disputes.
• If you use contractors to deliver services, your contractor documentation should match the IP and confidentiality promises you’re making to customers in your MSA.

If you’d like help drafting or reviewing a Master Services Agreement (or setting up a clean MSA + SOW structure that fits how you actually work), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.