How to Draft a Consultancy Contract

If you are hiring a consultant for strategy, marketing, operations, IT, finance or another specialist project, a vague agreement can become expensive very quickly. New Zealand businesses often make the same mistakes: they rely on a proposal instead of a signed contract, they leave the scope too broad, or they forget to deal with ownership of work product and confidentiality. Another common problem is calling someone a contractor while giving them working arrangements that look more like employment.

A well-drafted consultancy contract should do more than say what the consultant will do and how much you will pay. It should set clear boundaries, manage risk, and deal with what happens if the project changes, goes wrong, or ends early. This guide explains how to draft a consultancy contract for a New Zealand business, the clauses worth including, and the legal issues to check before you sign or accept the consultant's standard terms.

Overview

A consultancy agreement records the commercial deal and helps both sides avoid misunderstandings once work starts. For New Zealand businesses, the most useful contract is usually one that is practical, specific, and tailored to the actual project rather than copied from a generic online template.

The main aim is to make the consultant's role, limits, payment terms and legal responsibilities clear before any work begins.

• Define the services, deliverables and timing with enough detail to avoid scope disputes
• State whether the consultant is an independent contractor, and make the working arrangement match that label
• Set payment terms, expenses, late payment rules and any milestone or retainer structure
• Deal with intellectual property ownership, licences and use of pre-existing materials
• Include confidentiality, privacy and data protection obligations where business information is shared
• Address liability limits, indemnities, warranties and what happens if advice is wrong or delayed
• Cover termination rights, notice periods, handover obligations and payment on exit
• Make sure marketing claims, service promises and conduct align with New Zealand law, including fair dealing obligations

What This Means For Your Business

Drafting a consultancy contract means translating a business conversation into a document that is clear enough to enforce and practical enough to use day to day. For most founders and SMEs, the real job is not writing legal jargon, it is deciding exactly what has been agreed and what risks need to be managed before you sign.

Consultants are often brought in when a business needs specialist knowledge without hiring a permanent employee. That may include a short diagnostic project, ongoing advisory services, implementation support, or a one-off strategic review. Each of those arrangements creates different risks, so the contract should reflect the actual engagement.

Why a consultancy contract matters

The contract becomes the reference point when expectations drift. If a consultant says a task is out of scope, if you expected ownership of reports or code, or if either side wants to end the relationship early, the written terms are what you turn to.

That matters most in founder moments such as:

• before you rely on a verbal promise made in a sales meeting
• before you accept the provider's standard terms without review
• before you share customer data, financial information or product plans
• before you spend money on setup or project delivery based on assumed timing
• before you treat a long-term consultant like part of your internal team

Key clauses every consultancy agreement should cover

A good consultant agreement usually includes the following core terms.

1. Parties and services

Start by naming the correct legal parties. If the consultant works through a company, the agreement should usually be with that company, not just the individual. If you are contracting through your own company, use the company name as recorded with the Companies Office.

The services clause should describe what the consultant will and will not do. Avoid general wording like “business consulting services as required”. That creates room for dispute. Set out the project, the deliverables, any assumptions, and who is responsible for inputs or approvals.

Useful detail may include:

• the objective of the engagement
• specific deliverables such as reports, plans, workshops or recommendations
• the number of hours, days or milestones included
• response times or service levels, if they matter
• dependencies on your team, systems or information
• anything expressly excluded from scope

2. Term and timing

Say when the agreement starts, whether it ends on a fixed date or continues until terminated, and any milestone dates. If timing matters commercially, be clear about whether dates are estimates or hard deadlines.

This is also where founders often get caught. If your business needs work completed before a funding round, launch date or internal planning cycle, the agreement should say so. If not, delay may be frustrating but harder to treat as a breach.

3. Fees, invoicing and expenses

Your payment clause should match the project. Some consultancy engagements suit fixed fees, some suit hourly or daily rates, and some suit staged payments tied to milestones.

Spell out:

• the fee model and rates
• when invoices can be issued
• payment due dates
• whether fees are exclusive or inclusive of GST
• what expenses can be charged and whether pre-approval is required
• what happens if the project pauses or scope changes

If there is a deposit, retainer or minimum commitment, say how it is applied and whether it is refundable.

4. Scope changes

Most consultancy disputes are really scope disputes. A short variation clause can save a lot of friction. It should say that changes to services, timing or fees must be agreed in writing, even if by email.

That helps if the project expands gradually through meetings and informal requests. Without a variation process, both sides may think the other has accepted something different.

5. Intellectual property

If the consultant creates reports, training materials, designs, software, templates or other work product, your contract should say who owns it. This is one of the most overlooked parts of how to draft a consultancy contract.

There are usually three moving parts:

• new material created specifically for the project
• the consultant's pre-existing tools, methods, templates or know-how
• your pre-existing materials, systems, branding and confidential information

You may want ownership of bespoke deliverables, while the consultant may want to keep ownership of their underlying methods and license them for your use. The contract should separate those categories clearly.

6. Confidentiality and privacy

If the consultant will see sensitive business information, a confidentiality clause is essential. It should cover what information is confidential, how it can be used, who it can be shared with, and what happens at the end of the project.

If the consultant handles personal information, the Privacy Act 2020 may also be relevant. The agreement should set expectations about data access, security, permitted use, storage, deletion and breach notification. This matters if the consultant can access customer records, employee data or contact databases, and may justify a separate privacy notice in some cases.

7. Independent contractor status

A consultancy contract should state that the consultant is an independent contractor, not an employee. But the label alone is not enough. New Zealand law looks at the real nature of the relationship.

If the consultant works only for you, follows fixed hours, uses your systems like staff, reports through your management chain and is treated like part of the workforce, there may be a risk the arrangement looks employment-like. That can create legal and financial issues well beyond the contract wording.

The agreement and the working arrangement should align on matters such as:

• control over how the work is performed
• ability to work for other clients
• use of the consultant's own equipment or methods
• responsibility for leave and benefits
• ability to subcontract, if appropriate

8. Warranties, liability and indemnities

Consultants often give advice that affects commercial decisions, so this section matters. A contract can set reasonable expectations about skill and care, compliance with law, and reliance on information supplied by the client.

Liability clauses may include limits on the consultant's exposure, exclusion of indirect loss, and time limits for bringing claims. Indemnities may also appear, but they need care. A broad indemnity can shift more risk than many businesses realise before they sign.

The right balance depends on the project. A small advisory engagement may justify a different risk position from a systems implementation or compliance review.

9. Termination and exit

The contract should say when either side can end the arrangement. Common triggers include notice for convenience, material breach, insolvency, non-payment, or prolonged delay.

It should also cover the practical consequences of termination, such as:

• what fees are payable up to the end date
• whether committed work in progress must be paid for
• handover of documents and materials
• return or deletion of confidential information
• ongoing IP, confidentiality and liability provisions

Legal Issues To Check Before You Sign

The main legal issues are scope certainty, contractor status, ownership of deliverables, information handling and risk allocation. If any of those are unclear before you sign, the contract may not protect your business when the relationship gets tested.

Is the consultant really a contractor?

If you are engaging one person on a long-term basis, pause and test whether the arrangement genuinely looks like a consultancy engagement. This is especially important where the person works regular days each week, appears on staff charts, or operates under close supervision.

A written contractor clause helps, but it does not automatically decide status. Make sure the commercial reality supports the contract wording.

Are promises outside the contract still floating around?

Sales calls, proposals and email threads often contain statements about timing, outcomes or inclusions that never make it into the final agreement. Before you sign, compare the contract against what was actually discussed.

Check for mismatches about:

• deliverables and deadlines
• who provides data, access or approvals
• whether the consultant guarantees any result
• training, support or revisions after delivery
• who owns the final materials

If a representation influenced your decision, consider whether it needs to be stated clearly in the contract. This also helps reduce issues under fair dealing rules if services have been marketed in a misleading way.

Does the contract deal with personal information properly?

If the consultant can access personal information, privacy should not be left to assumption. A simple confidentiality clause is often not enough if the consultant is handling customer, user or employee data.

Consider whether the agreement should include:

• limits on the personal information the consultant can access
• security standards or practical handling rules
• restrictions on overseas storage or subcontracting
• requirements to notify you of a privacy incident
• deletion or return obligations when the work ends

Who owns drafts, reports, code or templates?

Businesses often assume they own whatever they paid for. That is not always how a contract is written. If ownership matters to your business, say so expressly.

This is especially important where the consultant is producing material you will reuse internally, provide to customers, build into products, or rely on after the engagement has ended.

Are the liability clauses commercially sensible?

Many consultant templates cap liability at a very low amount, sometimes no more than the fees paid in a short period. That may be reasonable in some projects and unrealistic in others.

Look closely at:

• the cap amount and whether it reflects the project risk
• any exclusion of indirect or consequential loss
• whether there are carve-outs for confidentiality or IP breach
• any one-sided indemnity given by your business
• whether the consultant should hold relevant insurance

You do not need every agreement to be aggressive. You do need the risk allocation to make commercial sense.

Common Mistakes With How to Draft a Consultancy Contract

The most common mistakes are using generic wording, leaving key assumptions unstated, and signing a consultant's template without checking how it shifts risk. Most problems show up later as payment disputes, scope arguments or confusion about ownership and confidentiality.

Using a proposal as the whole agreement

A proposal may be useful commercially, but it often reads like marketing copy rather than a binding contract. It may not cover termination, liability, confidentiality or ownership.

If you want to incorporate a proposal, attach it to the agreement and make clear which document prevails if they conflict.

Describing the scope too broadly

“Advisory services as required” sounds flexible, but it creates uncertainty. Founders sometimes accept vague drafting because they want to move fast. The result is that no one can tell what is included without revisiting every conversation.

Write the scope so an outsider could understand what the consultant is supposed to deliver, by when, and with what assumptions.

Ignoring the consultant's pre-existing IP

Businesses often ask for ownership of all IP created under the agreement. Consultants often expect to keep their frameworks, know-how and reusable tools. If the contract does not separate bespoke output from background materials, the clause may create avoidable tension or not reflect the real deal.

Forgetting practical exit terms

Some contracts say either party can terminate on notice but do not explain what happens next. That leaves open questions about payment for partly completed work, access to files, handover meetings and use of draft deliverables.

Exit clauses work best when they deal with the practical end of the relationship, not just the legal trigger.

Missing privacy and security detail

If the consultant is handling data, a bare confidentiality promise is not much comfort. The contract should match the sensitivity of the information involved.

For example, an IT consultant with system access may need tighter security obligations than a facilitator running a one-off workshop.

Creating employment-style arrangements

This is where growing businesses can slip. A consultant may start as a short project resource and become embedded in the team over time. If you do not revisit the arrangement, the contract may stop matching reality.

Review longer engagements periodically, especially if the consultant works regular hours, takes direction like staff, or becomes operationally essential.

Accepting broad consultant disclaimers

Some consultant agreements say the advice is general only, that no outcome is promised, and that liability is heavily limited even where the consultant is plainly being hired for specialist expertise. Those clauses may or may not be acceptable, but they should be considered, not skimmed over.

Before you sign, ask whether the contract reflects the value of the service and the consequences if it goes wrong.

FAQs

What should be included in a consultancy contract in New Zealand?

A consultancy contract should usually cover the parties, services, timing, fees, expenses, IP ownership, confidentiality, privacy obligations where relevant, liability, contractor status, dispute process and termination terms. The right detail depends on the project and the risks involved.

Can I use a template consultancy agreement?

You can start from a template, but templates often miss project-specific issues such as scope detail, ownership of work product or privacy handling. Before you sign, make sure the wording matches the actual deal and the New Zealand business context.

Who owns the work a consultant creates for my business?

Ownership depends on the contract. Do not assume payment alone gives your business ownership of reports, designs, software or other deliverables. The agreement should state who owns new material and what happens to pre-existing tools or templates.

How do I reduce the risk of a consultant being treated like an employee?

Use a contract that clearly states independent contractor status, but also make sure the day-to-day arrangement supports that position. The more control, integration and exclusivity you impose, the greater the risk that the relationship looks employment-like.

Should a consultancy agreement include a confidentiality clause?

Yes, in most cases. If the consultant will access financial information, strategy, customer details, internal processes or product plans, confidentiality obligations should be clearly set out. If personal information is involved, privacy terms may also be needed.

Key Takeaways

• A consultancy contract should clearly define the services, deliverables, timing and assumptions so scope disputes are less likely.
• The agreement should deal with fees, expenses and changes to scope in a way that reflects how the project will actually run.
• IP ownership, confidentiality and privacy terms are essential where the consultant creates valuable work product or accesses sensitive information.
• The contract should describe an independent contractor arrangement, and your real working practices should match that description.
• Liability caps, warranties, indemnities and termination clauses should be reviewed carefully before you accept standard terms.
• Generic templates and proposals often leave gaps, especially around ownership, exit, data handling and commercial risk.

If you want help with contract review, scope clauses, intellectual property ownership, privacy terms, liability and termination provisions, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.