Must-Have Clauses For Consultant Contracts In New Zealand

If you’re running a small business, bringing in a consultant can be a smart (and fast) way to get specialist skills without hiring someone full-time.

But there’s a catch: if your agreement isn’t clear, “quick help” can turn into delayed projects, arguments over fees, or a messy dispute about who owns the work the consultant created.

A well-drafted consultant contract protects your business from day one. It sets expectations, reduces risk, and gives you a clear path if the relationship doesn’t work out.

Below, we’ll walk through the must-have clauses to include in consultant contracts in New Zealand, written for business owners who want practical guidance (without the legal jargon).

What Is A Consultant Contract (And When Do You Need One)?

A consultant contract (sometimes called a consulting agreement) is a written agreement where your business engages an independent consultant to provide services.

In simple terms, it covers things like:

• What the consultant is doing for you (scope of services)
• When they’ll do it (timeframes and milestones)
• How they’ll do it (deliverables and standards)
• How much you’ll pay (fees and invoicing)
• What happens if things go wrong (termination, liability, disputes)

You’ll usually want consultant contracts whenever you’re engaging someone who:

• isn’t on your payroll as an employee (for example, a marketing strategist, IT specialist, HR consultant, or business coach)
• is doing project-based work that has clear deliverables
• will have access to confidential business information (like pricing, client lists, financials, or product plans)
• is creating something valuable (like reports, templates, software, designs, or written content)

Even if the consultant is someone you trust, a contract isn’t about assuming the worst. It’s about making sure you’re both on the same page before money and deadlines are involved.

For many small businesses, a tailored Consulting Agreement is the simplest way to get those protections in place.

How Do Consultant Contracts Differ From Employment Agreements?

This is one of the biggest issues we see in practice: a business thinks they’ve hired a “consultant”, but the working arrangement looks (legally) like employment.

Why does this matter? Because employees and contractors/consultants are treated differently under New Zealand law, including around leave, tax withholding, and employer obligations.

There isn’t a single deciding factor. Instead, the overall relationship is assessed. If you’re giving the person fixed hours, close supervision, ongoing work, and they’re integrated into your business like staff, it can start to look like employment (even if the contract uses the word “consultant”).

That’s why your paperwork and your real-world working arrangement need to match.

As a starting point:

• Employees are typically paid wages/salary, are part of your organisation, and are covered by employment law protections.
• Consultants generally run their own business, invoice you for services, control how they perform the work, and take on more commercial risk.

If your consultant arrangement is actually more like a contractor relationship (rather than a one-off consultant project), you might be better protected with a more formal Contractors Agreement that matches the reality of the engagement.

If you’re unsure, it’s worth getting advice early. Misclassification can create expensive problems later-particularly if the relationship ends badly. (And if you have questions about tax treatment, PAYE, or withholding, it’s also worth checking in with your accountant or the IRD, as this article isn’t tax advice.)

Must‑Have Clauses In Consultant Contracts (NZ)

Good consultant contracts aren’t just “admin”. They’re your risk management tool. The clauses below are the ones we generally recommend you consider for most consulting engagements (with the exact drafting depending on your industry and the type of work).

1) Scope Of Services (What Exactly Are You Buying?)

Vague scope is one of the fastest ways to end up with scope creep (and a consultant who feels underpaid or a business who feels short-changed).

Your consultant contract should clearly describe:

• the services being provided (and what’s not included)
• assumptions (for example, you’ll provide access to systems or key staff)
• any limitations (for example, “advisory only” vs implementation)
• how additional work is approved (for example, written change requests)

If you have multiple projects or rolling work, you can structure this with a main agreement and separate Statements of Work (SOWs) for each project.

2) Deliverables, Milestones, And Acceptance

“Deliverables” are the tangible outputs you expect-like a report, strategy document, training session, code repository, or marketing plan.

Your agreement should cover:

• what deliverables will be provided
• due dates and milestone timelines
• what information you need to provide (and by when)
• how you’ll confirm the deliverable is acceptable (and what happens if it isn’t)

This is especially important when your consultant’s output affects revenue, compliance, or customer experience.

3) Fees, Invoicing, And Payment Terms

This section should be crystal clear, because payment disputes can damage otherwise good working relationships.

Common points to include:

• fee structure (fixed fee, hourly/daily rate, retainer, milestone payments)
• when invoices can be issued
• payment timeframe (for example, 7 or 14 days)
• whether GST applies
• what happens if payment is late (interest, suspension of work, debt recovery costs)

If you’re paying partly based on milestones or outcomes, spell out the trigger for payment. Ambiguity here often leads to “but I thought…” disagreements.

4) Expenses (And Pre-Approval Rules)

Many consultants incur expenses like travel, accommodation, software subscriptions, or subcontractor costs.

To avoid surprise invoices, set out:

• what expenses are reimbursable
• whether expenses need your written pre-approval
• receipt and reporting requirements
• spend caps (if relevant)

5) Term, Renewal, And Time Commitment

Your consultant contracts should state when the engagement starts and ends.

You might include:

• a fixed term (for example, 3 months)
• an ongoing term that can be ended on notice
• renewal rules (automatic renewal vs new agreement required)
• minimum availability expectations (if needed)

Be careful with clauses that look like employment (for example, requiring set hours every week). If you do need set availability, get advice on how to structure this without creating unintended employment risk.

6) Confidentiality

If a consultant will see your pricing, customer data, internal processes, or future plans, confidentiality protections are essential.

Your consultant contract should cover:

• what counts as confidential information
• how the consultant must store and protect it
• who they can share it with (if anyone)
• what happens at the end of the engagement (return or destruction of information)

In many cases, confidentiality is important enough that you might also use a standalone Non-Disclosure Agreement-for example, before you share information during early discussions.

7) Intellectual Property (IP) Ownership

This is a big one for small businesses.

Many business owners assume: “If I pay for it, I own it.” But IP ownership can be more complicated than that-especially if the contract is silent or unclear, and depending on the circumstances of the engagement.

Your consultant contract should address:

• whether all new IP created during the engagement is assigned to your business
• whether the consultant keeps ownership but grants you a licence to use it
• whether the consultant is allowed to reuse templates, tools, or “background IP” they already had
• what rights you have to modify, commercialise, or sub-licence the work

If you want ownership transferred, you’ll often need proper IP assignment wording (and sometimes a separate deed), such as an IP Assignment.

If the consultant is retaining ownership but allowing you to use the work, you may need an IP Licence clause that clearly sets out how and where you can use it (and for how long).

8) Subcontracting And Delegation

Some consultants work with a small team, or outsource parts of the work to trusted subcontractors.

If you’re expecting a specific person to do the work (because of their expertise), your contract should say whether subcontracting is allowed.

Common approaches include:

• No subcontracting without your written approval
• Subcontracting allowed, but the consultant remains responsible for quality and delivery
• Named subcontractors approved upfront

This clause matters for quality control, confidentiality, and privacy compliance.

9) Warranties And Standard Of Care

Warranties are promises about the standard of work and how services will be delivered.

Examples you might include:

• the consultant will perform services with reasonable care and skill
• deliverables will not knowingly infringe third-party IP rights
• the consultant will comply with applicable laws
• any required licences, qualifications, or insurances are in place

These clauses help you set minimum standards and create leverage if the work is poor or exposes your business to risk.

10) Liability, Indemnities, And Insurance

Liability clauses are where you decide (in advance) who pays if something goes wrong.

Depending on the type of consulting work, you may want to address:

• caps on liability (for example, fees paid in the last X months)
• exclusions of indirect or consequential loss
• indemnities for third-party claims (for example, IP infringement)
• required insurance (professional indemnity, public liability, cyber insurance)

This is also where generic templates often fail. Liability needs to match the reality of your risk. For example, an IT consultant with access to sensitive data can create a very different risk profile to a leadership coach running a one-off workshop.

11) Dispute Resolution

Even with the best relationships, disagreements happen-especially when deadlines, invoices, or expectations are involved.

A good dispute resolution clause can reduce the chance of a blow-up by setting a clear process, such as:

• good faith negotiation between decision-makers
• mediation before court proceedings
• which country’s laws apply (New Zealand) and which courts have jurisdiction

This can save time, cost, and stress if you ever need to enforce the agreement.

Managing Risk: Privacy, IP, And Compliance

Many consultant engagements involve sensitive information-whether that’s customer details, employee records, or confidential business plans.

That’s why consultant contracts should work alongside your wider compliance obligations, rather than sitting in a vacuum.

Privacy And Data Handling

If your consultant will collect, access, store, or process personal information (for example, customer lists, email addresses, health information, or employee data), you’ll want contract terms that align with the Privacy Act 2020.

Practically, your consultant contract can include:

• limits on what personal information the consultant can access
• security requirements (passwords, encryption, secure storage)
• rules around overseas storage or cloud tools
• breach notification obligations (if something goes wrong)
• return/deletion of data at the end of the engagement

If you collect customer data through your website or systems, it’s also worth checking you have a fit-for-purpose Privacy Policy, because your external contractors and consultants can become part of your privacy risk profile.

Fair Trading And Marketing Claims

If your consultant is doing marketing, lead generation, or sales strategy, it’s worth remembering your business can still be responsible for what gets published under your brand.

In New Zealand, the Fair Trading Act 1986 prohibits misleading or deceptive conduct. So if a consultant creates ad copy, website claims, testimonials, or pricing representations, you’ll want clear review and approval processes (and contract wording that makes responsibilities clear).

Who Owns The Work Product?

We mentioned IP above, but it’s worth repeating: ownership of deliverables is one of the most common pressure points in consultant contracts.

Imagine this: your business pays a consultant to develop a process manual, a set of training slides, and a customer onboarding workflow. Six months later, you want to roll it out across new locations or license it to partners. If your contract doesn’t clearly assign IP (or give you the right licence), you may not be able to use it the way you planned.

This is exactly why it’s worth getting the IP clause right from the start.

Getting Paid And Ending The Relationship Cleanly

One of the most practical purposes of consultant contracts is making sure you can run your business confidently even if the relationship changes.

Payment Protection And “Pause Work” Rights

If you’re engaging consultants regularly, it’s common to include a right to pause work if invoices aren’t paid on time. This can be a fair way to manage cashflow without immediately terminating the agreement.

If your consultant contract is part of a broader engagement model (for example, ongoing business services), a more general Service Agreement structure can help keep your payment, scope, and delivery terms consistent.

Termination For Convenience And For Cause

Most small businesses want the ability to end the arrangement if priorities change-or if the consultant isn’t delivering.

Your contract should usually cover:

• Termination for convenience: you can end the contract on notice (for example, 7 or 14 days)
• Termination for cause: immediate termination for serious issues (for example, breach of confidentiality, non-payment, misconduct, or repeated failure to meet milestones)
• What happens on termination: final invoices, handover requirements, return of confidential info, IP transfer, and access removal

If the consultant is embedded in your operations (for example, ongoing IT support), consider adding handover obligations so you’re not left stranded.

Restraints And Non-Solicitation (If Appropriate)

In some cases, you may want to stop a consultant from:

• poaching your staff
• soliciting your clients
• using your confidential methods to compete directly with you

These clauses need to be drafted carefully. Overly broad restraints can be hard to enforce, and what’s “reasonable” depends heavily on the specific facts (including the industry, duration, geography, and the consultant’s role), so it’s worth getting advice before relying on them.

Choosing The Right Contract Structure

Not every engagement needs the same format.

• If the work is ongoing and varied, a Master Services Agreement can be a practical way to handle overarching legal terms, with individual SOWs for each project.
• If it’s a one-off engagement with a clear output, a straightforward consulting agreement may be enough.

The key is that your contract structure should match how you actually work with consultants-so you’re protected in practice, not just on paper.

Key Takeaways

• Consultant contracts help protect your business by setting clear scope, deliverables, fees, and expectations from day one.
• Make sure your consultant arrangement doesn’t accidentally look like an employment relationship, as misclassification can create legal and tax risks.
• Must-have clauses typically include scope, milestones/acceptance, fees and expenses, term, confidentiality, IP ownership/licensing, subcontracting rules, warranties, liability, and dispute resolution.
• IP is one of the most common friction points-if you want to own what the consultant creates, your consultant contract needs clear assignment wording.
• If the consultant will handle personal information, your contract should align with the Privacy Act 2020 and your privacy processes.
• A practical termination and handover process can save you major headaches if the relationship ends or your business priorities change.

If you’d like help drafting or reviewing consultant contracts for your business, we’re here to help. You can reach us on 0800 002 184 or email team@sprintlaw.co.nz for a free, no-obligations chat.