How To Draft An Intellectual Property Clause For Your Contract

If you’re building a startup or growing an SME, chances are you’re creating (or paying for) valuable things every day - your brand name, your website, your software, your product designs, your marketing content, your training materials, even your internal processes.

The tricky part is that “who owns what” isn’t always as obvious as it feels when you’re moving fast.

That’s where a well-drafted intellectual property clause comes in. It helps you avoid misunderstandings, protect your investment, and keep control of the assets that actually make your business valuable (especially if you ever raise capital, sell your business, or bring on strategic partners).

Below we’ll walk you through how to draft an intellectual property clause in a practical, startup-friendly way - including what to include, common traps, and example wording you can adapt (with the important note that your final clause should be tailored to your specific deal).

What Is An Intellectual Property Clause (And Why Does It Matter)?

An intellectual property clause is the part of a contract that sets out how IP is treated between the parties.

In plain English, it answers questions like:

• What IP is being brought into the relationship (and who already owns it)?
• What IP will be created during the project (and who will own it)?
• Is anyone allowed to use the other party’s IP - and if so, how?
• What happens to IP when the relationship ends?

This clause is especially important for startups and SMEs because you’re often:

• working with contractors rather than employees;
• outsourcing core deliverables (like design, development, marketing, or content);
• collaborating with other businesses;
• moving quickly and iterating (which creates lots of new materials); and
• building value in intangible assets that don’t “sit” on your balance sheet unless you own them.

If your contract is silent (or vague) on IP ownership, you can end up paying for something but not fully owning it - which can create expensive issues later, especially during due diligence or a dispute.

Step 1: Identify What “Intellectual Property” Means In Your Contract

Before you can draft a strong intellectual property clause, you need to define what counts as “IP” in the agreement.

Most contracts include a definition of Intellectual Property that covers a broad list, such as:

• copyright (e.g. written content, code, website copy, designs, photos, videos)
• trade marks (e.g. brand names, logos, taglines)
• patents (e.g. inventions and new technical solutions)
• design rights (e.g. product appearance and visual features)
• trade secrets and confidential information (e.g. pricing models, customer lists, processes)
• domain names, social handles, and related digital assets

Why Definitions Matter (More Than You’d Think)

Definitions do a lot of heavy lifting. If your definition is too narrow, important assets can fall outside the clause. If it’s too broad without clarity, the clause can create confusion or overreach (for example, unintentionally claiming ownership over a contractor’s tools or templates).

A good approach is to define IP broadly, then separate it into categories like:

• Background IP (pre-existing IP brought in by either party)
• Project IP (IP created specifically for the project)
• Third Party IP (IP owned by someone else that may be used in the deliverables)

This sets you up to draft the ownership and licence parts of the intellectual property clause cleanly.

Step 2: Decide Who Owns Background IP Vs New IP

One of the most common reasons IP clauses cause problems is that they don’t clearly distinguish between:

• what each party already owns, and
• what is created as part of the engagement.

Background IP: Keep It With The Original Owner

As a starting point, it’s common for the contract to say:

• Each party retains ownership of its Background IP.
• Nothing in the agreement transfers ownership of Background IP, except as expressly stated.

This matters because your contractor (or partner) might bring tools, frameworks, code libraries, design systems, or templates that they use across clients. They’ll usually want to keep owning those.

You’re not necessarily trying to own their entire toolkit - you’re trying to own (or have rights to use) what you’re paying for.

New IP: Make Ownership A Conscious Choice

Next, decide what happens to IP created under the agreement (often called “Developed IP”, “Project IP”, “Deliverables IP”, or similar).

Common approaches include:

• Assignment to you (the business): the contractor assigns all rights in the new IP to you, usually on payment.
• Contractor retains ownership, you get a licence: you can use the deliverables, but you don’t own them.
• Shared ownership: generally not recommended unless the arrangement truly requires it, because “shared” can create future restrictions and uncertainty.

For most startups and SMEs commissioning core deliverables (like website builds, branding, software, or key marketing assets), you’ll usually want an assignment of IP so your business owns what it paid to create.

If you’re engaging someone under an ongoing services arrangement, you might document the engagement in a Consulting Agreement (or a tailored services contract) with an IP clause that clearly deals with both Background IP and newly created materials.

Step 3: Include An IP Assignment (And Make Sure It Actually Works)

An “IP assignment” is the part of the intellectual property clause that transfers ownership from the creator to your business.

For Australian startups and SMEs, this is a critical point: paying for work does not automatically mean you own the IP in that work, especially if it’s created by an independent contractor.

What A Practical IP Assignment Should Cover

Your assignment wording should usually address:

• What is being assigned: the IP in the deliverables, and often any related materials created in providing the services.
• When the assignment happens: immediately on creation, or on payment (or both).
• Further assurance: an obligation to sign documents and do acts needed to perfect the transfer (important for formal registrations or platform transfers).
• Moral rights (where relevant): consents for certain uses of copyright materials (more on that below).

Example IP Assignment Wording (General Only)

Here’s an example structure (not a one-size-fits-all clause):

• “The Service Provider assigns to the Client all right, title and interest in and to the Project IP upon creation (and in any event upon payment of all fees due).”
• “The Service Provider must do all things and sign all documents reasonably required by the Client to give effect to this assignment.”

In practice, the “what counts as Project IP” definition is what prevents disputes. If “Project IP” is poorly defined, the assignment may be too narrow (or too broad) for your needs.

Don’t Forget Moral Rights (Especially For Branding, Content And Design)

If the deliverables include copyright works (like written copy, designs, photos, videos, or code), moral rights may be relevant. Moral rights relate to how the creator is attributed and whether their work is treated in a way that harms their reputation.

Startups often need the flexibility to edit, adapt, or repurpose materials (for example, tweaking branding assets or updating website content). That’s why IP clauses often include a moral rights consent to reduce the risk of later friction - noting that moral rights can’t be assigned, and a consent won’t necessarily cover every possible future use unless it’s drafted appropriately.

This is particularly important for marketing and brand work, where you may want to adapt assets across platforms and campaigns.

Step 4: Add The Right Licences (Because Not Everything Should Be Assigned)

Even when you want to own the core deliverables, there are situations where a licence (permission to use IP) makes more sense than an assignment.

When A Licence Is The Better Fit

You may need a licence where:

• the supplier needs to keep using their Background IP to deliver the services (e.g. software tools, reusable templates);
• you are using third-party materials (e.g. stock images, plugins, fonts, open-source libraries);
• you’re entering a partnership and both sides need rights to use each other’s IP without transferring ownership; or
• the relationship is more like a subscription/service access model, rather than a bespoke “build and handover”.

A good intellectual property clause will often include:

• a licence from you to them (limited rights to use your IP for the project), and
• a licence from them to you (rights to use any Background IP embedded in the deliverables).

Key Licence Terms To Decide

When drafting an IP licence, be clear on:

• Scope: what can the IP be used for?
• Territory: Australia only, or worldwide?
• Duration: for the project term, or ongoing?
• Sublicensing: can you allow others (like customers, affiliates, related entities, or future buyers) to use it?
• Exclusivity: exclusive or non-exclusive?

If you expect future growth (investors, acquirers, offshore expansion), a licence that is too narrow can quietly become a blocker later.

For example, if a developer retains ownership of a critical component and only gives you a limited licence, your ability to sell the business or raise capital may be affected. This is why it’s worth getting the IP clause right from the start.

Step 5: Address Confidentiality, Employees/Contractors, And Practical “Handover” Details

Your intellectual property clause shouldn’t sit in isolation. It works best when it aligns with the rest of the agreement - especially confidentiality, payment, termination, and who is actually doing the work.

Make Sure The Right People Are Bound

If you are contracting with a business (e.g. an agency), but the work is actually being created by individuals (employees or subcontractors), your contract should ensure the supplier is responsible for obtaining valid assignments/consents from the people doing the work.

This helps avoid the situation where you have a signed agreement with the agency, but the individual creator later claims ownership or objects to use.

Link IP Transfer To Payment (Carefully)

Many businesses prefer that IP transfers only once payment has been made. This is a reasonable commercial position, but you should be clear about it in the clause so there’s no ambiguity.

If you want the best of both worlds, you can structure it so the assignment is effective on creation but subject to payment, or it becomes effective upon payment. The right approach depends on your commercial leverage and the risk profile of the project.

Include “Deliverables” And Handover Obligations

If the goal is that you can actually operate the business asset after the engagement ends, your contract should spell out handover requirements, such as:

• source files (design files, editable formats, code repositories)
• admin access to accounts (domains, hosting, analytics, ad accounts, social pages)
• documentation (so your team can maintain or update the asset)
• third-party licence details (plugins, fonts, stock assets, open-source notices)

This isn’t always “IP” in the strict legal sense, but it’s often the practical difference between owning something on paper and being able to use it in real life.

Don’t Overlook Employment And Contractor Settings

If you’re building IP with staff or contractors, you should ensure your agreements cover IP ownership consistently across your business.

For employees, an Employment Contract often includes IP and confidentiality terms so it’s clear that work created in the course of employment belongs to the business - but note that ownership can still depend on the role, the circumstances, and the wording of the contract (so it’s worth getting the clause right).

For contractors, you’ll generally want an agreement that clearly addresses assignment and licences, because contractor arrangements are where IP disputes commonly appear.

Consider How This Fits With Your Broader Contract Suite

Your intellectual property clause is typically one part of a broader set of legal foundations. Depending on how your startup or SME is structured, you might also need documents like a Shareholders Agreement (to manage ownership and decision-making between founders) and a Company Constitution (rules for how the company operates).

These documents don’t replace an IP clause in your commercial contracts, but they often interact with IP strategy - particularly around who controls key assets and how value is protected as you grow.

Common Mistakes To Avoid When Drafting An Intellectual Property Clause

Even when a contract “has an IP clause”, it can still fail to protect you if it’s vague, inconsistent, or mismatched to the deal. Here are issues we commonly see growing businesses run into.

1. Using A Generic Clause That Doesn’t Match The Relationship

An IP clause for an outsourced software build is not the same as an IP clause for a marketing retainer, a joint venture, or a supplier arrangement.

If your clause doesn’t reflect what’s actually happening (and what you actually need), it can create a false sense of security.

2. Not Defining Deliverables Or Project IP Properly

“All IP created during the project is assigned” sounds fine until you realise the key deliverable wasn’t technically “created during the project” (or wasn’t included in the definition), or the contractor argues it’s their pre-existing framework.

Clear definitions prevent arguments later.

3. Forgetting Third-Party IP

If your website uses third-party plugins, fonts, or stock images, your contract should make it clear:

• what third-party components are included,
• who is responsible for licensing costs, and
• what limitations apply to your use.

If you don’t address this, you can end up with unexpected ongoing fees, licensing breaches, or restrictions that limit how you can scale or commercialise the asset.

4. Assuming You Automatically Own Work Created By Contractors

This is a big one. Many founders assume that if they paid for it, they own it.

In Australia, ownership can depend on the arrangement and the contract terms, which is why a clear IP assignment clause is so important when using contractors.

5. Ignoring Privacy And Data Issues When IP Includes Digital Assets

Sometimes what you’re “taking ownership” of includes customer data, mailing lists, analytics, and user content.

If your deliverables touch personal information (for example, an app, website, CRM integration, or marketing database), make sure your broader legal setup includes a properly drafted Privacy Policy and a clear understanding of who controls and can access that data.

This isn’t strictly an IP issue, but it often comes up in the same projects - and it’s much easier to deal with up front than after launch.

Key Takeaways

• An intellectual property clause is how your contract sets out who owns IP, who can use it, and what happens to IP when the relationship ends.
• Strong IP clauses usually separate Background IP (what each party already owns) from Project IP (what’s created during the engagement).
• If you’re paying for core business assets (like branding, content, code, or designs), you’ll often want an IP assignment so your business truly owns the deliverables.
• Licences still matter - especially where third-party tools, reusable templates, or embedded Background IP are involved.
• Practical details like source file handover, account access, and moral rights consents can be just as important as the legal wording.
• Getting your IP clause right early can prevent disputes and protect business value, particularly when raising funds, scaling, or selling.

If you’d like help drafting or reviewing an intellectual property clause for your startup or SME, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.