Contract For Services In NZ: Differences From A Contract Of Service & Key Terms

If you’re hiring help for your business (a freelancer, consultant, tradie, developer, designer, or other specialist), it’s easy to assume a “quick agreement” is enough.

But in New Zealand, the type of agreement you use - whether it’s a contract for services or a contract of service - can have real consequences for your costs, your risk, and your compliance obligations.

Getting this right from day one doesn’t just prevent disputes - it helps you build a business that can scale confidently, because you’ll know who is an employee, who is a contractor, and what rules apply to each relationship.

What Is A Contract For Services?

A contract for services is the agreement you use when you engage an independent contractor to provide services to your business.

In simple terms, it’s usually used when you’re paying someone to deliver a defined service or outcome, but they’re not your employee.

Common examples include engaging:

• a graphic designer to create your brand assets
• a marketing consultant to manage campaigns for three months
• a software developer to build and maintain an app
• a bookkeeper to do monthly accounts
• a cleaner for regular cleaning services
• a tradie to complete a specific job

Because the contractor is (generally) running their own business, a contract for services usually focuses on:

• scope of services (what they will deliver, and what they won’t)
• fees and invoicing
• timing (deadlines, milestones, and availability)
• quality standards and rework
• ownership of work product (like IP and deliverables)
• confidentiality
• liability and risk allocation
• how the relationship can end

If you’re engaging contractors regularly, it’s worth having a properly drafted Contractors Agreement (or a service agreement) that matches how your business actually operates, rather than relying on a generic template.

Contract For Services Vs Contract Of Service: What’s The Difference?

This is the key distinction many small businesses miss.

A contract of service is typically what you use for an employee relationship. If someone is working for you as part of your business (rather than running their own), they may be an employee - even if you call them a “contractor”.

In New Zealand, this isn’t decided by the label in the agreement alone. Courts and authorities can look at the real nature of the relationship, using a range of factors (often described as a multi-factor test) to assess whether the worker is truly in business on their own account, or really working as part of your business.

An employee relationship generally requires a written employment agreement, and it comes with specific statutory rights and obligations (like leave entitlements and minimum employment standards).

In contrast, a contract for services is for independent contractors, where the relationship is usually more “business-to-business”.

Why This Classification Matters For Your Business

If you get the classification wrong, it can cause serious headaches later - particularly if a worker claims they were really an employee all along.

That can trigger issues like:

• claims for unpaid holiday pay or other entitlements
• tax and payroll complications (for example, whether PAYE should have been applied - speak with your accountant or check IRD guidance for tax treatment)
• problems if you terminate the relationship without a fair process
• confusion about who owns the work created
• unexpected liability if something goes wrong

Even if you’ve signed a contractor agreement, a court or authority can look at the real nature of the working relationship. So the practical day-to-day arrangement needs to line up with what the contract says.

Quick Comparison: Contractor Vs Employee

Every situation is different, but here’s a practical way to think about it (noting that no single factor is decisive on its own).

• Control: Employees are usually told how, when, and where to work. Contractors often decide how to deliver the service.
• Integration: Employees are integrated into your business (team, systems, ongoing duties). Contractors are typically engaged for specific outputs.
• Tools and equipment: Employees often use the business’ tools/systems. Contractors often supply their own tools.
• Ability to subcontract: Contractors may be able to delegate or subcontract (depending on the agreement). Employees generally can’t.
• Financial risk: Contractors often carry more commercial risk and manage their own expenses; employees don’t usually carry that risk.

If you’re actually hiring someone in an employee-style role, it’s safer to use an Employment Contract rather than trying to force the relationship into a contractor model.

When Should You Use A Contract For Services In NZ?

A contract for services makes sense when you want flexibility and you’re engaging a specialist to deliver defined work - without bringing them into your business as staff.

As a small business owner, you might use a contract for services when you:

• need extra help during a busy season (without hiring permanently)
• need a specialist skill set (like IT, HR consulting, or design) for a project
• are testing a new product or service and want to keep overheads lean
• work with contractors across different regions

But it’s important to match the contract to reality. If you start setting fixed hours, requiring permission for leave, and managing performance like an employer would, the relationship can drift into “employee territory”.

If you’re unsure where the line is, it’s worth getting advice early. It’s almost always easier (and cheaper) to set the relationship up properly than to fix it mid-dispute.

What Should A Contract For Services Include?

A well-drafted contract for services is more than “you do work, we pay you”. It’s your playbook for what happens when things go well and when they don’t.

Below are the clauses we commonly recommend including, depending on your industry and risk profile.

1. Parties And Relationship (Independent Contractor Status)

Start with the basics: who the parties are, and a clear statement that the contractor is engaged as an independent contractor (not as an employee, agent, or partner).

This clause won’t magically prevent misclassification on its own, but it’s still important because it sets expectations and supports the intended structure.

2. Scope Of Services (And What’s Out Of Scope)

Scope is where many disputes begin, especially with project work.

Your contract should clearly cover:

• what services are included
• deliverables (what gets handed over at the end)
• milestones, timelines, and dependencies (what you need to provide to enable them to do the work)
• what counts as a variation or extra work

If you want extra clarity, you can attach a statement of work (SOW) or schedule that sets out the practical details.

3. Fees, Invoicing, And Expenses

This section should answer (in plain English): how much are you paying, when, and under what conditions?

Typical points to include:

• hourly rate vs fixed fee
• when invoices can be issued (e.g. milestone-based)
• payment terms (e.g. 7 days, 14 days)
• whether expenses are included or reimbursed
• what happens if you dispute an invoice

For ongoing service providers, it can also be helpful to align these terms with broader customer-facing Terms Of Trade or internal procurement processes, so your business stays consistent.

4. Timeframes, Availability, And Service Levels

If timing matters (and it usually does), you’ll want clear expectations on:

• start date and end date (or project completion triggers)
• expected turnaround times
• response times for communications
• service levels (especially for IT or managed services)

For service-based work that needs measurable standards, a Service Level Agreement style schedule can be a practical way to lock in performance expectations without cluttering the main agreement.

5. Confidentiality And Handling Sensitive Information

Most contractors will end up seeing business-sensitive information - pricing, client lists, strategies, systems, or product roadmaps.

Your contract should clearly state:

• what counts as confidential information
• how the contractor must store and protect it
• when they can disclose it (if ever)
• what happens on termination (returning or deleting data)

In practice, confidentiality is often backed by a separate Non-Disclosure Agreement, especially if you’re sharing information before the contractor is formally engaged.

6. Intellectual Property (Who Owns The Work?)

This is one of the biggest “hidden traps” for business owners.

Many people assume: “If I paid for it, I own it.” But that’s not always how IP works.

If your contractor creates materials for you (like code, designs, written content, systems, training resources, or processes), your agreement should cover:

• what IP the contractor already owned before the project (pre-existing IP)
• what new IP is created during the engagement (developed IP)
• whether that developed IP is assigned to you, licensed to you, or retained by the contractor
• any limits on how you can use the deliverables

This needs to be drafted carefully, particularly for software and creative work where contractors may reuse frameworks, templates, or reusable tools across clients.

7. Compliance With Laws (And Your Business Policies)

Even if someone is a contractor, your business still has legal obligations around the way work is performed and the way information is handled.

Depending on what the contractor is doing, your agreement may need to deal with compliance obligations under laws such as:

• Privacy Act 2020 (if they handle personal information about customers, clients, or staff)
• Health and Safety at Work Act 2015 (especially for on-site work or higher-risk industries)
• Fair Trading Act 1986 (if they are marketing or making claims on your behalf)

This section can also include a requirement to comply with your internal policies (like security policies, acceptable use rules, or brand guidelines) where relevant.

8. Liability, Indemnities, And Insurance

When you engage a contractor, you’re often relying on their skill and expertise. If they make a mistake, you’ll want the contract to clearly allocate who carries what risk.

Depending on the work, you might include:

• limits of liability (for example, a cap tied to fees paid)
• exclusions (e.g. excluding liability for indirect or consequential loss)
• indemnities (e.g. if their breach causes third-party claims)
• an obligation to maintain insurance (like professional indemnity or public liability)

These clauses need to be balanced - too one-sided and the contractor may push back, but too vague and you might not be protected when it counts.

9. Restraints, Non-Solicitation, And Conflicts

Small businesses often share valuable relationships with contractors - your clients, suppliers, or staff.

Depending on the engagement, you may want clauses dealing with:

• conflicts of interest (especially if they work with competitors)
• non-solicitation (not poaching your clients or team)
• restraints of trade (in limited, reasonable circumstances)

These clauses can be tricky to enforce if they’re too broad, so they should be drafted with your particular business model in mind.

10. Term, Termination, And What Happens At The End

One of the most practical parts of any contract is: how do we end this cleanly if it’s not working out?

A contract for services should address:

• the term (fixed project vs ongoing)
• termination for convenience (ending without breach) and required notice
• termination for breach (and whether there is a cure period)
• handover obligations (files, logins, work-in-progress)
• final invoices and payment timing
• ongoing obligations (confidentiality and IP clauses often survive termination)

If you’ve ever been stuck with a contractor who “owns” the key system access or hasn’t handed over deliverables, you’ll know why this section matters.

Common Mistakes Small Businesses Make With Contracts For Services

Most disputes we see aren’t because the business owner didn’t care - it’s because they moved fast, trusted the relationship, and didn’t want to overcomplicate things.

Here are a few common pitfalls to avoid.

Using A Contractor Agreement But Treating The Person Like An Employee

If you require set hours, manage performance like a staff member, and roll them into internal processes (without contractor-style independence), you can increase the risk that the relationship is treated as a contract of service in practice.

That can create issues later if the relationship ends badly.

Not Defining The Scope Clearly

“Do our marketing” or “build our website” sounds clear until expectations diverge. A clear scope (plus variation process) can save you a lot of time and money.

Forgetting IP Ownership

This is a big one. If you don’t address IP properly, you may end up with limited rights to use what you paid for - or find that you can’t easily sell the business or bring the work in-house later.

Not Addressing Confidentiality And Data Security

If your contractor accesses customer data, pricing, or strategy documents, you should treat confidentiality and information security as non-negotiable business foundations.

Relying On Templates That Don’t Match Your Business

A generic template might look professional, but if it doesn’t reflect what you actually do (and how you operate), it can leave gaps - especially around termination, liability, and deliverables.

This is where tailored advice can make a huge difference, particularly if you’re scaling and engaging contractors regularly.

Key Takeaways

• A contract for services is typically used to engage an independent contractor, while a contract of service is generally an employment agreement.
• Getting the classification right matters because a worker can be treated as an employee based on the real nature of the relationship, which may expose your business to costs and disputes (including claims for employee-style entitlements).
• A strong contract for services should clearly cover the scope, fees, timelines, confidentiality, IP ownership, liability, and termination.
• Make sure the day-to-day working arrangement matches the contract - calling someone a “contractor” won’t help if they’re treated like an employee in practice.
• Contracts are part of your legal foundations, and putting the right agreement in place early helps you stay protected as your business grows.

If you’d like help putting a contract for services in place (or reviewing a contractor agreement before you sign), reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.