Why the background IP license back clause decides your options

Dual sourcing fails at the IP clause more often than at the tooling clause. What a supply agreement has to say for a second source to be possible at all.

What does a background IP license-back clause do in a supply agreement?

It gives the buyer a defined right to use the supplier’s pre-existing intellectual property to the extent necessary to make, or have made, the supplied part. Without it, a buyer may own the drawings, the tooling and any jointly developed improvements and still be unable to produce the part elsewhere, because manufacturing it practises supplier process knowledge the buyer has no licence to use. The clause needs a defined scope, a trigger or standing grant, a sublicensing right so a third-party manufacturer can rely on it, and a term that survives expiry and termination.

Last updated: October 6, 2026 · Reviewed by the Aavenir Manufacturing practice

Key takeaways

  • ✓Owning drawings and tooling is not the same as having the right to make the part somewhere else.
  • ✓Background and foreground IP need separate definitions, or improvements become disputed by default.
  • ✓A license-back without a sublicensing right cannot be used by a contract manufacturer, which defeats its purpose.
  • ✓The licence has to survive termination, including termination for the buyer’s breach, or it fails exactly when needed.

Dual sourcing is a standard resilience requirement and a standard board commitment. It is also, frequently, undeliverable, and the reason is rarely capacity. It is that the agreement with the incumbent supplier never gave the buyer the right to have the part made by anyone else, and nobody discovered that until the second source programme was already funded.

The confusion usually comes from a reasonable assumption. The buyer owns the product design, paid for the tooling, holds the drawings and has a clause assigning improvements. That feels like control. What it omits is the supplier’s background process knowledge, which is what turns a drawing and a tool into a conforming part, and which the supplier has every commercial reason to keep.

This guide covers how background and foreground intellectual property should be separated in a supply agreement, what a usable license-back actually contains, and how to hold the resulting terms so that a sourcing team can answer the dual-source question from a field rather than from a legal review.

The five IP terms that decide sourcing flexibility

These five appear in most supply agreements in some form. The gap is usually not that they are absent but that they are drafted without reference to each other, so the combination does not deliver what any individual clause implies.

  • Background IP definition, what each party brings, with a record of the specific technology contributed where joint development is contemplated.
  • Foreground IP ownership, who owns what is created during performance, with joint ownership avoided in favour of allocation plus a broad licence.
  • The license-back grant, scope, field of use, whether standing or triggered, and critically whether it includes a have made and sublicensing right.
  • Technical information access, the drawings, parameters, process documentation and quality methods needed to make the licence exercisable in practice.
  • Survival and assignment, whether the licence survives expiry and termination, including for buyer breach, and whether it binds a transferee of the supplier’s IP.

A sourcing team reading those five together can tell you whether a second source is possible. A sourcing team reading only the tooling clause cannot, which is how programmes get approved on the strength of an asset ownership statement that does not answer the question.

The have made right is the one that matters

A licence permitting the buyer to make the part, without a have made or sublicensing right, is unusable for its main purpose, because almost no buyer intends to manufacture the part itself. It intends to appoint a contract manufacturer. Suppliers will often concede a have made right bounded by field of use more readily than they will widen the scope, so this is usually an achievable negotiation if it is raised deliberately rather than at the end.

Making the terms operational

IP clauses are static text, but the information needed to rely on them is not. Four or five practices keep the position usable across a supply base of thousands of parts.

  • Hold the IP position as fields per agreement. Foreground ownership, licence present, scope, have made right, survival and assignment binding, recorded as structured values rather than left in the document
  • Link the position to the part, not just the supplier. Sourcing decisions are made at part level. Mapping the IP position through to the part numbers covered is what makes the data usable in a resilience review
  • Track technical information deposits. Where the agreement requires process documentation to be deposited or made available, treat it as an obligation with a due date and an artefact, not a standing promise
  • Review on supplier change of control. A supplier acquisition is the event that tests the assignment and survival terms. Make it a trigger for review rather than discovering the position later
  • Record background IP contributions at project start. For joint development, capture what each party contributed when it is still known. This single record prevents the most intractable category of later dispute

A five-step roadmap for closing the dual-source gap

Step 1, identify the single-source critical parts

Start from the parts where a supply failure would stop production or breach a customer commitment, and where only one supplier is currently qualified. This is usually a short list relative to the supply base, which makes the rest of the exercise tractable.

Step 2, read the five IP terms for each

For every agreement covering those parts, record foreground ownership, whether a license-back exists, its scope, whether it carries a have made right, and whether it survives termination and binds assignees. Expect a significant proportion to fail on one of the last two.

Step 3, fix the template and the negotiation position

Update the standard supply agreement so the five terms are drafted as a set, and give reviewers a clear minimum position on each. The have made right and survival are the two that should not be conceded quietly for commercial expedience.

Step 4, remediate by criticality, using commercial moments

Amendments to IP terms are hard to obtain mid-term and much easier at renewal, price negotiation or new programme award. Keep the required language ready so it can be introduced when a commercial moment opens rather than as a standalone request.

Step 5, record the position where sourcing can see it

Put the resulting IP position on the part and supplier record so a resilience review can be answered from data. The value of this work is lost if the answer still requires a lawyer to read an agreement each time the question is asked.

Answer the dual-source question from data

Aavenir holds IP ownership, licence scope, have made rights and survival terms as fields on the supplier agreement and the parts it covers.

Book a demo

Where the gap usually gets discovered

Three moments expose it. A supply disruption, when the buyer tries to qualify an alternative and finds it cannot lawfully use the process knowledge required. A supplier insolvency, when the tooling can be recovered but the know-how cannot. And a supplier acquisition, where a new owner takes a different view of an obligation that was never clearly binding on assignees. In each case the remedy available afterwards is negotiation from a weak position, which is expensive and slow. Manufacturers that already track supplier quality and PPAP commitments have the record structure to hold the IP position alongside them.

IP term, risk if absent and what to record

The table pairs each term with the exposure it creates when missing and the value worth holding as data. The right-hand column is what a sourcing or resilience review should be able to query.

IP termRisk if absentField to holdReview trigger
Background IP definitionImprovement ownership disputedDefined or undefinedNew development project
Foreground ownershipBuyer cannot use its own design freelyBuyer, supplier or jointProgramme award
License-back grantSecond source legally impossiblePresent, scope, field of useResilience review
Have made rightOnly buyer could manufactureYes or noResilience review
Survival and assignmentLicence lost on termination or saleSurvives, binds assigneesSupplier change of control

The practical lesson is that resilience commitments should be tested against the IP clause before they are made, not after. A dual-sourcing programme approved on the basis of tooling ownership can fail entirely at the licence, and the failure appears late, after qualification work has been funded. Reading five terms as a set, holding the answers as fields on the part record, and introducing the required language at commercial moments rather than as isolated requests turns this from a recurring surprise into a known position. Manufacturers running broader obligation management for manufacturing already have somewhere to put it.

For related guidance, see Price adjustment clauses in direct material contracts, ESG and supply chain due diligence clause tracking and Incoterms, title and risk in supply contracts.

FAQ

Supply agreement IP questions, answered

What is the difference between background and foreground IP? +
Background IP is what each party brings to the relationship, developed before it or independently of it. Foreground IP is created in the course of performing the agreement, whether by one party or jointly. The distinction matters because the commercial instinct differs: buyers generally expect to own foreground IP relating to their product, while suppliers reasonably expect to keep background process knowledge. Agreements that use a single undefined term for both produce disputes about improvements.
Why is owning the tooling not enough? +
Tooling is a physical asset. Making a part from that tooling may still require supplier process knowledge, including parameters, sequences, treatments and quality methods that are not embodied in the tool or the drawing. A buyer that owns the tool, collects it and ships it to a second source can find the second source unable to produce a conforming part, or able to do so only by independently developing process knowledge the original supplier already holds and has not licensed.
What scope should the license-back have? +
Narrow enough that the supplier will agree, broad enough to be useful. A workable formulation covers the right to make, have made, use and sell the specific supplied parts and their direct derivatives, limited to that purpose, with no right to use the licensed technology for other products. Field of use and product limitations are the normal way to bound it. What should not be negotiated away is the have made right, since that is what makes a third-party manufacturer possible.
Should the licence be standing or triggered? +
Triggered licences are easier to agree and harder to rely on, because the trigger definition becomes the argument. Common triggers include supplier insolvency, failure to supply for a defined period, repeated quality failure and end of life. If a triggered structure is unavoidable, define the triggers objectively and include a short determination process. A standing licence limited to exercise only on those events achieves a similar result with less room for dispute.
What makes a license-back unusable in practice? +
Four omissions. No sublicensing or have made right, so only the buyer itself could manufacture. No survival clause, so the licence dies with the agreement. No access to the technical information needed to exercise it, which leaves a legal right with no practical content. And no limitation on the supplier’s ability to assign its IP free of the licence, which can strand the buyer after a supplier acquisition.
How does this interact with joint development work? +
Joint development multiplies the complexity, because foreground IP may be genuinely joint and each party’s background IP may be embedded in the result. The practical approach is to avoid joint ownership where possible, allocating foreground IP to one party with a broad licence to the other, and to record each party’s contributed background IP at project start. Reconstructing who brought what, years later, is close to impossible.

Make IP terms visible across the supply base

See how Aavenir holds IP ownership, licence scope, sublicensing and survival terms as fields on the supplier agreement, so sourcing options are known before they are needed.

  • ✓IP and licence terms as searchable fields per part
  • ✓Tooling and survival duties tracked with owners
  • ✓Standalone or native on ServiceNow