How To Define Your Scope Of Work In A New Zealand Service Agreement

If you sell services, your “scope of work” is where your service agreement either saves you… or causes you headaches later.

Most disputes between small businesses and clients don’t start because someone is trying to be difficult. They start because each side had a different (but reasonable) understanding of what was included, what wasn’t, and what “done” actually means.

That’s why getting the scope of work right in your service agreement matters. It’s not just a box-ticking exercise - it’s one of the simplest ways to protect your time, your cashflow, and your reputation from day one.

Below, we’ll walk you through what a scope of work is in a New Zealand service agreement, what to include, and how to write it in a way that’s clear enough to avoid scope creep (without scaring clients off).

What Is A Scope Of Work In A Service Agreement (And Why Does It Matter In NZ)?

A scope of work (often shortened to “SOW”) is the part of your service agreement that spells out exactly what you’re providing to your client.

In plain terms, it answers questions like:

• What are you actually delivering?
• When will you deliver it?
• What do you need from the client?
• What is not included?
• How will changes be handled (and paid for)?

Even if you’ve had a friendly conversation, exchanged a few emails, or sent a quick quote, putting a clear scope of work inside a Service Agreement helps make expectations easier to manage and (if needed) rely on later.

From a legal and practical risk perspective, a clear scope of work in your service agreement can help you:

• Reduce misunderstandings about what the client is buying
• Limit scope creep (extra work that “somehow” becomes expected)
• Link payment to deliverables so your invoices are easier to justify
• Set objective acceptance criteria so projects don’t drag on forever
• Support your position if a dispute arises about performance or non-payment

And in New Zealand, that clarity matters because contracts can be formed (and varied) through a mix of documents and communications - including proposals, emails and messages - depending on what was agreed and the surrounding circumstances. Putting the scope in one clear place helps align everything.

What Problems Does A Vague Scope Of Work Cause For Small Businesses?

If you’ve ever felt like a project “kept growing” while the price stayed the same, you’ve seen scope problems in real life.

Here are some of the most common issues we see when the scope isn’t tight enough.

Scope Creep (And Free Work You Didn’t Price For)

Scope creep is when the client asks for “just one more thing” - and then another - and another - until you’re doing work you never agreed to include.

It often happens when the scope:

• doesn’t define deliverables clearly
• doesn’t include limits (for example, number of revisions)
• doesn’t explain how variations are quoted and approved

Payment Disputes

If your agreement says “we’ll provide marketing services” and your invoice says “marketing services”, a client can still argue they didn’t get what they expected. A detailed scope makes it far easier to show you delivered what was agreed.

This becomes even more important if your payment terms involve deposits, milestone payments, or progress invoicing.

Endless Revisions And “Not Quite Happy Yet” Delays

Without acceptance criteria and a defined revision process, a client can keep requesting changes indefinitely - even after you’ve delivered something reasonable.

A well-drafted scope of work section should make it clear what “approved” means, how feedback is provided, and what happens if the client goes quiet.

Consumer Law Or Fair Trading Risk If You Overpromise

If you advertise or describe your services in a way that creates unrealistic expectations, you may trigger issues under the Fair Trading Act 1986 (for misleading or deceptive conduct).

This doesn’t mean you can’t market confidently - it just means your scope should line up with what you’ve represented to the client (including in proposals, ads, and sales calls).

What Should You Include In A Scope Of Work Service Agreement?

A good scope of work isn’t necessarily “long”. It’s specific, and it removes the grey areas that cause problems later.

Here’s a practical checklist of clauses and details to consider including in your scope of work section.

1. A Plain-English Description Of The Services

Start with a short overview of what the client is engaging you to do. Keep it simple, then expand into specifics.

For example, instead of: “Provide consulting services”, consider: “Provide operational consulting to improve inventory and dispatch workflows, including process mapping and a final recommendations report.”

2. Deliverables (What You Will Hand Over)

Deliverables are the tangible outputs your client will receive. These can be documents, designs, reports, code, training sessions, or even ongoing support.

Be as concrete as you can, for example:

• “One brand style guide in PDF format (10–15 pages)”
• “Two blog articles per month (1,000–1,200 words each)”
• “A monthly performance report delivered by the 5th business day of each month”

If you’re also transferring ownership of work product, you’ll often want IP terms to match. Depending on the arrangement, you may need an IP Assignment or a licence model instead.

3. What’s Excluded (Your Boundaries)

This is one of the most important (and most overlooked) parts of the scope.

A simple “Out of Scope” list helps prevent the classic: “Oh, I assumed that was included.”

Examples might include:

• printing costs
• ad spend
• third-party software subscriptions
• travel and accommodation
• implementation of recommendations (if you’re only advising)
• website hosting, maintenance, or ongoing support (if it’s a one-off build)

Being clear here doesn’t make you “difficult” - it makes you professional.

4. Assumptions And Client Responsibilities

Many projects only run smoothly if the client does their part. So your scope should spell out what you need from them and when.

For example:

• providing access to systems, accounts, or premises
• supplying content, images, or product information by certain dates
• reviewing drafts and giving feedback within a set timeframe
• having a single point of contact with authority to approve decisions

This also helps if there are delays. If the client doesn’t provide required input, you may need the agreement to allow timeline changes (and potentially additional fees).

5. Timeline, Milestones, And Dependencies

For one-off projects, the scope should include:

• start date
• key milestone dates
• final delivery date (or estimated timeframe)
• dependencies (for example, “timeline assumes client feedback within 3 business days”)

If your agreement uses “business days”, define it properly so you’re both aligned (particularly around public holidays). You can also sanity-check this concept against the standard meaning of Business Day.

6. Fees, Invoicing, And What Triggers Payment

Your scope of work and payment terms should line up neatly.

Common approaches include:

• Fixed fee (with clear boundaries and a variation process)
• Hourly / daily rate (with reporting and optional caps)
• Milestone-based (payments due on delivery/acceptance of milestones)
• Retainer (a set amount of service time/value per month)

Where possible, define:

• what counts as billable time
• minimum increments (for example, 15-minute blocks)
• what happens if the client pauses the project
• late payment consequences (if included in your broader agreement)

7. Acceptance Criteria And The Review Process

This is where you define what “done” looks like.

Depending on the service, acceptance criteria could include:

• the client confirms in writing that deliverables meet the agreed requirements
• a time-based acceptance rule (for example, “deemed accepted if no feedback within 5 business days”)
• objective standards (file formats, performance benchmarks, compliance requirements, etc.)

This is especially useful when you’re delivering creative work, technical deliverables, or anything subjective.

8. Variations (How Changes Are Managed)

Changes are normal. The issue is when changes aren’t priced or documented.

A good variation clause typically covers:

• how the client requests a change (in writing)
• how you will quote the change (time and cost impact)
• when the change becomes binding (for example, once the client approves the quote)
• whether you can pause work until the variation is approved

If your services are delivered through a structured document format, your scope might also be attached as an annexure and updated through a contract change process as the project evolves.

How Do You Write A Scope Of Work That’s Clear (But Still Flexible)?

Small businesses often worry that a detailed scope will feel “too formal” and scare off clients. In practice, clarity usually has the opposite effect - it builds trust and makes it easier for the client to say yes.

The trick is to write a scope that is:

• specific about deliverables and limits
• flexible about how changes can happen
• easy for a non-lawyer to understand

Use Simple Structure And Headings

Clients are more likely to read the scope if it’s scannable. Use clear headings like:

• Services
• Deliverables
• Out Of Scope
• Timeline
• Fees
• Assumptions
• Variations

Define Key Terms Once (Then Reuse Them Consistently)

If you call something a “Deliverable” in one section and “Output” elsewhere, you create room for confusion. Pick one label and stick to it.

Be Careful With Words Like “Support”, “Advice”, And “Help”

These are common “grey words” that can unintentionally broaden your obligations.

Instead of saying: “We’ll provide support”, consider specifying:

• support channels (email only? phone?)
• support hours
• response times (best endeavours vs guaranteed)
• what counts as support vs new work

Include A Clear “Out Of Scope” List (Even If It’s Short)

Even a few bullets can prevent misunderstandings. It also makes your variation process feel normal and expected: “If it’s not in scope, we can quote it.”

Make Room For Growth Without Leaving It Wide Open

If you think the scope may expand, don’t keep it vague “just in case”. A better approach is:

• keep the base scope tight
• include optional add-ons (with pricing or a pricing method)
• include a variation process that’s quick and workable

This is where well-drafted Business Terms and a tailored service agreement can save you a lot of back-and-forth.

What NZ Laws Should You Keep In Mind When Defining Scope?

Most scope of work issues are commercial, but there are a few key legal angles in New Zealand that are worth keeping in mind when you draft your scope.

Fair Trading Act 1986 (Don’t Overpromise)

If your sales materials, website, or proposal says the client will get a particular outcome, you need to make sure your scope matches that representation.

For example, if you say “we guarantee a 3x increase in sales” but the scope is really just “we’ll run some ads”, that mismatch can create risk. Safer framing is usually to describe what you’ll do (inputs and deliverables), rather than guaranteeing outcomes you can’t fully control.

Consumer Guarantees Act 1993 (If You’re Dealing With Consumers)

If your client is acquiring services for personal or household use (rather than business use), consumer guarantees may apply automatically.

Many B2B service agreements will include terms about who the services are for (business purposes) and, where legally allowed, may contract out of the Consumer Guarantees Act for business clients. This needs to be done correctly, so it’s worth getting advice for your specific setup.

Privacy Act 2020 (If Your Services Involve Personal Data)

If the scope involves handling customer lists, employee details, patient information, or any identifiable personal data, you should think about:

• what information you’ll access
• where it will be stored
• who can see it (including subcontractors)
• security measures and breach response

In those cases, having a Privacy Policy (and sometimes additional contract terms) can be an important part of your legal foundations.

Health And Safety (If You’re Delivering Services On Site)

If you (or your contractors) work on a client site, your scope might need to address practical safety matters like induction requirements, site access rules, and who is responsible for what.

This helps avoid awkward situations where you’re expected to do work in unsafe conditions or without appropriate information.

Key Takeaways

• A clear scope of work in your service agreement sets out what you will deliver, what you won’t deliver, and how changes are handled - which is key to avoiding disputes and protecting your time.
• Your scope should cover deliverables, exclusions, timelines, client responsibilities, fees, acceptance criteria, and a variation process that works in real life.
• Most scope problems show up as scope creep, payment disputes, or endless revision cycles - all of which are easier to prevent than fix later.
• In New Zealand, your marketing and promises should align with your scope to reduce risk under laws like the Fair Trading Act 1986, and privacy obligations may apply if personal data is involved.
• A scope that’s specific doesn’t have to be “heavy” - clear headings, plain English, and defined boundaries can make your agreement easier for clients to understand and easier for you to rely on.
• If you want your scope to actually protect you (not just look professional), it should be tailored to how you deliver your services and how your clients typically request changes.

Note: This article is general information only and isn’t legal advice.

If you’d like help drafting or reviewing a scope of work for your service agreement, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.