Learning / Commercial foundations

IP Ownership and Licensing for Software Projects

Agree on rights before the product grows.

A product can contain code, designs, copy, brand assets, data and tools created by several parties. Clear rights let the people building and operating it know what they may use, change, publish and pass on.

Read the guide

At a glance

  1. Separate existing IP from new project work
  2. Choose ownership and use rights deliberately
  3. Record third-party and open-source conditions

Identify three kinds of material

Background IP exists before or outside the engagement: a client's brand assets, a consultant's reusable framework or a previous research method. Project IP is created during the work. Third-party IP belongs to someone else, such as a stock-image owner, font foundry or software-library author.

List important inputs before work starts. Note who owns each item, what permission the project needs and whether the final product can continue using it after the engagement ends. IP Australia recommends dealing with background, project and third-party IP in the collaboration agreement.

Choose ownership of new work

In Australia, a contractor generally owns the IP they create unless the contract says otherwise; employee-created IP has different starting rules. A client who needs to own a deliverable should have that expressed in a written agreement, including which deliverables transfer and when.

Assignment transfers ownership. A licence grants permission to use IP while ownership stays with the owner. A project may use both: ownership of bespoke final assets for the client, with a licence to use pre-existing tools that make those assets work. The exact split depends on the material and the deal.

Make a licence specific enough to use

IP Australia describes exclusive, sole and non-exclusive licences. Discuss the permitted use, territory, duration, payment, right to modify, right to sublicense, attribution and what happens when the relationship ends. Broad exclusivity can limit the owner's future work, so it deserves careful pricing and legal review.

For co-created products, decide who may maintain the code, license to others, use learnings in future work and approve a sale or pivot. Joint ownership can make later decisions difficult if the agreement does not say how consent and returns work.

  • Assignment: transfer ownership of defined work on agreed conditions.
  • Exclusive licence: one licensee receives the agreed commercial rights, subject to stated limits.
  • Sole licence: one licensee and the owner can use the IP within the agreed scope.
  • Non-exclusive licence: the owner may permit multiple users within the agreed scope.

Track the things neither party owns

External fonts, imagery, datasets, software packages and services have their own terms. Keep a simple register of where each came from, its licence, attribution needs and any distribution limits. Open-source software can be highly useful, but its licence terms still need to be checked before release.

At handover, give the operator the records and access needed to run the product, while respecting any third-party restrictions. A source-code repository transfer alone does not settle the rights to all its contents.

The clearest starting question is: who needs to do what with each asset after the project, and what permission makes that possible?

External project website

Open this project site?

is hosted at . It will open in a new tab.