How to Draft a Consulting Contract That Protects Your Business

A consulting arrangement can look simple at the start. You need specialist help, the consultant wants to get moving, and both sides are keen to keep the paperwork light. That is usually where the trouble starts. New Zealand businesses often rely on a short proposal, a few emails, or the consultant’s standard terms, then discover later that no one agreed on scope, ownership of work, payment timing, or what happens if the project goes off track.

Three common mistakes come up again and again: using vague deliverables, assuming intellectual property automatically belongs to the client, and leaving termination rights until there is already a dispute. Another frequent problem is accepting broad promises about results without tying them to measurable obligations.

A well-drafted consulting contract should do more than confirm the fee. It should set out what is being delivered, when it is due, who carries the risk if things change, and how confidential information and business assets are protected. This guide explains what New Zealand businesses should include before you sign, the legal issues to check, and the mistakes that can leave your business exposed.

Overview

A consulting contract protects your business when it clearly allocates work, payment, ownership, confidentiality, risk, and exit rights. If those points are left vague, even a capable consultant relationship can become expensive and distracting.

• Define the services, deliverables, milestones, and any assumptions in practical detail.
• Set payment terms, invoicing timing, expenses, and what happens if the scope changes.
• State who owns intellectual property, including draft work, final work product, and pre-existing materials.
• Include confidentiality and privacy obligations where business or customer information is involved.
• Deal with liability caps, exclusions, indemnities, and responsibility for third party claims.
• Set clear termination rights, notice periods, handover obligations, and consequences of early exit.
• Check whether the consultant is genuinely independent and not being treated like an employee or contractor in practice.
• Make sure marketing claims, service promises, and written terms line up so there are no conflicting expectations.

What To Know Before You Start

For a New Zealand business, a consulting contract is the document that turns commercial expectations into enforceable terms before you rely on a verbal promise. The main job of the contract is to remove uncertainty while the relationship is still positive.

Founders often engage consultants for strategy, marketing, technology, operations, finance support, design, procurement, or short-term project management.

In each case, the legal risk is similar: the consultant may think they are supplying advice only, while the business expects a finished result that can be used immediately.

A strong contract closes that gap. It records the exact services being supplied, the level of care expected, and the limits of what the consultant is taking responsibility for.

Scope needs to be specific, not aspirational

The first protection is a precise scope. “Business advisory services” or “marketing support” is rarely enough on its own. A better clause spells out the deliverables, deadlines, approvals needed from your side, and anything excluded from the engagement.

Before you sign, make sure the contract answers practical questions such as:

• What will the consultant actually deliver?
• Are there milestones or stages?
• Who is the key contact on each side?
• What information or access must your business provide?
• What is outside scope and charged separately?
• What assumptions does the consultant rely on?

This is where founders often get caught. A consultant may quote for an initial piece of work, then treat revisions, implementation support, training, or attendance at meetings as extra services. If your business expects those items to be included, the contract should say so.

Payment terms should match the way the work is delivered

Your payment clause should reflect the commercial reality of the project. Fixed-fee, hourly, retainer, and milestone-based arrangements each create different risks.

For example, an hourly contract can become open-ended if there is no estimate, approval process, or spend cap. A fixed-fee contract can also create conflict if the scope is poorly defined and the consultant claims the agreed fee only covers part of the job.

Useful payment terms usually cover:

• the fee structure and any GST treatment
• when invoices can be issued
• how long your business has to pay
• whether expenses are included or need pre-approval
• what happens if milestones are delayed
• how variations are priced and approved
• whether any part of the fee is refundable if the project ends early

If the project may evolve, include a variation process in the written terms. That gives both sides a disciplined way to approve new work before more time is spent.

Intellectual property ownership should never be left to assumption

One of the most misunderstood parts of a consulting contract is intellectual property. New Zealand businesses often assume that if they paid for the work, they own it automatically. That is not always a safe assumption.

The contract should distinguish between:

• pre-existing intellectual property the consultant already owns
• materials your business provides to the consultant
• new work created specifically for your business
• third party tools, software, templates, or data sets used in the project

Sometimes full ownership is appropriate. In other cases, the consultant keeps ownership of background tools and grants your business a licence to use them, while your business owns the project-specific output. The right approach depends on the work involved, but the contract should be explicit.

If branding, written content, software, training materials, reports, or design assets are being created, the ownership clause matters even more. Without clarity, your business may pay for work but still face limits on reuse, modification, or commercial rollout.

Confidential information and privacy need separate attention

If a consultant will see sensitive commercial information, your contract should protect it. A basic confidentiality clause should define what confidential information is, what the consultant can use it for, and when disclosure is allowed.

If the consultant will handle personal information, the arrangement may also need to reflect obligations under the Privacy Act 2020. The contract should say what data the consultant can access, how it must be stored, who can use it, and what happens if there is a privacy incident. In some cases, a privacy notice or internal privacy policy may also need updating.

This matters particularly for consultants working with customer databases, HR records, user analytics, health-related information, payment details, or internal business systems.

Legal Issues To Check Before You Sign

Before you sign a consulting contract, the key legal question is not whether the document looks professional. It is whether it allocates risk in a way your business can actually live with if the project fails, drags on, or causes loss.

Independent contractor versus employee risk

Calling someone a consultant does not automatically make them an independent contractor. If the practical relationship looks more like employment, there can be wider legal consequences.

You should look at factors such as:

• how much control your business has over the consultant’s hours and methods
• whether they work mainly for your business
• whether they can subcontract or send a replacement
• whether they supply their own tools and systems
• whether they are paid per result or more like a salary
• how integrated they are into your team and operations

The contract should support the real nature of the relationship. If you need an employee, an employment agreement is usually the safer path. If you genuinely want an external specialist, the consulting contract should reinforce that independence.

Liability caps and exclusions

Every consulting contract should deal with liability directly. If it does not, your business may be left arguing over general legal principles after something has gone wrong, which is not a good place to be.

A consultant may ask for broad exclusions of indirect or consequential loss and a low cap on total liability. Those requests are common, but they should be reviewed against the value and risk of the project. If the consultant is handling sensitive data, making high-stakes recommendations, or producing work your business will rely on heavily, a very low cap may be unreasonable.

Points to assess include:

• whether the cap is tied to fees paid, fees payable, or a higher agreed amount
• whether confidentiality breaches and privacy breaches are carved out
• whether intellectual property infringement claims are treated differently
• whether fraud, wilful misconduct, or deliberate breach should be excluded from the cap
• whether the consultant should maintain insurance obligations

The right balance depends on the engagement, but the main risk is accepting a cap that leaves your business carrying most of the practical downside.

Warranties, service standards, and reliance

Your contract should make clear what the consultant is promising. Some consultants only agree to use reasonable care and skill. Others may commit to specific service levels, deadlines, or outcomes.

If your business is relying on specialist expertise, the contract should record that clearly. It should also say whether you are relying on the consultant’s recommendations for implementation decisions, and whether any assumptions need to be verified independently.

Marketing-style claims made during the sales process can create problems if they are not reflected in the written contract. Under the Fair Trading Act 1986, businesses should be careful about misleading statements or exaggerated claims in trade. If a consultant has made strong claims about results, make sure the final contract either confirms those promises accurately or qualifies them properly.

Termination, suspension, and handover

The contract should tell you how to get out cleanly if the project stops working. Waiting until there is a dispute usually means the exit terms favour whoever drafted the document first.

Good termination clauses usually cover:

• termination for convenience on notice
• termination for breach if the problem is not fixed within a stated period
• immediate termination for insolvency, serious misconduct, or confidentiality breaches
• what fees are payable up to termination
• whether work in progress must be handed over
• return or deletion of confidential information
• ongoing clauses that survive termination, such as confidentiality and intellectual property terms

Handover obligations are especially important for software, marketing campaigns, strategic plans, research files, account access, and supplier communications. If the relationship ends suddenly, your business still needs a practical way to continue operating.

Disputes, governing law, and practical enforcement

A dispute clause will not stop conflict, but it can make conflict easier to manage. For New Zealand businesses, governing law and jurisdiction should usually align with New Zealand where possible, especially if the consultant is overseas.

The contract can also require senior representatives to meet before formal proceedings begin. That will not solve every problem, but it often helps avoid an immediate escalation over invoices or scope.

Common Mistakes With How to Draft a Consulting Contract That Protects Your Business

The most common mistake is treating a consulting contract like a formality after the deal is already done. Once work starts, your leverage to negotiate clear protections usually drops.

Relying on a proposal instead of a contract

A proposal can be useful commercially, but it often reads like sales material rather than a legal agreement. It may describe the project attractively without dealing with ownership, liability, termination, confidentiality, or dispute handling.

If you are using a proposal as part of the contract set, make sure there is a clear order of precedence. Otherwise a polished proposal and a separate set of terms can say different things about scope, timing, or outcomes.

Leaving deliverables too vague

Vague deliverables create avoidable conflict. “Provide advice”, “support implementation”, or “assist with strategy” can mean very different things to each side.

Use objective descriptions where possible, such as:

• named reports, plans, or templates
• a stated number of workshops or meetings
• draft and final versions
• acceptance criteria for technical work
• specific dates or milestone windows

When deliverables are measurable, payment disputes and performance disputes are easier to manage.

Ignoring ownership of background materials

Some projects combine your business material, the consultant’s existing frameworks, and newly created work. If the contract only says “all IP belongs to the client”, that can still leave arguments about what counts as pre-existing material.

The safer approach is to define background intellectual property and project intellectual property separately. That makes it easier to understand what each side can keep using after the engagement ends.

Accepting one-sided limitation clauses

Consultants often issue standard terms that heavily protect their side. That is not unusual, but it should not be accepted without review. A very broad exclusion clause can wipe out practical remedies even where your business suffers real loss.

Pay close attention before you accept the provider’s standard terms if they include:

• no liability for data loss
• no liability for delays caused by subcontractors
• no warranties about accuracy
• very short timeframes to raise claims
• automatic renewals
• wide rights to suspend work while retaining fees

These points are not always inappropriate, but they should be conscious commercial decisions rather than hidden defaults.

Forgetting privacy and information security obligations

Businesses often think of privacy only when dealing with customers directly. In reality, consultants may create privacy risk if they access your systems, internal files, mailing lists, or support channels.

If personal information is involved, the contract should deal with access controls, permitted use, subcontracting, storage practices, and notification if something goes wrong. A short confidentiality clause alone may not be enough.

Not planning for change

Consulting projects often shift once the work begins. New stakeholders appear, priorities change, and the original scope no longer fits. If your contract has no variation process, every change becomes a mini argument.

Include a simple written change process that covers the extra work, revised timing, and any fee impact. This avoids the classic problem where everyone informally agrees to a broader project, then disputes the final invoice.

Missing restraint and conflict provisions where they matter

Not every consulting contract needs non-solicitation, exclusivity, or conflict management clauses. But some do. If the consultant will be close to your customers, staff, pricing, product roadmap, or acquisition strategy, those issues should be considered before you sign.

Any restraint-style clause should be carefully drafted and reasonable in scope. Terms that are too broad may be difficult to enforce, while terms that are too narrow may not give meaningful protection.

FAQs

Does a consulting contract need to be in writing in New Zealand?

A written contract is not always legally required, but it is strongly recommended. A written agreement gives your business clearer evidence of scope, fees, ownership, and termination rights if there is a disagreement later.

Who owns work created by a consultant?

Ownership depends on the contract and the type of work involved. Do not assume your business owns everything just because you paid for it. The agreement should state who owns new work and what happens to the consultant’s pre-existing materials.

Can I use the consultant’s standard terms?

Yes, but review them carefully before you sign. Standard terms are usually written to favour the party supplying them, especially on liability, payment timing, and intellectual property.

What if the consultant will access customer or employee data?

Your contract should include privacy and information handling terms. If personal information is involved, the arrangement should reflect your obligations under the Privacy Act 2020 and set clear rules for access, storage, and incident reporting.

Can I end the contract early if the project is not working?

That depends on the termination clause. A good contract should let your business terminate for breach, and in many cases for convenience on notice, while also dealing with fees, handover, and return of information.

Key Takeaways

• A consulting contract should clearly define services, deliverables, deadlines, assumptions, and what is out of scope.
• Payment terms should deal with invoicing, expenses, milestones, variations, and what happens if the project changes.
• Intellectual property should be addressed expressly, especially where the consultant uses pre-existing tools or creates valuable work product for your business.
• Confidentiality and privacy clauses matter if the consultant will access sensitive business information or personal information.
• Liability caps, exclusions, warranties, and insurance requirements should match the real risk of the engagement.
• Termination and handover terms are essential so your business can exit cleanly and keep operating if the relationship ends.
• Do not rely on verbal promises, proposals alone, or unreviewed standard terms before you sign a contract.

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