contracts
The Intellectual Property Ownership Clause: What It Means and How to Negotiate It (2026)
What is an intellectual property ownership clause? An intellectual property ownership clause decides who owns the intellectual property (IP) created, used or shared under a contract: copyrights, patents, trade marks, designs, trade secrets and know-how. It answers two different questions that people often confuse. First, who owns the background IP each party already had before the contract. Second, who owns the foreground IP created during the work. Getting this clause right is often more valuable than the fee, because IP ownership outlasts the project. It matters most in contracts where something is created: software development, design and creative work, research and development, consultancy, joint ventures and employment. The default position depends on the law and the relationship, and it is often not what people assume. A customer who pays a contractor to build software does not automatically own the code in every jurisdiction; without a clear assignment, the contractor may keep ownership and the customer may have only a licence. This article is general guidance, not legal advice. The law here varies by jurisdiction and changes over time, so have a qualified lawyer review any agreement before you rely on it. ## Sample intellectual property ownership wording ```
INTELLECTUAL PROPERTY 1. BACKGROUND IP Each party keeps ownership of all intellectual property it owned before this Agreement or develops outside it ("Background IP"). Neither party gains rights in the other's Background IP except the licences expressly granted here. 2. FOREGROUND IP All intellectual property created by the [Supplier] in performing the Services and delivered to the [Customer] as a Deliverable ("Foreground IP") will, on creation [or on full payment], belong to the [Customer]. The [Supplier] assigns to the [Customer] all such rights, present and future, including copyright, with full title guarantee. 3. LICENCE OF BACKGROUND IP To the extent any Background IP of the [Supplier] is embedded in a Deliverable, the [Supplier] grants the [Customer] a non-exclusive, perpetual, irrevocable, royalty-free, worldwide licence to use it as part of the Deliverable. 4. MORAL RIGHTS AND FURTHER ACTS The [Supplier] will, at the [Customer's] cost, do what is reasonably needed to perfect the [Customer's] ownership (for example sign assignments), and [waives / procures the waiver of] moral rights so far as the law allows. 5. THIRD-PARTY AND OPEN-SOURCE MATERIAL The [Supplier] will identify any third-party or open-source material in a Deliverable and ensure the [Customer] has the rights to use it. The [Supplier] will not include open-source components whose licence would require the [Customer] to disclose its own code without consent. 6. WARRANTY AND INDEMNITY The [Supplier] warrants the Deliverables do not infringe a third party's IP, and indemnifies the [Customer] against IP infringement claims arising from the Deliverables, subject to clause [liability].
- **Assignment of future rights (clause 2).** Note "present and future." In some jurisdictions you cannot assign copyright in a work that does not exist yet without specific wording, so a present assignment of future rights, or an obligation to assign on creation, is used.
- **"On full payment" (clause 2).** Suppliers often want ownership to pass only when they are paid, so unpaid work does not transfer. Customers prefer ownership on creation. This is a common negotiation point.
- **Background licence (clause 3).** Even when the customer owns the deliverable, the supplier's pre-existing tools or libraries inside it stay the supplier's. The customer needs a licence broad enough to use the deliverable fully, or it owns a thing it cannot properly use.
- **Moral rights and further acts (clause 4).** Moral rights (such as the right to be identified as author) cannot always be assigned, so they are waived where the law allows. The "further acts" duty makes the supplier sign whatever is needed to perfect title.
- **Open source (clause 5).** A critical practical risk in software. Some open-source licences can require disclosure of combined code. A good clause makes the supplier disclose and control open-source use.
- **Warranty and indemnity (clause 6).** The customer wants a promise the work does not infringe, backed by an indemnity for infringement claims. ## How to negotiate an intellectual property ownership clause - **If you are the customer paying for creation:** insist on a clear assignment of foreground IP (ideally on creation), a broad licence to any embedded background IP, an open-source control clause, and an IP warranty and indemnity. Make sure the assignment covers copyright, future rights and the duty to sign further documents.
- **If you are the supplier:** keep your background IP and reusable tools, methods and know-how clearly carved out so you can reuse them for other clients; consider passing ownership only on full payment; grant the customer a licence rather than ownership where that is enough; and keep your indemnity capped and tied to the liability clause.
- **Both sides:** separate background from foreground explicitly, address open-source and third-party material head-on, and match the IP warranty and indemnity to the overall liability cap. For jointly created IP, decide ownership and each side's right to exploit it, because joint ownership rules differ by country and can block either side from using the IP freely. ## A note on jurisdiction IP law is territorial, and ownership defaults differ. In India, the Copyright Act, 1957 governs copyright (including the first-ownership rules for commissioned work and works made in employment), the Patents Act, 1970 governs patents, and the Trade Marks Act, 1999 and the Designs Act, 2000 cover marks and designs; an assignment of copyright generally must be in writing and signed. In the United States the "work made for hire" doctrine can make an employer or, in limited categories, a commissioning party the author, but for an independent contractor outside those categories a written assignment is needed. The UK, Ireland, Singapore and Australia each have their own first-ownership and moral-rights rules. Because the default owner of commissioned work, the treatment of moral rights and the formalities of assignment all vary across IN, UK, IE, SG, AU and the US, treat ownership of created IP as something to set expressly in the contract and confirm under the governing law. ## Where a contract workspace helps Understanding the clause is one thing; keeping IP ownership consistent across every contract you sign is another. The ongoing work starts after signing: keeping terms consistent across many versions and counterparties, checking each draft for weak or missing terms before you sign, remembering key dates and obligations, and keeping versions straight as the deal changes. Drafting the assignment, licence and indemnity, reviewing the background and foreground IP split, and tracking the warranties that back it can all sit in one AI contract workspace tuned to how your company handles intellectual property. [Adira](https://adiralaw.com) is designed along those single-workspace lines. The explainer above is enough to read an IP ownership clause with care.
Frequently asked questions
- Who owns intellectual property created by a contractor if the contract is silent?
- It depends on the jurisdiction and the type of IP, and it is often not the customer. Without a clear written assignment, an independent contractor may keep ownership of what they create, leaving the paying customer with only an implied licence. Ownership defaults for commissioned work differ across countries, which is exactly why a clear assignment clause matters rather than relying on the default.
- What is the difference between background IP and foreground IP?
- Background IP is what each party already owned before the contract or develops outside it, such as a supplier's existing tools and libraries. Foreground IP is what is created during the work under the contract. A good clause lets each party keep its background IP, assigns the foreground IP to whoever the parties agree, and grants a licence to any background IP embedded in the deliverable.
- Why does open-source software matter in an IP ownership clause?
- If a supplier builds open-source components into a deliverable, the open-source licence terms travel with it. Some licences can require that combined or derivative code be made available under the same terms, which may force disclosure of code the customer wanted to keep private. A good clause makes the supplier identify open-source use, control it, and ensure the customer has the rights it needs.
Sources
See how Adira drafts in your voice and reads contracts from your side.
Explore the showroomWorking through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.
Try Weave — free