Pre-Existing Intellectual Property Rights: Who Owns What?

When you start a project, hire a contractor, or collaborate with a partner, there’s a good chance someone is bringing existing materials, code, designs or know‑how to the table. That existing material is often called “pre‑existing IP” or “background IP”.

Getting ownership and usage rights wrong at this point can cause real issues later - from product delays to disputes over who can commercialise the final outcome.

The good news? With a clear understanding of how pre‑existing intellectual property (IP) works in Australia, and the right contracts, you can set expectations early and protect your investment while respecting others’ rights.

Below, we break down what counts as pre‑existing IP, who usually owns it, and how to document background IP versus project IP so everyone is on the same page from day one.

What Counts As Pre‑Existing IP?

Pre‑existing IP (often called “Background IP”) is anything that existed before a particular project or engagement began, and which a party brings into the project. It might be:

• Source code libraries, SDKs or frameworks your developer wrote last year.
• Design templates, style guides, brand assets and photography a creative agency already owns.
• Proprietary processes, training content, datasets or algorithms a business has developed.
• Patents, trade marks, registered designs or unregistered copyright a party already holds.

By contrast, “Foreground IP” (often called “Project IP” or “New IP”) is created during the project itself - for example, the specific app built for you, the logo designed to your brief, or the course content produced under the contract.

Both types of IP matter. Background IP is the foundation that enables a project to run efficiently; Foreground IP is the outcome you want to own or use. Your contracts should clearly spell out the difference and allocate rights in each.

Who Owns Pre‑Existing IP In Australia?

Ownership depends on the relationship between the parties and the type of IP. Here’s how it typically plays out under Australian law:

Employees vs Contractors

• Employees: As a general rule, IP created by an employee in the course of their employment is owned by the employer. This is why a well‑drafted Employment Contract should reinforce that position and clarify what’s “in the course of employment”.
• Contractors: Independent contractors usually own the IP they create by default, unless the contract assigns it to the client. If you’re engaging a freelancer or external firm, your Contractors Agreement should set out exactly who owns what - including any pre‑existing materials they bring to the job.

Copyright Is Automatic, Moral Rights Still Apply

Copyright in Australia arises automatically when an original work is created (there’s no registration system). The creator also retains “moral rights” (such as the right to be attributed), even if economic rights are assigned. Your contracts can include moral rights consents where appropriate, especially for public‑facing works.

Trade Marks, Designs And Patents

Ownership of registered rights (like trade marks and designs) sits with the named owner on the register unless transferred. If someone contributes a registered right to a project, you’ll likely need a licence to use it rather than an assignment of title - unless there’s a strategic reason to transfer ownership outright.

Licences Vs Assignments: How Should You Use Someone Else’s Pre‑Existing IP?

When a party brings background IP into a project, you’ll typically choose between a licence (permission to use) or an assignment (transfer of ownership).

When To Use A Licence

Licensing allows the owner to keep title to their pre‑existing IP while giving the other party the rights needed to use it for the project and ongoing operations.

A well‑drafted licence spells out:

• Scope: What can you do with the IP (copy, modify, distribute)?
• Purpose: Is it limited to the project, a particular product, or your whole business?
• Exclusivity: Is the licence exclusive or non‑exclusive?
• Territory and term: Where and for how long can you use it?
• Fees/royalties: One‑off fee or ongoing royalties for use.
• Transfer/sublicensing: Can you grant rights to affiliates or subcontractors?

For content and creative materials, consider a IP Licence. For code, software or SaaS, you might rely on specific product terms or a negotiated licence within your master agreement.

When To Use An Assignment

An assignment permanently transfers ownership of the IP from one party to another.

Assignments are common when:

• You are paying for a bespoke outcome and want clear, unambiguous ownership of the Foreground IP.
• The business value depends on owning the code base, brand or design outright (for example, to sell or license it onwards).
• Investors or acquirers expect you to hold title to all key IP assets.

Use an IP Assignment to transfer ownership and set any carve‑outs (for example, the creator retains their pre‑existing libraries but assigns the specific deliverables). If you’re only licensing material, a standalone IP Licence remains appropriate.

How To Handle Background IP In Your Contracts

The best place to resolve “who owns what” is in writing - before work starts. Clear contract wording avoids confusion and keeps projects moving. The following techniques are standard:

Define Background IP And New IP

Start with precise definitions. For example: “Background IP means any intellectual property existing before the Commencement Date and contributed to the Services. New IP means any intellectual property created in providing the Services.”

Allocate Ownership

• Background IP: Usually remains with the original owner, with a licence granted to the other party as needed to use the final deliverables.
• New IP: Decide whether the client owns it on creation, or whether the supplier owns and licenses it back. If the client will own it, include an automatic assignment clause.

Grant The Right Licences

Spell out the licence scope to any Background IP necessary for ongoing use of the deliverables (for example, a perpetual, worldwide, royalty‑free licence). If the supplier relies on open‑source software, disclose licence obligations so there are no surprises.

Include Moral Rights Consents And Attribution

Where individuals create works, include reasonable attribution requirements and moral rights consents if you might need to alter or not attribute those works in future.

Use Confidentiality Early

Before any technical or creative deep‑dive, protect disclosure of pre‑existing materials with a Non‑Disclosure Agreement. This keeps negotiations safe while you explore whether a licence or assignment is needed.

Choose The Right Engagement Document

• For build projects, a tailored Software Development Agreement is ideal for scoping New IP ownership, third‑party components, open‑source usage and licences.
• For general services, a strong master services agreement or Contractors Agreement can set the baseline on IP, confidentiality and deliverables.
• For content or brand assets, consider a fit‑for‑purpose IP Licence or, if you need title, an IP Assignment.

Common Scenarios (And How To Get Them Right)

1) You Hire A Developer Who Reuses Their Own Libraries

Your developer may bring pre‑existing libraries they’ve built over years. They’ll likely want to retain ownership of those libraries, which is fair. You can still own the New IP (the app itself) and take a perpetual licence to the libraries so your product runs and can be maintained.

Document this balance in a Software Development Agreement with clear Background IP schedules and licence scope.

2) A Creative Agency Uses Its House Templates And Fonts

The agency’s templates, presets and stock may stay with them, while you own the specific designs created for you. Ensure the licence lets you reproduce, adapt and commercialise the deliverables across all channels you need (web, print, social, packaging, etc.).

3) A Contractor Produces Training Materials You’ll Use Internally

If the main value is internal use, a licence might be enough. But if you plan to resell the materials or embed them in a product, consider an assignment of New IP (and the necessary licences to any Background IP they’ve incorporated).

4) Your Employee Invents Something Using Company Resources

If created in the course of employment, the company typically owns the IP. Make sure your Employment Contract confirms this and requires disclosure of inventions and cooperation with filings, if you pursue protection.

5) Brand Elements: Who Owns The Name, Logo And Look?

Even if a designer helps, your business can own the brand assets if the agreement assigns the New IP. Then, lock in your brand protection and register your trade mark so you have nationwide rights to your name and logo.

Key Clauses To Include So “Who Owns What” Is Crystal Clear

To minimise risk and confusion, make sure your agreements cover:

• Definitions: Clear definitions for Background IP and New IP.
• Ownership: Who owns New IP on creation; automatic assignment wording if applicable.
• Licences: Scope, term and territory for any Background IP needed to use the deliverables.
• Third‑Party Materials: What’s included (fonts, stock, plugins), licence terms, and who pays ongoing fees.
• Attribution & Moral Rights: How creators will be credited and whether consents are required for edits/non‑attribution.
• Open‑Source: Disclosure of open‑source components and compliance responsibilities with licence terms.
• Escrow/Access: Practical access to source files, working files or repositories, where appropriate.
• Exit Rights: What happens if the relationship ends - ongoing licence rights, handover obligations, and assistance.
• Confidentiality: Protection for any non‑public information exchanged (often backed by a Non‑Disclosure Agreement).

Protecting Your Own Pre‑Existing IP Before You Share It

Before you bring your Background IP into any collaboration, take some simple steps to protect its value:

• Record Ownership: Keep dated records and version histories for code, designs and documents. This helps evidence what existed before the project.
• Use NDAs: Share details under a Non‑Disclosure Agreement while you negotiate commercial terms.
• Secure Registrations: If appropriate, file to register your trade mark or other registrable rights (such as designs) so ownership is clearer and easier to enforce.
• License Deliberately: Grant only the rights the other party truly needs - consider term limits, geography and ability to sublicense.
• Keep Carve‑Outs: If you need to reuse your Background IP in other projects, reserve those rights explicitly in your licence.

How To Avoid Disputes (And Keep Projects Moving)

Most IP disputes in projects arise from assumptions. People assume they own something because they paid for it, or they assume they can reuse materials because they created them years ago. Put the assumptions to bed with upfront, plain‑English clauses.

A practical workflow looks like this:

1. Pre‑contract: Exchange high‑level information under an NDA.
2. Scoping: Identify Background IP each party will bring; list third‑party materials and open‑source components.
3. Contracting: Agree on ownership of New IP, licences to Background IP, and any royalties if commercialisation is joint or ongoing.
4. Delivery: Ensure acceptance criteria include handover of files and any necessary access (repositories, design files, asset libraries).
5. Post‑delivery: Confirm ongoing licence rights and maintenance obligations.

If you’re commissioning creative works for broad reproduction or resale, consider whether you need an assignment now, or whether the creator will license to you with a fee structure tied to sales. Where ongoing payments are expected, make sure royalty terms align with how your products are actually sold.

Key Takeaways

• Pre‑existing IP (Background IP) is anything that existed before a project; New IP (Foreground IP) is what’s created during the project.
• Employees’ work is typically owned by the employer; contractors usually own what they create unless your contract assigns it - make sure your Employment Contract and Contractors Agreement are clear on this.
• Use licences when a party needs permission to use Background IP, and assignments when ownership of New IP (or certain assets) must transfer.
• Spell out IP ownership, licence scope, third‑party materials, open‑source use and moral rights in your agreements to avoid confusion later.
• Protect your own Background IP early with NDAs and, where appropriate, registrations such as to register your trade mark.
• For build or content projects, use fit‑for‑purpose documents like a Software Development Agreement, an IP Licence or an IP Assignment so “who owns what” is crystal clear.

If you’d like help documenting pre‑existing IP, licences or assignments for your project, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no‑obligations chat.