What Is A Consultancy Agreement? (2026 Updated)

Hiring a consultant can be a game-changer for your business. Maybe you’re bringing in a marketing specialist to launch a new product, a software developer to build a platform, or a finance expert to help you raise capital.

But here’s the thing: “We’ll just agree over email” can get messy fast. If the scope changes, deadlines slip, or there’s a disagreement about payment or ownership of work, you’ll want something more solid to fall back on.

That’s where a consultancy agreement comes in.

This guide (updated for current New Zealand business conditions and common contracting practices) breaks down what a consultancy agreement is, when you should use one, what to include, and the common traps we see businesses fall into.

What Is A Consultancy Agreement (And When Do You Need One)?

A consultancy agreement is a written contract between a business (you) and a consultant (an independent contractor) that sets out:

• what the consultant will do (and what they won’t do)
• how and when they’ll be paid
• who owns the work product (like IP, reports, designs, code, or strategies)
• confidentiality and privacy expectations
• how either party can end the relationship
• who is responsible if something goes wrong

You’ll typically use a consultancy agreement when you’re engaging someone who is not your employee, and you want clear boundaries around deliverables, timing, and risk.

Common Situations Where A Consultancy Agreement Makes Sense

• Project-based work: e.g. rebranding, website build, systems implementation, market research, or a one-off strategy piece.
• Specialist advice: e.g. HR consulting, finance consulting, legal operations support, or business coaching.
• Ongoing support: e.g. fractional CFO, retained marketing consultant, or IT support consultant.
• Short-term capacity boost: where you need help now, but you’re not ready to hire an employee.

Even if you trust the person (especially if you trust the person), having the agreement in place helps protect the relationship by making expectations clear from day one.

Consultancy Agreement Vs Employment Agreement: Why The Difference Matters

A consultant is usually engaged as an independent contractor. That means they run their own business (even if it’s just them), invoice you for services, and manage their own tax and costs.

An employee, on the other hand, is part of your business workforce and has rights and protections under employment law.

This difference matters because contractor relationships are typically governed by contract law, while employment relationships must comply with employment legislation like the Employment Relations Act 2000 and the Holidays Act 2003.

If you’re hiring someone to work regular hours under your direction, using your systems, and acting like part of the team, they may look more like an employee than a contractor (even if you call them a “consultant”). That’s where things can get risky.

If what you really need is a staff member, it’s usually safer to use an Employment Contract rather than trying to fit the relationship into a contractor model.

How Does A Consultancy Agreement Actually Protect You?

A consultancy agreement isn’t just paperwork for the sake of it. It’s a practical risk management tool that protects both sides and helps keep projects on track.

It Sets Clear Scope (So “Scope Creep” Doesn’t Become A Dispute)

One of the most common issues we see is scope creep. The consultant starts with one deliverable, then over time you ask for “just one more thing”, and suddenly there’s tension about timelines and payment.

A well-drafted consultancy agreement clearly defines:

• deliverables and milestones
• what’s included vs excluded
• revision rounds (if relevant)
• dependencies (e.g. you providing access, brand assets, stakeholder availability)
• how variations are requested and priced

For many businesses, it also makes sense to attach a short “Statement of Work” (SOW) that can be updated per project without rewriting the whole agreement.

It Reduces Payment Problems

Payment disputes often arise when expectations weren’t properly documented. A consultancy agreement can spell out:

• fixed fee vs hourly vs retainer pricing
• invoice schedule and payment terms
• late payment consequences (if any)
• expenses and whether they’re reimbursable
• GST treatment

This is especially helpful if your consultant is starting work before you’ve finalised internal budgets or approvals. It keeps everyone aligned.

It Protects Your Confidential Information

Consultants often get access to sensitive information: client lists, pricing, supplier terms, financials, internal processes, and product plans.

Your agreement should include confidentiality obligations and practical rules around:

• what information is confidential
• how it must be stored and handled
• when it can be shared (e.g. subcontractors with approval)
• what happens when the project ends (returning or deleting info)

In some cases, you might also want a separate Non-Disclosure Agreement if you’re sharing sensitive info before you’ve decided to proceed with the engagement.

It Clarifies Who Owns The Work Product (IP)

This is a big one.

Many business owners assume: “If I pay for it, I own it.” In practice, ownership depends on what your contract says.

Your consultancy agreement should clearly address:

• who owns deliverables as they’re created
• whether ownership transfers only after full payment
• what “background IP” the consultant is bringing in (templates, code libraries, frameworks)
• whether you’re getting an assignment of IP or a licence to use it

If you’re engaging a consultant to create valuable assets (like software, brand materials, training content, or product designs), you’ll want to get the IP position right upfront so you can scale without legal uncertainty later.

What Should Be Included In A Consultancy Agreement In NZ?

There isn’t a single “perfect” consultancy agreement, because it should match your business model and the type of consulting you’re engaging.

That said, there are core clauses that most New Zealand businesses should consider including.

1. Parties And Relationship (Independent Contractor)

The agreement should clearly identify who the parties are, and confirm the consultant is engaged as an independent contractor (not an employee, agent, partner, or joint venturer).

This clause should also align with how the relationship works in reality. If the day-to-day setup looks like employment, a contract label alone won’t fix that risk.

2. Scope Of Services And Deliverables

This section should describe the services and deliverables in plain language, and it should be detailed enough that both sides can tell whether the consultant has performed their obligations.

Depending on the work, you might include:

• a project timeline (or target dates)
• deliverable formats (e.g. documents, presentations, code repositories)
• acceptance criteria (how you confirm completion)
• meetings, reporting, and communication expectations

3. Fees, Invoicing, And Expenses

Spell out fees clearly. If you’re paying hourly, include:

• hourly rates
• time recording requirements
• approval requirements for work beyond a certain number of hours

If it’s a fixed fee, include what happens if the scope changes (so the consultant isn’t stuck doing double the work for the same price, and you don’t get surprise invoices).

4. Confidentiality And Privacy

Confidentiality is about protecting business information. Privacy is about complying with obligations when personal information is involved.

If the consultant will handle personal information (like customer records, mailing lists, health information, or employee information), your agreement should align with the Privacy Act 2020 and make it clear what the consultant can and can’t do with that data.

Many businesses also like to make sure their external-facing documents (like their Privacy Policy) align with how contractors actually handle data behind the scenes.

5. Intellectual Property (IP) Ownership And Licensing

Your agreement should clarify:

• ownership of deliverables created during the engagement
• how and when IP transfers (if it transfers)
• your rights to use, modify, and reproduce deliverables
• the consultant’s right (or lack of right) to reuse work for other clients

If your business relies heavily on IP (like a tech startup or a creative brand), this clause is often one of the most important parts of the agreement.

6. Warranties, Liability, And Indemnities

This part is about risk allocation: if something goes wrong, who wears the cost?

Common issues include:

• a consultant delivering work that infringes someone else’s IP
• incorrect advice leading to financial loss
• data breaches or mishandling of sensitive information
• third-party claims arising from the consultant’s work

It’s also common to include a limitation of liability clause, but it needs to be carefully drafted so it makes sense for your industry and doesn’t create unintended gaps in protection.

7. Term, Termination, And Handover

Even when a consulting relationship is going well, you still want a clean exit plan.

Your consultancy agreement should cover:

• the term (fixed period or ongoing)
• termination for convenience (e.g. 14 days’ notice)
• termination for breach (and any cure period)
• what happens to work in progress
• handover obligations and returning company property

If the consultant is embedded in key systems (like your CRM, website, or finance platforms), handover planning is essential to avoid being “locked out” of your own operations.

8. Restraints And Non-Solicitation (Where Appropriate)

Sometimes you’ll want to prevent a consultant from:

• poaching your staff or contractors
• soliciting your clients
• using your confidential strategies to compete directly with you

Restraints need to be reasonable to be enforceable, and they should be tailored to the genuine risks in your business (not just inserted because it “sounds standard”).

Common Mistakes Businesses Make With Consultancy Agreements

Most consultancy disputes don’t happen because someone is acting in bad faith. They usually happen because the agreement is unclear or doesn’t match what’s happening day-to-day.

Here are a few common pitfalls to watch out for.

Using A Generic Template That Doesn’t Match The Project

Templates can look appealing, but consulting arrangements vary a lot. A one-size-fits-all contract can leave key issues uncovered, like who owns work product, what happens if timelines change, or how you manage subcontractors.

When your agreement is tailored, it’s much more likely to protect you in real-world scenarios.

Not Being Clear About IP Ownership

If you’re paying a consultant to build something your business will rely on, you don’t want to discover later that you only have a limited licence (or no rights to modify or commercialise what you’ve paid for).

IP should be addressed clearly, not vaguely.

Accidentally Treating A Consultant Like An Employee

If you require set working hours, control the way they perform their work, and integrate them like staff, you could create legal risk around misclassification.

This is one reason it’s important to assess whether you need a consultant or an employee from the start. If you’re unsure, it’s worth getting advice early rather than trying to fix it later.

Forgetting About Privacy And Data Security

In 2026, many consultancy engagements involve cloud platforms, remote work, shared drives, and access to customer or employee information.

If a consultant is handling personal information, you should have clear rules about security standards, access controls, and what happens if there’s a suspected data breach.

Not Documenting Variations

If the project changes (and it often does), variations should be documented. Otherwise, both sides are relying on memory, which is a fast path to disagreement.

A simple written variation process can prevent a lot of stress.

How To Set Up A Consultancy Agreement That Actually Works (Practical Steps)

A good consultancy agreement isn’t just legally sound. It’s also practical and easy to use.

Here’s a straightforward way to approach it.

1. Get Clear On The Outcome You Want

Before drafting or signing anything, define your objective. Ask yourself:

• What does success look like at the end of the engagement?
• What deliverables do we need to get there?
• What information or systems will the consultant need access to?

This becomes the backbone of your scope and deliverables clause.

2. Decide How You Want To Pay (And Why)

Different fee structures suit different work:

• Fixed fee: great for defined deliverables, but needs a variation process.
• Hourly: flexible, but needs controls and reporting so you don’t blow the budget.
• Retainer: useful for ongoing support, but clarify inclusions and unused hours.

The key is aligning payment structure with risk. If your scope is uncertain, a fixed fee can create frustration. If deliverables are very clear, hourly billing might feel inefficient.

3. Put The Right Legal Document In Place

For most consulting engagements, a tailored Consulting Agreement is a solid starting point.

If the consultant will be building software, you may need something more specific like an Software Development Agreement so milestones, IP, testing, deployment, and handover are properly covered.

If you’re working with multiple related documents (like a master agreement plus SOWs), make sure they’re consistent and don’t contradict each other.

4. Think About Your “Worst Day” Scenarios

This sounds negative, but it’s actually empowering.

Ask:

• What if the consultant stops responding mid-project?
• What if the work is late or not usable?
• What if they’ve had access to client data?
• What if we need to switch providers quickly?

A good consultancy agreement answers these questions in advance, so you’re not scrambling when pressure is high.

5. Keep Your Agreement Consistent With Your Broader Business Contracts

If you have other agreements in place (like customer terms, supplier terms, or partnership arrangements), consistency matters.

For example, if the consultant is dealing directly with your clients, you may want to ensure your customer-facing agreements set expectations too, such as a Service Agreement that clarifies deliverables, timelines, and liability boundaries.

Key Takeaways

• A consultancy agreement is a contract that sets clear expectations for an independent contractor relationship, including scope, fees, IP, confidentiality, and termination.
• It helps prevent common disputes by clearly documenting deliverables, timelines, variations, and what happens if the engagement ends early.
• IP ownership should be dealt with explicitly, especially where the consultant is creating valuable assets like software, content, designs, or strategies.
• If the relationship looks and feels like employment in practice, using a consultancy agreement can create legal risk, so it’s important to structure it correctly from the start.
• Privacy and data security obligations matter when consultants handle personal information, and your contract should set practical rules for access, storage, and breach response.
• Generic templates often miss key protections, so it’s worth having your consultancy agreement tailored to your business and the specific engagement.

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