You’ve hired a designer to build your logo, a developer to create your app, or a marketing contractor to write your website copy. They deliver the files, you pay the invoice, and you start using the work in your business.
Then a question pops up (usually at the worst possible time): do you actually own it?
This is one of the most common “silent risks” for NZ businesses that use contractors. And because contracting is now a normal way to build and scale a business, it’s worth getting your intellectual property (IP) settings right from day one. This guide is updated to reflect current, real-world contracting practices and the increased focus on clear IP ownership in modern digital work.
Below, we’ll break down what IP ownership usually looks like in New Zealand, what the default legal position is, and how you can structure your contractor relationships so you’re not left with nasty surprises later.
Why IP Ownership Gets Confusing With Contractors
When you engage an employee, many business owners assume “anything they make for the job belongs to the business”. That’s not always perfectly automatic either (your employment contract matters), but it’s generally closer to how people expect work to operate.
Independent contractors are different.
Contractors are running their own business. They may:
- work for multiple clients at the same time
- reuse their own tools, templates, code libraries, or processes
- bring pre-existing materials into your project
- outsource parts of the work to subcontractors (if permitted)
- treat their work as part of their professional portfolio
So it’s completely normal for IP ownership to be more complicated than “you paid, therefore you own it”.
To make things trickier, “IP” isn’t just one thing. It can include:
- Copyright (e.g. written content, artwork, software code, photos, videos, training materials)
- Trade marks (e.g. your brand name, logo, slogan, and sometimes distinctive packaging)
- Design rights (e.g. product designs and visual features)
- Confidential information (e.g. customer lists, pricing, strategy, internal documents)
- Trade secrets and know-how (e.g. methods, formulas, processes)
In practice, most disputes happen because everyone thought they were on the same page… but nothing was clearly agreed in writing.
What Does NZ Law Say About Contractor-Created IP?
In New Zealand, the “default” starting point is usually:
- Contractors generally own the copyright in the work they create (unless a contract clearly says otherwise).
- Paying for work does not automatically transfer ownership of the underlying IP.
This surprises people, but it’s a key concept. You might have permission to use what you paid for, but you may not own it in the way you need to own it (for example, to modify it, sell it, license it, or stop others from using it).
Copyright Is Often The Big One
For many contractor projects (websites, branding, marketing content, photography, course content, software), copyright is the main IP right in play.
If you don’t clearly deal with copyright ownership, you can run into issues like:
- not being allowed to edit or adapt the work without the contractor’s permission
- limitations on using the work outside the original purpose (e.g. a logo designed “for socials” later used on packaging)
- the contractor reusing similar work for competitors
- difficulty selling your business or raising investment because you can’t prove you own core IP
Trade Marks Are Separate (But Still Connected)
A contractor can design a logo, but that doesn’t automatically mean you own all rights associated with it. Also, if the logo or name is too similar to someone else’s trade mark, you could face infringement problems even if you “own” the design files.
That’s why it’s smart to think about both:
- ownership of the design files (copyright), and
- protecting the brand in market (trade marks and brand clearance).
Even if something isn’t strictly “copyright”, you still want to protect what you share with contractors (like financials, product plans, customer data, and strategy).
That’s where the confidentiality terms matter, and why many businesses put an NDA in place before sharing sensitive information, especially early in discussions. A tailored Non-Disclosure Agreement can be a simple but powerful step.
Tip: If the contractor will access customer or user data (even just for testing), you also need to think about privacy obligations and making sure your business has the right external-facing documents in place, like a Privacy Policy.
How Do You Make Sure Your Business Owns The IP?
The safest approach is to set expectations upfront, in writing, before the work begins. When the contractor relationship is clear at the start, it’s usually straightforward, friendly, and fast.
When it’s dealt with later (after delivery, after payment, or after a relationship sours), it can become expensive and stressful.
Start With A Proper Contractor Agreement
Your first layer of protection is having the right agreement in place. A solid Contractor Agreement will usually cover:
- what is being delivered (and when)
- payment terms and milestones
- confidentiality and non-disclosure obligations
- who owns new IP created during the engagement
- whether the contractor can use the work in their portfolio
- warranties (e.g. the work is original and doesn’t infringe someone else’s rights)
- what happens if the relationship ends early
It’s also important that the agreement reflects reality. If your “contractor” is working like an employee (set hours, exclusive work, under your control), there can be legal risks beyond IP ownership, so it’s worth getting advice tailored to your setup.
Use An IP Assignment Where You Need Full Ownership
If the work is fundamental to your business (like your brand assets, core software code, or proprietary training materials), you’ll usually want the contractor to assign IP to you.
An assignment is basically a legal transfer of ownership. In practice, this often sits either:
- inside the contractor agreement as a clear “IP assignment” clause, and/or
- as a separate deed document that transfers IP once certain conditions are met (often payment).
For higher-value projects, a standalone IP Assignment can be a clean way to document the transfer.
Consider Licensing Instead (Sometimes That’s Enough)
Full ownership isn’t always necessary. Sometimes you just need broad, permanent permission to use the work. In those cases, an IP licence may make more sense than an assignment.
A licence can be appropriate where:
- the contractor uses pre-existing tools, templates, or frameworks
- you’re happy for the contractor to keep ownership, but you need ongoing usage rights
- the deliverable is not central to your competitive advantage
If licensing is the right approach, it should still be very clear and business-friendly (for example, worldwide, perpetual, and allowing you to modify and sublicense if needed). That’s where an IP Licence can help lock in the usage rights you actually need.
Don’t Forget Moral Rights (Especially For Creative Work)
In NZ, creators may have “moral rights” in certain works (for example, the right to be identified as the author, or to object to derogatory treatment of a work). These can matter for branding and marketing assets.
Even if you own copyright, you may want the contractor agreement to address how attribution will work and whether the contractor consents to edits and adaptations (so you’re not stuck later when you need to rework or update content).
Common Contractor Scenarios (And The IP Traps To Watch For)
Most IP disputes aren’t about “bad behaviour”. They happen because the project moved quickly, everyone was focused on delivery, and the legal basics were left for later.
Here are some common scenarios where it’s worth being extra clear.
1) A Designer Creates Your Logo Or Brand Kit
You’ll typically want to ensure:
- you own (or have broad rights to use) the final logo, icons, fonts (where licensing allows), and brand guidelines
- you receive editable source files (not just flattened PNGs)
- the designer confirms the work is original and doesn’t infringe others
- portfolio use is agreed (for example, allowed after your launch date)
If you’re planning to scale, sell the business, franchise, or license your brand, clean IP ownership in your brand assets is a big deal.
2) A Developer Builds Your Website Or App
Software projects often involve a mix of:
- new custom code built specifically for you
- open-source components (with their own licences and obligations)
- the developer’s existing libraries, frameworks, or reusable modules
- third-party platform terms (Shopify apps, WordPress plugins, hosting providers)
This is why “you own everything” can be unrealistic, but “you only get a limited right to use it” can be too risky.
A well-drafted Software Development Agreement can clearly separate:
- background IP (what the developer already owned before the project)
- project IP (what is created for you during the engagement)
- licensing terms for any background IP embedded in the deliverables
- handover obligations (code repositories, documentation, admin access)
It can also include practical protections, like warranty clauses, bug-fix periods, and support arrangements, so you’re not stuck if the relationship ends.
3) A Marketing Contractor Writes Content Or Makes Videos
Content is IP-rich, and it gets reused everywhere (website, ads, social media, brochures, email sequences). Make sure the agreement covers:
- who owns the copy, scripts, images, and video files
- whether stock images/music are used and who pays for licensing
- whether you can edit, repurpose, or reuse the content in future campaigns
- who owns raw footage and project files
Also consider whether the contractor might be using AI tools as part of creation (which is increasingly common). Your contract should be clear on quality, originality, confidentiality, and infringement risk, rather than relying on assumptions about how work is produced.
4) A Contractor Creates Training, Course, Or Internal Documents
If a contractor creates training materials, SOPs, onboarding resources, or course modules, those can become core business assets. Without proper ownership terms, you might not be able to:
- scale training across a growing team
- sell the course or license it later
- stop the contractor from reusing similar materials elsewhere
These projects often suit an IP assignment model, plus strong confidentiality obligations.
What If There’s No Contract (Or The Contract Is Silent)?
If you’re already partway through a project and you’re now realising the IP position isn’t clear, don’t panic. You still have options, but it’s best to act quickly and keep things professional.
Step 1: Identify What You Actually Need To Own
Start with the practical questions:
- Do you need exclusive rights, or just permission to use it?
- Do you need to modify the work, or only use it “as delivered”?
- Do you need to sublicense it (e.g. to customers, franchisees, partners, or a buyer)?
- Is the work central to your value (brand, codebase, product design), or more replaceable?
This helps you choose between an assignment and a licence, and it keeps negotiations grounded in what matters.
Step 2: Check What You Paid For (And What Was Delivered)
Invoices, email chains, proposals, statements of work, and messages can give clues about the intended scope of use. Sometimes the parties have (informally) agreed to a broad right to use the deliverable, even if ownership wasn’t clearly transferred.
But relying on scattered communications is risky, especially if you want to raise capital, sell the business, or enforce your rights later.
Step 3: Paper It Properly With A Deed Or Updated Agreement
Often the cleanest fix is:
- a short deed of assignment signed by both parties; or
- an updated contractor agreement confirming IP ownership/licensing going forward.
Done early and respectfully, this is usually a simple admin step. Done late (after a dispute), it can turn into leverage and cost.
Step 4: Think About The Bigger Risk Picture
IP ownership issues don’t just create legal headaches. They can block commercial opportunities.
For example, if you later want to bring on investors or sell your business, due diligence will often ask:
- Do you own your brand assets?
- Do you own (or properly license) your software and content?
- Have all contractors assigned IP to the business?
If you can’t answer “yes” confidently, you may face delays, price reductions, or additional documentation requirements right when you want a smooth transaction.
Key Takeaways
- Don’t assume you automatically own contractor-created IP just because you paid for it. In many cases, contractors will own copyright unless it’s clearly assigned or licensed to you.
- Get clear IP terms in writing before work begins. This is usually the easiest (and cheapest) time to set expectations and avoid disputes.
- Use the right document for the job. A tailored Contractor Agreement is a strong starting point, but key assets may also need an IP Assignment or IP Licence depending on what you’re building.
- Be specific about what’s included in the deliverables. Source files, raw footage, repositories, documentation, and handover obligations should be clearly listed.
- Watch out for mixed-IP projects like software. Developers may use pre-existing libraries and open-source components, so your agreement should separate background IP and new IP.
- If there’s no contract (or it’s silent), you still have options. The sooner you document ownership or licensing properly, the less risk you carry as your business grows.
If you’d like help locking in IP ownership with contractors or updating your agreements so you’re protected from day one, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
