Consulting Services Agreements in NZ

A consulting services agreement can look deceptively simple. A founder wants specialist help, a consultant wants to start quickly, and both sides assume a few emails and a proposal will do the job. That is usually where problems start. Common mistakes include leaving the scope vague, forgetting to deal with intellectual property, and relying on payment terms that do not say when fees are due or what happens if the project changes.

If you are hiring a consultant or providing consulting services in New Zealand, the contract should do more than record a price. It should set expectations, reduce disputes, and protect your business if the relationship does not go to plan. The guide below covers what a consulting services agreement should include, the legal issues to check before you sign, and the drafting traps that catch New Zealand businesses most often.

Overview

A well-drafted consulting services agreement sets out who is doing what, when they will do it, what they will be paid, and who owns the work created. It also helps both sides deal with confidentiality, delays, disputes, and early termination without relying on assumptions or verbal promises.

Define the services and deliverables clearly
Set fees, invoicing dates, expenses, and overdue payment terms
State whether the consultant is an independent contractor, not an employee
Deal with ownership and use of intellectual property
Include confidentiality and privacy obligations where business information or personal information is involved
Set timelines, milestones, approvals, and responsibilities for both parties
Explain what happens if the scope changes
Include warranties, liability caps, and exclusions that fit the project
Set out termination rights, notice periods, and post-termination obligations
Make sure the agreement is consistent with New Zealand law and the way the work will actually be done

What Consulting Services Agreement Means For New Zealand Businesses

A consulting services agreement is the main contract that governs a business-to-business consulting relationship. In plain English, it says what advice or services will be provided, what the client will pay, and what each side can expect if something goes wrong.

For New Zealand businesses, this matters because many consulting arrangements start informally. A director might ask a marketing consultant to prepare a campaign strategy, a software adviser might be brought in for a short project, or an operations consultant might be engaged to fix a process issue. If the arrangement grows beyond a quick task, a short proposal alone is often not enough.

What the agreement usually covers

The exact drafting depends on the project, but most consulting contracts should include core commercial terms and risk protections. At a minimum, the parties should be able to read the agreement and answer the following questions.

What services is the consultant actually providing?
What deliverables must be produced, and by when?
Is the work fixed-fee, hourly, milestone-based, or ongoing?
Who approves stages of work, and how quickly?
Can the scope be changed, and how are extra fees handled?
Who owns reports, code, designs, templates, or other work product?
Can the consultant reuse pre-existing tools, methods, or know-how?
What information must be kept confidential?
What level of liability is accepted by each side?
How can the agreement be ended?

Why informal arrangements cause real business risk

The main risk is mismatch between what was sold and what was expected. A client may think it is buying a finished outcome, while the consultant thinks it is only providing advice. A founder may assume ownership of everything produced, while the consultant assumes it keeps ownership of background materials and licences limited use.

This is where founders often get caught before they sign a contract. They focus on the price and timing, but not on use rights, confidentiality, reliance, or the practical details that decide whether a project can continue smoothly.

Independent contractor status matters

A consulting services agreement should usually say that the consultant is engaged as an independent contractor, not as an employee. That clause helps record the commercial intention, but the label alone is not conclusive. The real relationship still matters.

If the arrangement looks like employment in practice, there can be risk around employment rights and obligations. That is especially relevant where an individual consultant works only for one business, follows strict direction, and is integrated into day-to-day operations. The agreement should reflect the actual working model rather than trying to force a label onto it.

New Zealand consumer and fair trading issues can still matter

Even in a business-to-business context, New Zealand legal rules around misleading conduct and service quality can still be relevant. If a consultant makes promises about outcomes, expertise, timing, or savings, those statements should be accurate and not overstated. Marketing claims and sales pitches can become part of the factual background to a dispute later.

Where services are supplied, there may also be statutory obligations that cannot simply be wished away with broad boilerplate. The contract should be drafted with the actual relationship, bargaining position, and service type in mind.

Legal Issues To Check Before You Sign

Before you sign a consulting services agreement, the most useful question is whether the document matches how the project will work in real life. If the answer is no, the contract needs work, even if the commercial deal feels settled.

Scope of services and deliverables

The scope is usually the first place disputes begin. If the contract says the consultant will provide strategic advice, that may be too vague to measure. If it says the consultant will produce a detailed market entry report, workshop materials, and three revision rounds by set dates, both sides have something concrete to work against.

The scope should cover:

the exact services being provided
specific deliverables and formats
project stages or milestones
client dependencies, such as providing data, access, or feedback
what is excluded from the price

If the work may evolve, include a variation process. That should explain who can request changes, how they are approved, and when extra fees apply.

Fees, invoicing, and expenses

Payment terms should be precise, not implied. A good clause explains whether fees are fixed, hourly, daily, retainer-based, or tied to milestones. It should also state when invoices can be issued and when payment is due.

Check that the agreement deals with:

deposit requirements, if any
payment dates and invoice timing
whether fees are quoted inclusive or exclusive of GST
approval and reimbursement of expenses
late payment consequences, such as interest or suspension rights
what happens to fees if the project is paused or terminated early

If the fee model is based on time spent, think carefully about timesheets, caps, and approval requirements. If the project is fixed-fee, be clear about assumptions so the consultant is not expected to absorb endless extra work.

Intellectual property ownership

Intellectual property is one of the most negotiated parts of a consulting services agreement. The right answer depends on what is being created and how the client wants to use it after the project ends.

Some clients expect to own all deliverables on payment. Consultants often want to keep ownership of pre-existing materials, methodologies, templates, and know-how, while giving the client a right to use the final work product.

The agreement should separate:

background intellectual property, which existed before the engagement
project-specific deliverables created for the client
third-party materials or software used in the work
licences the client needs to use the outputs after completion

If the consultant is preparing software, content, branding, reports, training material, or technical documentation, do not rely on assumptions. Spell out who owns what and when ownership transfers, if it does.

Confidentiality and privacy

If the consultant will see business plans, pricing, customer lists, product ideas, financial data, or other sensitive information, the agreement should include a clear confidentiality clause. That clause should say what information is confidential, how it can be used, who can access it, and what happens when the project ends.

Privacy obligations become especially important if personal information is involved. If the consultant will handle customer data, employee information, or user records, the parties should consider what responsibilities sit under the Privacy Act 2020. The contract should address data access, security expectations, permitted uses, and return or deletion requirements in a privacy notice or related data protection terms.

Warranties, liability, and reliance

A consulting agreement should not promise perfect outcomes unless that is genuinely intended. Advice-based projects often involve judgement, assumptions, and client-supplied information. The contract should reflect that reality.

Common points to review include:

whether the consultant warrants that services will be performed with reasonable care and skill
whether the consultant is responsible for outcomes outside its control
whether indirect or consequential losses are excluded
whether liability is capped, and if so, at what amount
whether the client is prevented from relying on informal statements not written into the agreement

Liability clauses need to be drafted carefully. A clause that is too aggressive may be challenged commercially or create distrust before the project even starts. A clause that is too loose may leave the consultant exposed far beyond the fee earned.

Term, termination, and exit rights

Every consulting relationship should have a clean exit process. Projects change, budgets get cut, and relationships can break down even when everyone started in good faith.

The agreement should say:

when the contract starts and ends
whether it is for a fixed term or ongoing until notice is given
when either side can terminate for convenience
what counts as serious breach allowing immediate termination
what fees remain payable on termination
what must be returned, deleted, or handed over after termination

This is particularly important before you accept the provider's standard terms. Some standard forms make termination easy for one side and expensive for the other.

Dispute process and governing law

A dispute clause does not stop disagreements, but it can make them easier to manage. For New Zealand businesses, the agreement should generally identify New Zealand law as the governing law unless there is a genuine commercial reason otherwise.

It can also help to include a simple escalation process, such as good faith discussions between nominated representatives before formal steps are taken. That gives both sides room to solve delivery issues without immediately escalating the situation.

Common Mistakes With Consulting Services Agreement

Most contract problems do not come from obscure legal points. They come from everyday shortcuts taken when everyone is in a hurry. A consulting services agreement often fails because the parties assume the relationship is straightforward.

Using a vague statement of work

Founders often rely on general language because they want flexibility. The problem is that flexibility for one side can mean uncertainty for the other. If the deliverables are not measurable, there is no clear way to decide whether the work has been completed properly.

A better approach is to describe outputs, timing, review steps, and exclusions in plain English. That makes project management easier as well as legal enforcement.

Relying on a proposal and email chain only

A proposal can be useful, but it often focuses on the sales case rather than the legal deal. Important points such as ownership, confidentiality, liability, and termination are frequently missing or inconsistent across documents.

Before you rely on a verbal promise or scattered emails, check whether the agreement says the full contract is contained in the signed document and any attached schedule. If key promises matter, they should be written into the agreement itself.

Ignoring intellectual property until the end

This is a classic issue for design, tech, brand, training, and strategy projects. The client assumes it owns the output because it paid for the work. The consultant assumes it can reuse parts of the work because those parts reflect its methods or pre-existing material.

If that issue is not settled early, it can derail handover, future use, or investment due diligence. Buyers and investors often want clear evidence that the business owns or validly licenses the material it relies on.

Accepting one-sided liability terms

Consultants sometimes sign contracts that make them responsible for nearly any loss connected to the project, even where the client controls the final decision. Clients also make mistakes by accepting heavily limited terms that give almost no recourse if the consultant fails to deliver.

The right balance depends on the size of the job, the fee level, the nature of the advice, and the commercial risk. Blanket positions rarely work well.

Not matching the contract to the real relationship

A contract might say the consultant has full control over how the services are delivered, but in practice the consultant is managed like a staff member and required to work fixed hours on-site. That mismatch can create legal and operational problems.

The same issue arises where the contract says the consultant only provides advice, but the client expects implementation, staff training, and ongoing support. The document should reflect the actual arrangement, not an idealised version.

Leaving privacy and data handling too loose

Businesses often think a standard confidentiality clause is enough. It may not be. If the consultant accesses customer or employee information, the agreement should go further and cover data security, permitted use, subcontracting, incident notification, and return or deletion.

That matters even more where the consultant uses cloud tools, offshore systems, or third-party platforms to carry out the work.

Forgetting practical sign-off steps

Even where the legal drafting is sound, projects can stall because the contract does not explain who approves work and when. If there is no sign-off process, a client can delay acceptance while still expecting the project to stay on track.

It helps to include:

named contacts for instructions and approvals
timeframes for feedback
rules for deemed acceptance if no feedback is given in time
milestone completion criteria
what happens if the client causes delay

FAQs

What should be included in a consulting services agreement in New Zealand?

A consulting services agreement should cover the scope of services, deliverables, fees, payment timing, contractor status, intellectual property, confidentiality, privacy, liability, termination rights, and dispute process. The detail should match the actual project, not just a generic template.

Is a consultant the same as an employee?

Not necessarily. A consultant is usually engaged as an independent contractor, but the true legal position depends on how the relationship works in practice. If the consultant is treated like part of the business on an ongoing basis, the label in the contract may not be enough on its own.

Who owns the work created by a consultant?

It depends on what the agreement says. Some contracts assign ownership of project deliverables to the client once fees are paid. Others let the consultant keep ownership and give the client a licence to use the work. Background materials and pre-existing know-how should be addressed separately.

Can a consulting services agreement limit liability?

Yes, many consulting contracts include liability caps and exclusions, but the clause needs to be drafted carefully and fit the commercial context. The parties should be clear about what losses are covered, what is excluded, and whether any obligations remain uncapped.

Do I need a written contract for a short consulting project?

A written contract is strongly recommended, even for a short project. Short engagements still raise issues about payment, scope changes, ownership of work, confidentiality, and early termination. A simple but tailored written agreement is usually far safer than relying on informal messages.

Key Takeaways

A consulting services agreement should clearly define the services, deliverables, pricing, and project timing.
Do not leave intellectual property, confidentiality, privacy, and liability terms to assumption or later discussion.
The contract should match the real working relationship, especially where contractor and employee issues could arise.
Variation, approval, termination, and handover clauses are often what save a project when things change.
Before you sign, make sure the agreement reflects New Zealand law and the specific risks of the work being done.

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

Consulting Services Agreements in New Zealand: What to Include