Service Level Agreements in New Zealand: Setting Clear Terms

If you provide services to customers (or rely on someone else’s services to run your business), you’ve probably had that moment where you think: “What exactly are we promising here?”

That’s where service level agreements (SLAs) come in.

A well-drafted SLA can turn vague expectations into clear, measurable commitments - so you can deliver confidently, get paid properly, and avoid disputes when something goes wrong. Just as importantly, it can help you keep clients happy because everyone knows what “good service” actually looks like.

Below, we break down how service level agreements work in a New Zealand context, when you should use one, what to include, and the common pitfalls that can cause headaches later.

What Is A Service Level Agreement (SLA)?

A service level agreement (SLA) is a contract (or part of a contract) that sets out the service standards you agree to meet.

It usually covers things like:

• what services are included (and what’s excluded);
• how quickly you’ll respond to issues;
• uptime, availability, turnaround times, or delivery timeframes;
• how you measure performance (KPIs);
• what happens if the service levels aren’t met (for example, credits or other remedies).

In practice, an SLA is less about legal jargon and more about avoiding misunderstandings. It’s the “this is what you can expect from us” document - in writing.

Sometimes an SLA is a standalone document, but more often it sits alongside a broader services contract, like a Master Services Agreement or a general Service Agreement. Think of the main agreement as the “legal framework” and the SLA as the “operational detail”.

Is An SLA Legally Binding In New Zealand?

It can be, as long as it’s drafted and executed like a proper contract (or is incorporated correctly into one).

Generally, in New Zealand, a contract is enforceable if there is:

• agreement (offer and acceptance);
• consideration (something of value exchanged, usually payment for services);
• intention to create legal relations (usually assumed in business dealings); and
• certainty in the key terms (so it’s not too vague to enforce).

Where SLAs can get tricky is “certainty”. If your SLA uses loose language like “reasonable response times” or “best efforts support” without defining what those mean, it can be harder to enforce - and easier to argue about.

When Do New Zealand Businesses Actually Need Service Level Agreements?

You don’t need service level agreements for every single job. But if your service is ongoing, business-critical, or performance-sensitive, an SLA is usually a smart move.

Here are common scenarios where an SLA is worth having in place from day one.

1) Ongoing Managed Services Or Retainers

If you provide services on a monthly retainer (for example, IT support, digital marketing, bookkeeping, HR consulting, or maintenance services), clients often assume you’re “on call”. An SLA helps you define what’s included, what’s not, and how support works.

For tech and support providers, an IT Service Agreement plus a clear SLA is often the backbone of the entire client relationship.

2) High-Impact Operations Where Downtime Costs Money

If your customer’s business relies on your service to operate - think software, hosting, connectivity, payment systems, or logistics - your service levels need to be crystal clear.

Without an SLA, you may be exposed to unrealistic expectations, complaints, and “you cost us revenue” claims that could escalate quickly.

3) You’re Working With Larger Clients Or Government

Bigger organisations often expect formal service levels, reporting, and escalation processes. If you’re trying to win these contracts, having a robust SLA (and the ability to negotiate it confidently) can make you look more professional and reduce procurement delays.

4) You Need To Manage Client Behaviour As Well As Your Own

SLAs aren’t just about what you do. They can also set expectations for what the customer must do to help you deliver the service, such as:

• providing access to systems or premises;
• nominating authorised contacts;
• using a ticketing system correctly;
• responding within set timeframes to requests for information or approvals.

This is one of the most overlooked benefits of service level agreements: they can reduce delays caused by the customer, and protect you from being blamed when you’re waiting on them.

What Should You Include In Service Level Agreements?

The best SLAs are specific, measurable, and aligned with how you actually deliver your services. If it’s too complicated to follow day-to-day, it won’t help you (and it may create compliance risk if you can’t meet it).

Below are the clauses and concepts we commonly recommend including.

Service Scope (What You’re Delivering)

Start with a simple, plain-English description of the service. This should match your proposal or statement of work, and clearly outline:

• the services included;
• deliverables (if any);
• service hours (for example, business hours support vs 24/7);
• what is out of scope and will be billed separately (if applicable).

Scope is also important under New Zealand consumer law and fair trading rules. If you advertise a service, the description shouldn’t be misleading. The Fair Trading Act 1986 can apply if claims about your service levels are inaccurate or create a false impression.

Performance Metrics (KPIs) And Targets

This is the heart of service level agreements. Metrics need to be measurable. Common examples include:

• response time: how quickly you acknowledge a request (for example, within 2 business hours);
• resolution time: how quickly you fix an issue (often different based on severity);
• uptime/availability: particularly for online services (for example, 99.9% monthly uptime);
• delivery turnaround: for recurring outputs (reports delivered within X days);
• quality standards: accuracy thresholds, rework limits, or acceptance criteria.

A practical tip: if you’re using severity levels (P1/P2/P3, critical/major/minor), define them properly. Otherwise, everything becomes “urgent” the moment a client is stressed.

Support Process And Escalation

Even good providers have bad days - systems fail, people get sick, suppliers cause delays. Your SLA should set out how issues are handled, including:

• how customers lodge requests (email, portal, phone);
• the information they must provide;
• your triage process;
• escalation steps and timeframes (including senior escalation);
• what happens during major incidents.

This is also where you can manage expectations about “quiet work” versus “urgent interruptions”. If you don’t define the process, you may end up responding to scattered texts and late-night calls - and then arguing about whether you “responded in time”.

Service Credits, Remedies, And Limitations

If you miss a service level, what happens next?

Many SLAs include service credits (for example, a percentage discount on the monthly fee if uptime drops below a threshold). These can work well because they provide a predefined remedy without immediately escalating into a dispute.

But you need to be careful here:

• If the remedy is unclear, you may end up negotiating “compensation” every time something goes wrong.
• If the remedy is too generous, you may create commercial risk you can’t afford.
• If your SLA says credits are the exclusive remedy, make sure that approach is clearly drafted and consistent with the rest of your contract - and remember that statutory rights (like those under the Consumer Guarantees Act 1993) may still apply in some cases, unless validly contracted out where permitted.

This is also where limitation of liability clauses usually sit (often in the main agreement rather than the SLA). Getting this right is crucial - especially if your service could be linked to business interruption, lost profits, or downstream claims.

Reporting, Reviews, And Continuous Improvement

Service levels aren’t set-and-forget.

Consider including:

• monthly or quarterly reporting (what you report, how, and when);
• review meetings (frequency and attendee roles);
• a mechanism for updating the SLA as needs change.

If you’re planning to change service levels over time (for example, as you scale your team), it’s worth ensuring the contract includes a clear process for variations.

Privacy And Data Handling (If You Touch Personal Information)

Many service providers handle customer data in some form - names, emails, addresses, employee details, access credentials, usage analytics, and so on.

If that’s you, your service levels should align with your privacy commitments and security obligations. In New Zealand, the Privacy Act 2020 requires businesses to take reasonable steps to protect personal information, and there are mandatory reporting obligations for notifiable privacy breaches.

Depending on your setup, you may need a Privacy Policy and a Data processing agreement that matches how data is collected, stored, used, and shared - especially if you’re using subcontractors or overseas tools.

How Do SLAs Fit With Your Other Contracts And Legal Obligations?

A common mistake is treating service level agreements as a “nice extra” document that sits off to the side. In reality, your SLA needs to line up with your broader contract terms and your legal obligations - otherwise you can accidentally overpromise or create contradictions.

SLAs vs The Main Services Contract

Most businesses use a main services agreement (or master agreement) plus supporting documents (like SLAs and statements of work). The main agreement usually covers:

• fees and payment terms;
• term and termination rights;
• intellectual property ownership and licensing;
• confidentiality;
• limitations of liability;
• dispute resolution; and
• general legal “housekeeping” terms.

The SLA then provides the operational detail: timelines, service standards, and how support works.

What matters is priority. Your documents should say what happens if there’s an inconsistency between the SLA and the main agreement. If you don’t deal with this upfront, you can end up arguing about which document “wins”.

SLAs And Consumer Law Considerations

If you’re dealing with consumers (rather than business customers), you may also need to consider the Consumer Guarantees Act 1993. It creates automatic guarantees around services being carried out with reasonable care and skill, being fit for purpose, and completed within a reasonable time (among other things).

In some business-to-business deals, businesses can agree to contract out of the Consumer Guarantees Act - but only if the contracting-out clause meets the Act’s requirements and it’s fair and reasonable in the circumstances. If you can’t (or don’t) contract out, those statutory rights will sit alongside your contract and SLA.

Even if you’re primarily B2B, it’s still worth being careful about advertising claims. Overly ambitious SLA promises can create risk under the Fair Trading Act 1986 if they’re misleading or not supportable in practice.

SLAs And Subcontractors

If you rely on subcontractors to deliver parts of the service, your SLA should reflect reality - and your subcontractor contracts should align with what you’ve promised your customer.

For example, if you promise a 4-hour resolution time, but your subcontractor only works two days a week, you’re setting yourself up to fail.

This is one of those areas where it’s worth getting the whole contract suite reviewed together, not document-by-document. A targeted Contract review can help you spot mismatches before they turn into disputes.

Common SLA Mistakes (And How To Avoid Them)

Service level agreements are meant to reduce conflict - but poorly drafted SLAs can do the opposite. Here are some of the most common issues we see for small businesses.

1) Vague Commitments That Can’t Be Measured

Phrases like “fast support” or “high availability” sound good, but they don’t hold up when there’s a disagreement.

Fix: use measurable commitments (timeframes, percentages, defined severity categories) and define key terms.

2) Overpromising To Win The Deal

It’s tempting to agree to aggressive response times because you want the customer to sign. But if your team can’t realistically deliver, you’re creating ongoing stress - and possibly liability exposure.

Fix: draft service levels that match your resourcing and pricing. If a client wants premium SLAs, you can offer a premium tier.

3) Forgetting Exclusions And Dependencies

If you don’t list exclusions, customers can assume “everything” is covered. If you don’t list dependencies, you may be blamed for delays caused by missing information or access.

Fix: clearly state exclusions and what the customer must provide to enable you to meet the service levels.

4) No Clear Remedy (So Every Issue Becomes A Negotiation)

If your SLA says “we will do our best” but doesn’t say what happens when targets aren’t met, you can end up in constant back-and-forth about refunds or compensation.

Fix: agree on service credits (if appropriate), and ensure your limitation of liability clauses support your intended risk allocation (noting that some statutory rights may not be excluded in certain situations).

5) Using A Template That Doesn’t Match Your Business

Generic templates often include service levels that don’t reflect how you actually deliver the service - or they leave out key protections (like priority rules, variation processes, or customer responsibilities).

Fix: have the SLA drafted or reviewed for your specific service model, pricing, and risk profile. It’s one of those documents that can save you a lot more than it costs.

Key Takeaways

• Service level agreements set clear, measurable expectations about how your services will be delivered, including response times, resolution times, availability, and support processes.
• An SLA can be legally binding in New Zealand if it’s properly incorporated into a broader contract and drafted with enough certainty to be enforceable.
• The most useful SLAs define scope, service metrics, escalation procedures, remedies (like service credits), reporting, and customer responsibilities.
• Your SLA should align with your main contract terms (such as limitation of liability, termination, and priority rules) so you don’t create contradictions.
• If your services involve handling personal information, make sure your SLA matches your privacy and security commitments under the Privacy Act 2020.
• Avoid vague wording and overpromising - realistic SLAs that match your operations are usually better for client relationships and long-term growth.

If you’d like help drafting or reviewing service level agreements so you’re protected from day one, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

This article is general information only and does not constitute legal advice. For advice about your specific situation, get in touch with a lawyer.