Freelancer IP for NZ Not-for-profit Service Providers

If your not-for-profit uses freelancers for branding, website work, programmes, training materials, photography or grant-funded projects, do not assume your organisation automatically owns what gets created. That is where many charities, incorporated societies and other service providers get caught. A common mistake is paying an invoice and assuming payment transfers ownership. Another is using a short email brief instead of a proper contract. A third is letting a freelancer reuse the same materials for other clients without thinking through whether your organisation needs exclusivity.

The main issue is simple: unless the contract says otherwise, the person who creates original work will often own the intellectual property. That can become a real problem when you want to update your website, expand a programme, licence materials to partners, or stop a former freelancer from reusing your branding. This guide explains how freelancer IP ownership works in New Zealand, when the issue comes up for not-for-profit service providers, and what to put in place before you sign a contract, invest in branding, or publish content created by external contractors.

Overview

For a New Zealand not-for-profit service provider, freelancer IP ownership usually turns on the contract, not on who paid for the work. If you want your organisation to own logos, content, software code, course materials or campaign assets created by a freelancer, the agreement should clearly say that IP is assigned to the organisation, and it should also deal with pre-existing materials, moral rights, confidentiality and reuse.

Confirm whether the worker is a freelancer or an employee, because ownership rules are different.
State exactly what intellectual property is being created, and whether ownership transfers or a licence applies.
Identify any pre-existing templates, tools, stock images or software libraries the freelancer brings into the project.
Decide whether your organisation needs exclusive use, full assignment, or a narrower licence.
Cover moral rights consents where copyright works are involved, especially for design, written content, video and photographs.
Include confidentiality, privacy and data handling terms if the freelancer will access donor, client or staff information.
Check whether funder conditions, collaboration arrangements or partner agreements affect who should own the work.

What Freelancer IP Ownership Not-for-profit Service Provider Means For New Zealand Businesses

The short answer is that your not-for-profit does not automatically own IP created by a freelancer just because you commissioned it or paid for it.

In New Zealand, intellectual property can include copyright, trade marks, confidential information, designs, software code, databases, educational resources, policy manuals, recordings and branding assets. For many not-for-profit service providers, the most relevant rights are copyright and trade marks.

logos and visual branding elements
website copy and page layouts
training manuals and workshop slides
videos, photos and audio recordings
software code and digital tools
research reports and impact summaries
programme materials and service templates

If an employee creates copyright material in the course of employment, the employer will often own it, subject to the employment arrangement and any special circumstances. A freelancer is different. An independent contractor commonly owns the copyright in what they create unless the contract transfers ownership or creates a sufficiently clear right for the client to use it.

This distinction matters because many not-for-profits use small project teams made up of employees, volunteers and freelance specialists. Founders and managers can assume everyone contributing to a community programme is on the same footing, but the legal position is not the same across those relationships.

Why ownership matters for not-for-profit service providers

The practical question is not just who made the work. The practical question is what your organisation wants to do with it later.

If your organisation owns the IP, it is generally in a stronger position to:

reuse and adapt materials across future programmes
share resources with partner organisations or regional branches
update a website or software platform with another provider
stop others from copying distinctive content or branding
apply for a trade mark based on branding you actually control
meet funding or procurement requirements about ownership of project outputs

If your organisation does not own the IP, you may only have an implied or express licence to use it in limited ways. That can leave you exposed when the freelancer relationship ends, when you want to scale nationally, or when another supplier needs access to the original working files.

Ownership versus licence

A full assignment means the freelancer transfers ownership of the specified IP to your organisation. A licence means the freelancer keeps ownership but gives your organisation permission to use the material in agreed ways.

Neither model is automatically right or wrong. A licence may be enough for one-off photography or a limited campaign. An assignment is often better for core assets, such as:

your organisation's name, logo and brand system
website build and custom code for your service delivery platform
signature programme materials that define your service offering
training and assessment tools that you plan to use long term

This is where founders often get caught. They ask for a logo, social media pack or website, but the contract only gives them a basic right to use the final files. That can be too narrow if the organisation later needs source files, editable documents, code repositories, or the right to adapt the work without further approval.

Trade marks are a separate issue

Owning copyright in a logo is not the same as having a registered trade mark. If your not-for-profit is investing in branding before you register a domain or print signage, trade mark strategy should be part of the conversation.

A freelancer may create your name or logo, but your organisation should make sure it has the right to use and register that branding. If ownership is unclear, trade mark registration and brand enforcement can become harder later.

When This Issue Comes Up

This issue usually appears at ordinary growth moments, not during a legal crisis. The best time to sort it out is before you sign a contract or launch the work publicly.

Branding and rebrands

A not-for-profit often brings in a freelance designer to refresh its logo, colour palette, donor materials and website look. If there is no clear IP clause, the organisation may end up with only a limited right to use the finished brand package.

That becomes a problem when you want to tweak the design later, use it across new campaigns, or stop the designer from recycling a similar identity for another organisation in the same space.

Websites, apps and digital service tools

Many service providers outsource web development, booking systems, member portals or programme delivery tools to freelancers. The main risk is assuming ownership of code, designs and databases without checking the contract.

In digital projects, you also need to ask what sits underneath the final product. A freelancer may use:

their own code libraries or frameworks
third-party plugins or paid themes
stock imagery and licensed fonts
AI-assisted content or design elements

Your agreement should say what is assigned, what remains the freelancer's background IP, and what third-party terms apply. It should also deal with access credentials, handover, maintenance and privacy obligations if personal information is involved.

Programme materials and educational content

Service-based not-for-profits often rely on freelance writers, facilitators, educators and evaluators to create workshop manuals, policy resources, online modules or client-facing guides. Those materials can become central to the organisation's service model.

If ownership is not dealt with properly, you may not have the right to revise the materials, sublicense them to delivery partners, or adapt them for new funding streams or regions.

Funded projects and collaborations

Grant-funded work often creates extra complexity. A funder may expect certain project outputs to be publicly available, controlled by the lead organisation, or shared with project partners. If a freelancer owns the underlying content and your organisation only has a narrow licence, your funding commitments can be harder to meet.

The same issue comes up where two organisations collaborate on service delivery. If one organisation commissions a freelancer to create shared resources, everyone should be clear on who owns the materials and who can use them after the project ends.

Photos, video and storytelling campaigns

Freelance photographers and videographers are frequently engaged for campaigns, annual reports and awareness initiatives. Not-for-profits sometimes focus on participant consent forms and forget the creator's rights.

You need to consider both sides of the picture:

the organisation's rights to use, edit and publish the content
the permissions needed from the people appearing in the content

Those are separate issues. A release from the subject does not transfer the photographer's copyright, and a copyright assignment from the photographer does not replace privacy or consent processes.

Practical Steps And Common Mistakes

The best protection is a written freelancer agreement tailored to the asset being created, signed before the work starts.

1. Classify the working relationship properly

Do not call someone a contractor if they are really functioning like an employee, and do not assume a contractor is covered by employee ownership rules. The label matters less than the real arrangement, but the contract should still reflect the intended relationship clearly.

If you are unsure whether a role is employment or independent contracting, get advice before the engagement begins. IP ownership is only one part of that question.

2. Describe the deliverables in detail

Vague scopes create ownership disputes. A contract should identify what the freelancer is actually creating and what must be handed over at the end.

For example, a better scope may include:

final logo files in specified formats
brand guidelines and editable source files
website copy, graphics and image licences
custom code, documentation and administrator access details
training manuals, slide decks and facilitator notes
raw photo or video files if needed for future editing

This matters before you spend money on setup, because the value often sits in the editable files and practical control, not just the finished PDF or image.

3. State whether IP is assigned or licensed

If your organisation needs ownership, say so clearly. If a licence is enough, define its scope. Do not rely on assumptions.

A good clause usually addresses:

when the assignment takes effect, such as on creation or on payment
whether all present and future rights in the deliverables are included
whether the licence is exclusive or non-exclusive
whether the organisation can modify, reproduce, distribute or sublicense the work
whether the freelancer can reuse any part of the work for other clients

For core brand assets and service materials, a full assignment is often the cleaner option. For specialist tools the freelancer uses across clients, a carve-out for their background IP with a broad licence to your organisation may be more realistic.

4. Separate new IP from background IP

Many freelancers bring pre-existing materials into a project. That may include templates, know-how, code snippets, design systems, worksheets or proprietary methods they use with multiple clients.

Your contract should distinguish between:

new IP created specifically for your organisation
background IP the freelancer already owned before the project
third-party materials licensed from others

If this split is not spelled out, ownership can be messy. You may think you bought the whole website or programme toolkit, while the freelancer thinks you only bought a right to use their standard framework.

5. Deal with moral rights

Copyright creators can have moral rights connected with their work, such as the right to be identified as author and the right to object to derogatory treatment in some circumstances. For design, written content, photography and film, your agreement should deal with moral rights consents where appropriate.

This can be especially useful if your organisation may edit materials over time, remove author credits, translate content, or combine works into new resources.

6. Include confidentiality and privacy terms

Not-for-profit service providers often handle sensitive information about donors, members, clients, volunteers or staff. A freelancer building a CRM integration, drafting case studies or producing reports may access personal or confidential information.

Your contract should cover:

what information is confidential
how information can be used and stored
who can access it
what happens on termination
what must be returned or deleted

If personal information is involved, your practices should also align with your Privacy Act obligations, privacy policy, and your own internal policies.

7. Secure practical control, not just legal rights

Ownership on paper is not enough if the freelancer keeps all the passwords, source files and platform access. Before you launch online or hand over a programme to staff, make sure the organisation controls the essentials.

That often includes:

domain registrar access
website hosting and CMS administrator access
social media account ownership
cloud storage folders and design files
code repositories and deployment credentials
licence keys and third-party service accounts

Founders often focus on the legal clause and miss the operational handover. Both matter.

8. Watch for common contract gaps

Small organisations often use recycled templates or informal email chains that leave too much unsaid. The most common mistakes include:

no written agreement at all
an agreement that talks about payment but not IP
an assignment clause that does not clearly cover all deliverables
no mention of background IP or third-party licences
no handover obligations for files, accounts and access
no confidentiality or privacy wording
no permission to edit or adapt the work

Another common mistake is signing the freelancer's own terms without reviewing the IP clause or getting a contract review. Many standard contractor terms are written to preserve the freelancer's ownership.

9. Match the IP terms to your organisation's structure and plans

The right arrangement depends on how your not-for-profit operates. An incorporated society, charitable trust or company limited by shares may all have different governance and approval processes, but each still needs clarity on asset ownership.

Think about what your organisation will need in the next few years, such as:

licensing materials to partner organisations
merging programmes or rebranding
selling services online or expanding into digital delivery
applying for future grants tied to project outputs
registering a trade mark for your core brand

IP terms should support those plans rather than creating friction later.

FAQs

Does paying a freelancer mean our not-for-profit owns the work?

No. Payment alone does not necessarily transfer intellectual property. You usually need a written contract that clearly assigns the IP or gives your organisation the right licence.

Can a freelancer keep using the same materials for other clients?

Yes, if the contract allows it or if they retain ownership. If your organisation needs exclusivity, especially for branding or signature programme content, the agreement should say that clearly.

What if the freelancer used templates, stock images or existing code?

Your organisation may not own those underlying materials. The contract should identify pre-existing and third-party materials, and confirm what rights your organisation receives to use them.

Do we need both an IP clause and a confidentiality clause?

Usually, yes. IP ownership and confidentiality deal with different risks. One covers rights in the work created, and the other covers protection of sensitive business, donor, client or service information.

Should our not-for-profit register a trade mark if a freelancer created our logo?

Often, yes, if the brand is central to your services and public identity. First make sure your organisation has clear rights to use and register the branding created by the freelancer.

Key Takeaways

For New Zealand not-for-profit service providers, freelancer IP ownership usually depends on the contract, not on who paid for the work.
Employee-created IP and freelancer-created IP are treated differently, so the worker's status matters.
Core assets like branding, websites, programme content and digital tools should have clear assignment or licensing terms before the project starts.
Your agreement should also address background IP, third-party materials, moral rights, confidentiality, privacy and practical handover of files and access.
Sorting this out early helps your organisation adapt materials, scale services, protect its brand and avoid disputes when a freelancer engagement ends.

If your business is dealing with freelancer IP ownership not-for-profit service provider and wants help with freelancer agreements, IP assignment clauses, trade mark planning, confidentiality and privacy terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.