What Is A Service Agreement? (2026 Updated)

If you’re providing services to clients (or engaging someone to do work for your business), you’ll quickly run into the same question: “Do we actually need a contract for this?”

In most cases, the answer is yes - and the contract you’re usually looking for is a service agreement.

This (2026 updated) guide explains what a service agreement is in New Zealand, when you should use one, what clauses matter most, and how to avoid the common mistakes that turn a simple job into an expensive dispute.

What Is A Service Agreement (And Why Does It Matter)?

A service agreement is a legally binding contract where one party agrees to provide services to another party, on agreed terms.

In plain English: it’s the document that sets out what’s being done, who’s doing it, when it must be done, how much it costs, and what happens if something goes wrong.

You’ll often see service agreements used by:

• consultants and contractors (marketing, IT, HR, design, bookkeeping)
• tradies and service providers (maintenance, cleaning, repairs)
• agencies (social media, recruitment, PR)
• businesses buying specialist services (software development, compliance, training)

Even if you’ve got a quote, an invoice, a few emails, or a “handshake deal”, you can still end up with a contract - but it may be unclear, incomplete, and much harder to enforce. A written service agreement is how you set expectations properly and protect your business from day one.

A strong agreement can help you:

• reduce scope creep (the “can you just also…” problem)
• get paid on time (and know what happens if the client doesn’t pay)
• limit disputes about deliverables, timeframes, or quality
• protect your intellectual property and confidential information
• clarify liability if something goes wrong
• set a clean process for ending the relationship

If you’re looking for a tailored document rather than a generic template, a properly drafted Service Agreement is usually the right starting point.

When Should You Use A Service Agreement (And When Not To)?

A service agreement is a great fit when you’re providing or receiving services rather than selling a one-off product.

You’ll usually want one when:

• the services will run over weeks or months (even if it’s “just a small project”)
• the work involves access to systems, customer data, trade secrets, or internal processes
• you’re paying a meaningful amount (or relying on the work for a critical business function)
• there’s any complexity around deliverables, milestones, approvals, or change requests
• either party needs the ability to terminate on notice

On the other hand, a service agreement might not be the best tool if what you really need is:

• Employment arrangements (that should be an employment contract, not a contractor-style service agreement)
• Ongoing platform or subscription terms (you may need website/app terms instead)
• A specific project framework where a master agreement plus “statements of work” are better

For example, if you’re hiring someone who will be treated like part of your staff (set hours, direction and control, integrated into your business), you should be using an Employment Contract - not a service agreement - because misclassifying workers can create real risk under employment law.

If you’re delivering a broader set of services over time, it can also make sense to use a Master Services Agreement and attach a project-specific scope separately (so you don’t need to renegotiate core terms each time you start a new piece of work).

What Should A Service Agreement Include?

There’s no single “perfect” service agreement - it needs to match your service, your industry, and your risk profile.

That said, most well-drafted service agreements cover the same key areas.

1. The Parties (And The Correct Legal Names)

This sounds basic, but it matters. If your client is “ABC Group” but the legal entity is “ABC Group Limited”, the agreement should reflect the correct contracting party.

If you operate under a trading name, it’s worth checking whether you’re using the right entity name too (especially if you’re a company).

2. Scope Of Services (What You’ll Do - And What You Won’t)

The scope is the heart of the agreement. A good scope section clearly explains:

• what services are included (deliverables, tasks, outputs)
• what is not included (boundaries and exclusions)
• assumptions (what you’re relying on the client to provide)
• how changes to scope will be handled (rates, approvals, timelines)

This is where many disputes come from. If the client believes you’re delivering “strategy + implementation + ongoing support”, but you believe it’s “strategy only”, you’ll feel the pain later.

3. Timeframes, Milestones And Acceptance

If you don’t set timeframes, your project can drag on indefinitely - or you can get blamed for delays caused by the client.

Consider including:

• start date and end date (or estimated duration)
• milestones and delivery dates
• what “acceptance” looks like (e.g. sign-off, testing, written approval)
• what happens if the client doesn’t respond (deemed acceptance rules)

This is especially important for creative, tech, and consulting services where “finished” can be subjective.

4. Fees, Payment Terms And Expenses

Be very clear about money. Your service agreement should spell out:

• how you charge (fixed fee, hourly rate, retainers, milestones)
• invoicing timing (upfront deposits, monthly billing, stage payments)
• payment due dates and consequences for late payment
• whether GST is included or added
• any reimbursable expenses (travel, tools, software licences)

A surprisingly common issue is where the work is done, but payment terms weren’t agreed properly - and then you’re negotiating from a weak position.

5. Client Responsibilities

Most services depend on the client doing their part. For example:

• providing content or access to systems
• approving drafts by certain dates
• assigning a decision-maker
• ensuring their information is accurate

Including client responsibilities protects you from being held responsible for delays or poor outcomes caused by missing information or late approvals.

6. Intellectual Property (IP) Ownership

IP is one of the most misunderstood parts of service arrangements.

Your agreement should address things like:

• who owns the final deliverables once paid for (e.g. designs, code, reports, training materials)
• whether you retain ownership but grant the client a licence to use it
• what happens to “background IP” (tools, templates, methods you already had)
• whether you can reuse general know-how (without disclosing confidential info)

This matters because, in many service businesses, your templates and systems are part of what makes you efficient and profitable. But your client may reasonably expect to “own what they paid for”. A well-drafted service agreement balances both.

If you’re licensing IP (rather than assigning it), an IP Licence approach can be built into the service agreement so everyone is clear on permitted use.

7. Confidentiality And Privacy

Confidentiality clauses protect commercially sensitive information - pricing, business plans, supplier terms, internal processes, customer lists, and more.

Privacy is slightly different. If you’re handling personal information (customer details, employee data, mailing lists), you also need to think about your obligations under the Privacy Act 2020, including taking reasonable steps to protect information and only using it for appropriate purposes.

Often, a service agreement should include privacy-related commitments (especially where you’re processing data for a client). Depending on the arrangement, you may also need a separate Data Processing Agreement to deal with data handling in more detail.

8. Warranties, Liability And Risk Allocation

This is where you decide (in advance) who carries what risk.

Common issues that come up here include:

• Warranties: promises that services will be provided with due care and skill
• Limitations of liability: caps on damages (for example, limited to fees paid)
• Exclusions: types of loss that aren’t covered (like indirect or consequential loss)
• Indemnities: where one party agrees to cover the other for specific losses (e.g. IP infringement from client-supplied materials)

These clauses can be the difference between a manageable issue and a business-threatening claim. They also need to be drafted carefully - especially where consumer law may apply, or where the clause could be considered unfair in certain contexts.

9. Termination (Ending The Arrangement Without Drama)

Even when everyone starts off excited, relationships change. Your service agreement should cover how the contract ends, including:

• termination for convenience (ending on notice)
• termination for breach (ending because something has gone wrong)
• immediate termination triggers (e.g. non-payment, insolvency, serious misconduct)
• what happens to work in progress, deposits, and handover of materials

Think of termination clauses as your exit plan. You hope you won’t need them - but you’ll be glad they’re there if the project turns messy.

What Laws In New Zealand Affect Service Agreements?

A service agreement is a contract, so general contract law principles apply - offer, acceptance, consideration, intention to create legal relations, and clear terms.

But in practice, service agreements in NZ often touch on a few key legal areas.

Contract And Commercial Law Basics

If the contract terms are unclear, inconsistent, or missing, you can end up in a dispute about what was actually agreed. Courts may interpret ambiguous terms against the party who drafted them (and arguments about “what we meant” are rarely cheap to resolve).

It’s also important that the agreement matches how you actually operate. For example, if your agreement says you’ll deliver within 5 business days but your internal process takes 3 weeks, you’re building a breach into your own contract.

Fair Trading Act 1986

If you’re advertising or selling services, the Fair Trading Act 1986 matters. In broad terms, it prohibits misleading or deceptive conduct and false representations.

That means you should be careful about:

• promising results you can’t guarantee (“we’ll double your sales in 30 days”)
• overstating experience, qualifications, or certifications
• unclear pricing (“from $X” but most clients pay more)

Your service agreement can support compliance by making deliverables, limitations, and assumptions clear - so you’re not accidentally over-promising in writing.

Consumer Guarantees Act 1993 (Sometimes)

The Consumer Guarantees Act 1993 can apply when services are supplied to consumers (for personal, domestic, or household use). It provides automatic guarantees, including that services are carried out with reasonable care and skill and completed within a reasonable time.

If your client is a business, you can sometimes contract out of the CGA (if it’s fair and reasonable and the services are acquired for business purposes), but you need to do it properly. This is one of those areas where tailored legal advice is important, because the right wording depends on who you’re dealing with and what you’re providing.

Privacy Act 2020

If you collect, store, use, or share personal information during the engagement, the Privacy Act 2020 is relevant. A service agreement can include privacy and security commitments, and it should line up with your overall privacy documents (like your privacy policy and internal processes).

Common Service Agreement Mistakes (And How To Avoid Them)

Service agreements don’t usually fail because people don’t care - they fail because the relationship moves quickly and nobody wants to “slow things down” with paperwork.

Here are some common traps we see, and what you can do instead.

Mistake 1: Relying On A Quote Or Invoice As The “Contract”

Quotes and invoices are useful, but they rarely cover the hard stuff: IP ownership, liability, confidentiality, termination rights, payment disputes, and delays.

Better approach: Use a service agreement (even a short one) and attach the quote or statement of work as a schedule.

Mistake 2: Scope Creep With No Change Control

Clients often ask for “small extras” that add up. If you don’t have a process for approving changes (and charging for them), you end up working for free or damaging the relationship by suddenly pushing back.

Better approach: Include a clear scope and a variation process: what counts as extra work, how you price it, and how it gets approved.

Mistake 3: Unclear IP Ownership

This is a big one for designers, developers, consultants, and agencies. If you don’t address IP, you can end up arguing over who owns the work - and whether the client can keep using it after termination or non-payment.

Better approach: Spell out ownership, licences, and what happens if invoices aren’t paid (e.g. IP transfers only upon full payment).

Mistake 4: Using A Random Online Template

Templates can be tempting when you’re busy. The risk is that they’re often written for different jurisdictions, different industries, or different business models - and they can include clauses that don’t match what you actually do.

Better approach: Use a tailored agreement that reflects your real service delivery, pricing, and risk. It’s usually much cheaper to do it right upfront than to fix it during a dispute.

Mistake 5: Misclassifying Workers As Contractors

If you’re engaging individuals to work regularly in your business, a “service agreement” doesn’t automatically make them a contractor. In NZ, the real nature of the working relationship matters.

Better approach: Get advice early and use the right document. If the person is effectively an employee, you should be using an employment agreement (and following employment law obligations).

Key Takeaways

• A service agreement is a contract that sets out the services, payment terms, responsibilities, and what happens if something goes wrong - so you’re protected from day one.
• Service agreements are especially useful for ongoing work, higher-value projects, or any engagement involving confidential information, IP, timeframes, or milestone payments.
• A strong service agreement usually covers scope, timeframes, fees, client responsibilities, IP ownership, confidentiality/privacy, liability, and termination.
• New Zealand laws like the Fair Trading Act 1986, Consumer Guarantees Act 1993 (in some cases), and Privacy Act 2020 can affect how you sell and deliver services and what you can include in your contract.
• Common mistakes include relying on quotes/invoices alone, letting scope creep happen, leaving IP unclear, using generic templates, and accidentally treating employees like contractors.
• Because service agreements need to match your actual business model and risk, it’s worth getting the document tailored rather than trying to DIY it.

If you’d like help putting a service agreement in place (or reviewing one a client has sent you), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.