IP Assignment Clauses in New Zealand Consulting Agreements

If your business hires a consultant to build software, create designs, write training materials, develop a process, or produce strategy documents, ownership of that work is not something to leave vague. A lot of New Zealand businesses assume that paying for work means they automatically own the intellectual property, that a simple confidentiality clause is enough, or that email discussions will sort out ownership later. Those assumptions regularly create problems when a consultant reuses work for another client, asks for extra payment to transfer ownership, or keeps control over code, documents, templates, or know-how your business thought it had bought.

An IP assignment clause can decide who owns what, when ownership transfers, what rights each party keeps, and what happens to pre-existing materials. Before you sign a contract, it is worth being clear on the difference between ownership and a licence, how moral rights and future rights can affect the deal, and which contract drafting points matter most in a New Zealand consulting agreement.

Overview

An IP assignment clause in a consulting agreement is the section that transfers ownership of intellectual property from the consultant to the client, usually for work created under the contract. If the clause is vague, too narrow, or missing key mechanics, your business may end up with only limited use rights instead of full ownership.

For New Zealand businesses, the main issue is making sure the agreement matches the commercial reality of the project. A clause that works for a one-off logo design may not work for custom software, internal systems, data models, or consulting frameworks used across multiple clients.

• define exactly what intellectual property is being assigned, including drafts, source files, code, designs, documents, data outputs, and other deliverables
• separate newly created work from the consultant's pre-existing tools, templates, methods, and background IP
• state when the assignment takes effect, such as on creation, on payment, or on completion of milestones
• deal with future rights and any further assurance obligations, so the consultant must sign extra documents if needed later
• consider whether the client needs full ownership, an exclusive licence, or a narrower right to use the materials
• cover confidentiality, moral rights consents where relevant, and restrictions on reuse for other clients
• make sure subcontractors are also bound, especially if the consultant uses developers, designers, or specialist freelancers
• check that the agreement lines up with warranties, indemnities, termination rights, and payment terms

What IP Assignment Clause Consulting Firms Means For New Zealand Businesses

For most businesses, this clause decides whether the consultant's work becomes a business asset you control, or just something you can use on limited terms.

That matters most when the work is core to your operations or value, such as a website build, app code, automation workflow, brand assets, customer databases, technical drawings, internal manuals, product specs, or proprietary methodology developed for your business.

What an IP assignment clause actually does

An assignment transfers ownership of intellectual property rights from one party to another. In a consulting agreement, that usually means the consultant assigns rights in project deliverables to the client.

If drafted properly, the clause can cover copyright works, designs, inventions, confidential material captured in documents, and other rights arising from the consultant's work. The exact rights in play depend on the project and the type of material being created.

Payment does not always equal ownership

This is where founders often get caught. Paying an invoice does not automatically mean your business owns every part of what was produced.

In some projects, you may only receive an implied or express licence to use the work for a specific purpose. That can be enough for a limited engagement, but it may be a poor fit if you need to modify, commercialise, resell, or stop the consultant from reusing the same material elsewhere.

Assignment versus licence

An assignment and a licence are not the same thing. An assignment transfers ownership. A licence gives permission to use intellectual property on stated terms.

Sometimes a full assignment is the right commercial answer. Sometimes it is not. A consultant may reasonably want to retain ownership of general know-how, templates, libraries, or tools used across many client projects, while assigning the client-specific output.

A sensible agreement often splits the position into two parts:

• the client owns bespoke project deliverables created specifically for the engagement
• the consultant keeps ownership of background IP, but gives the client a licence to use it as needed with the deliverables

That distinction is especially common in software, marketing, product design, engineering, and business systems projects.

Why New Zealand consulting businesses should care

If you are the client, unclear ownership can affect future growth. It may interfere with investment due diligence, a business sale, platform changes, expansion into new markets, or a dispute with a contractor after the relationship ends.

If you are the consultant, an overreaching clause can strip you of your own methods, reusable frameworks, code snippets, and industry know-how. Accepting a client's standard terms without checking the IP wording can result in giving away more than you intended.

For both sides, the key question before you sign is simple: what exactly is being created for this project, and who should own each part of it?

Common project examples

The answer can look different depending on the engagement. For example:

• a brand consultant may assign the final logo, artwork, and campaign assets, while retaining ownership of general design processes and draft concepts not selected
• a software consultant may assign custom code written specifically for the client, while keeping ownership of pre-existing modules, libraries, and development tools
• a management consultant may assign final reports, workshop materials, and tailored implementation documents, while keeping underlying methodology and templates
• a product consultant may assign drawings and specifications created for the client's product, while keeping unrelated background know-how developed before the engagement

Without that level of specificity, both parties may think they have agreed to something different.

Legal Issues To Check Before You Sign

The safest approach is to match the IP clause to the actual work product, not rely on generic wording copied from another deal.

Before you accept the provider's standard terms, look closely at the drafting points below.

1. Define the deliverables and the IP clearly

If the agreement just says the consultant assigns "all IP", you may still end up arguing about what falls within that phrase. The contract should identify deliverables in practical terms.

Depending on the project, that may include:

• documents, reports, manuals, and slide decks
• source code, object code, scripts, integrations, and configuration files
• design files, artwork, videos, photographs, and brand assets
• technical plans, specifications, CAD files, and prototypes
• databases, data models, schemas, and dashboards
• training content, workflows, templates, and policies created specifically for the client

The more valuable the output, the less you should rely on broad catch-all language alone.

2. Separate project IP from background IP

This is one of the biggest negotiation points in consulting agreements. Background IP is the material a consultant already owned, developed independently, or uses generally across multiple clients.

If that is not carved out properly, the client may think it owns more than it reasonably should, or the consultant may later claim that key parts of the deliverables depend on pre-existing materials it still owns.

A better clause usually:

• defines background IP separately
• states the consultant retains ownership of background IP
• gives the client a sufficient licence to use background IP embedded in or necessary for the deliverables
• prevents the consultant from withdrawing access in a way that makes the deliverables unusable

3. Decide when the assignment happens

Ownership timing matters. Some agreements say the assignment occurs immediately on creation. Others say it happens only once the client has paid in full.

Neither model is automatically right or wrong, but the contract should be clear. If payment is tied to ownership, think about what happens if there is a payment dispute, partial completion, or an early termination.

Before you sign, make sure the timing aligns with the commercial deal and milestone structure.

4. Cover future rights and further assurances

Some IP rights only become fully clear over time, or additional paperwork may be needed later to perfect ownership. The agreement should require the consultant to do what is reasonably necessary after signing, such as executing confirmatory documents or helping record ownership where appropriate.

This matters particularly where the work may later be commercialised, licensed, sold, or scrutinised in due diligence.

5. Check for subcontractors and third party contributors

A consultant does not always do all the work personally. They may use employees, freelancers, offshore developers, specialist designers, or subcontractors.

If those people are not properly bound, the consultant may promise an assignment that it cannot fully deliver. Ask whether the consultant has written agreements in place so that all relevant rights are effectively passed through.

This point is easy to miss before you rely on a verbal promise that "our team will handle it". The contract should support that promise.

6. Consider moral rights and attribution issues

In some creative projects, moral rights can still matter even where ownership is assigned. Depending on the work involved, the agreement may need a consent relating to treatment, adaptation, or non-attribution, to the extent legally appropriate.

This often comes up with design, content, photography, video, and branding projects where the client wants flexibility to edit or repurpose materials later.

7. Match the IP clause with confidentiality and privacy obligations

Ownership is only part of the picture. A consultant may handle confidential information, customer data, internal processes, pricing, business plans, or sensitive technical material while creating the deliverables.

The agreement should work consistently across:

• confidentiality obligations
• privacy responsibilities where personal information is involved
• data return or deletion obligations at the end of the project
• restrictions on portfolio use, publicity, and case studies

For New Zealand businesses, privacy obligations and a clear privacy policy can be particularly relevant if a consultant is handling personal information while building systems, marketing tools, or customer-facing processes.

8. Review warranties and infringement risk

An assignment clause does not automatically protect you if the work copied someone else's intellectual property. If you are the client, you may want warranties that the deliverables are original to the extent promised, that the consultant has the right to assign them, and that third party material has been properly licensed.

You may also consider whether an indemnity is appropriate, depending on the size and risk of the project.

9. Think about termination and what survives

If the project ends early, ownership and usage rights can become messy. The agreement should say what happens to work in progress, partially completed deliverables, background IP licences, and unpaid materials if the contract is terminated.

This is especially important for staged builds, advisory projects, or retainers where output is created over time.

Common Mistakes With IP Assignment Clause Consulting Firms

The most common mistake is assuming the contract says more than it actually does.

Business owners often focus on scope, price, and timing, then skim over the IP section because it looks technical. That is usually the part that matters most once the work has value.

Assuming a confidentiality clause transfers ownership

Confidentiality and ownership are different issues. A consultant can be obliged to keep your information secret but still own the materials they create, unless the contract properly assigns them.

Using a one-size-fits-all clause

A short template may be fine for simple work, but it can fail badly on projects involving software, datasets, technical design, or layered content creation. A generic assignment of "all works" may ignore background IP, open source components, third party assets, or the practical need for ongoing licences.

Forgetting about pre-existing materials

Clients sometimes ask for all IP created "in connection with" the services, which can be broader than intended. Consultants sometimes resist that wording, but then fail to identify what pre-existing materials are actually excluded.

That leaves room for dispute. It is better to name categories clearly and, where needed, attach a schedule.

Not checking whether the consultant can assign what they promise

If the work includes stock images, licensed fonts, third party plug-ins, open source software, external research tools, or subcontractor contributions, there may be limits on assignment. In that case, the client may need a licence rather than ownership of those components.

This should be addressed before you sign, not after the project is delivered.

Leaving ownership conditional on vague payment wording

Some contracts say IP transfers on payment, but do not state whether that means each invoice, final payment, or full payment of all amounts ever due. If a dispute arises over a small amount, that ambiguity can become a larger commercial problem.

Clear milestone wording helps avoid that trap.

Ignoring future use and modification rights

Even if the client gets ownership of final deliverables, the contract may not say enough about source files, editable versions, passwords, admin access, development environments, or handover material. In practical terms, ownership is less useful if you cannot actually access or modify the asset.

Think about what your business will need six months after the consultant has moved on.

Relying on emails or verbal assurances

Founders often hear phrases like "of course you'll own it" or "we never reuse client work". Unless the contract reflects that position, those statements may not help much later.

Before you sign, put the commercial understanding into the written terms of the agreement itself.

Over-claiming ownership as a consultant

Consultants can make mistakes too. Demanding to keep ownership of all project output may look efficient at first, but it can make the deal unattractive, create procurement friction, or cause a client to walk away.

A balanced clause often wins trust faster than an aggressive one. The goal is to protect your reusable know-how without blocking the client from using what it paid for.

FAQs

Does paying a consultant mean my business owns the IP automatically?

Not necessarily. Payment and ownership are separate issues, so the agreement should state clearly whether IP is assigned, licensed, or partly split between project deliverables and background materials.

What is the difference between an IP assignment and an IP licence?

An assignment transfers ownership. A licence lets someone use the IP on agreed terms while ownership stays with the original owner.

Can a consultant keep ownership of their templates and methods?

Yes, that is common. A well-drafted agreement often lets the consultant keep background IP while giving the client rights to use any embedded materials needed for the deliverables to function properly.

Do subcontractors matter for IP ownership?

Yes. If subcontractors, freelancers, or developers contribute to the work, the consultant should have written agreements ensuring the relevant rights can be passed on to the client where required.

Should the clause cover draft materials and source files?

Usually, yes if those items matter to the project. If your business needs editable files, source code, design working files, or documentation for future updates, the agreement should say so expressly.

Key Takeaways

• An IP assignment clause in a consulting agreement decides whether your business owns the work product or only has limited rights to use it.
• Paying for consulting services does not automatically guarantee ownership of code, designs, documents, templates, or other deliverables.
• The contract should clearly distinguish project-specific deliverables from the consultant's background IP, methods, tools, and pre-existing materials.
• Before you sign, check timing of transfer, subcontractor arrangements, confidentiality, privacy, warranties, termination rights, and any need for ongoing licences.
• The best drafting is practical and specific, especially for software, branding, product development, technical design, and business systems projects.
• If you are reviewing or negotiating IP assignment clause consulting firms and want help with consulting agreements, intellectual property ownership terms, software and design deliverables, or confidentiality and licensing issues, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.