Sublicense Clause

TL;DR: A sublicense clause governs whether and how a licensee may grant some or all of its rights under a license to a third party (the sublicensee). The clause specifies who may receive a sublicense (anyone, only affiliates, or only with consent), what rights may be sublicensed, what flow-down terms must apply, what happens to sublicenses if the head license terminates, and how royalties on sublicensee revenue flow back to the head licensor. Without an explicit sublicense right, most jurisdictions presume the licensee cannot sublicense.

‍

What Is a Sublicense Clause?

A sublicense is a license granted by a licensee to a third party under rights that the licensee itself received from the original licensor. The sublicense clause is the operative provision in the head license that defines whether sublicensing is permitted at all and, if so, on what conditions. It sits in the same architectural layer as the license grant clause, but it governs a transitive relationship: the head licensor's rights, the licensee's rights, and the sublicensee's rights all need to align.

The default rule in US patent and copyright law is that a licensee cannot sublicense without express authorization. The leading case In re CFLC, Inc. (Everex Systems v. Cadtrak Corp., 9th Cir. 1996) held that patent licenses are personal and non-assignable absent express consent, and the same general principle applies to copyright licenses. UK and EU jurisdictions follow similar defaults. This means a license that is silent on sublicensing leaves the licensee unable to grant rights to its customers, contract manufacturers, or affiliates, often with serious operational consequences discovered late.

When sublicensing is permitted, the head license must address several key questions. First, scope: can the licensee sublicense all of its rights or only a subset? Second, identity restrictions: any third party, only affiliates, only named approved sublicensees, or anyone subject to licensor consent? Third, flow-down: which terms of the head license must appear in every sublicense (most commonly confidentiality, IP ownership, audit, and reporting)? Fourth, financial terms: does the head licensor receive a share of sublicensee royalties, and if so, at what rate? Fifth, survival on termination: if the head license terminates, do existing sublicenses fail with it, survive automatically, or convert to direct licenses with the head licensor?

Sublicensing matters most in patent licensing (where licensees often sublicense to affiliates and contract manufacturers), university tech-transfer (where startups license university IP and then build sublicensee networks), and enterprise software (where master partners sublicense to end customers). It matters least in pure end-user software licenses, which typically prohibit sublicensing outright.

‍

Why It Matters

• Operational flexibility: A licensee that cannot sublicense to its affiliates must enter into separate licenses for each subsidiary, often facing renewed negotiation, audit, and consent requirements. Affiliate sublicensing rights are nearly universal in commercial license agreements as a result.
• Royalty leakage and gaming: Without a sublicensee royalty pass-through, the head licensee can grant sublicenses at low or zero royalty (perhaps to affiliated entities) while keeping the value capture upstream. Head licensors typically negotiate either a flat percentage of sublicensee revenue or a most-favored-nation rate.
• Quality control for trademarks: Trademark licenses with sublicensing rights are particularly sensitive. The trademark owner must control quality through every layer; if the sublicensee operates outside the brand standards, the entire mark can be deemed abandoned.
• Survival on termination: A sublicensee whose rights terminate when the head license terminates faces a sudden cliff. Banks financing sublicensees, and the sublicensees themselves, push hard for survival language so that termination of the head license converts the sublicense into a direct license with the head licensor.
• Field of use and territory enforcement: Sublicenses cannot exceed the head license. If the head license is limited to oncology in the US, no sublicense can authorize the sublicensee to commercialize in cardiology or in Europe. Head licensors regularly audit sublicenses for scope creep.
• Bankruptcy implications: Under 11 U.S.C. § 365(n), if the licensor enters bankruptcy and rejects the head license, the licensee retains rights but only as to existing sublicenses, not new ones. Long-term financing structures depend on this provision.

‍

Key Elements of a Well-Drafted Sublicense Clause

1. Permission scope: State whether sublicensing is permitted (with or without consent), permitted only to affiliates, permitted to named third parties, or prohibited. "With prior written consent of Licensor, not to be unreasonably withheld" is the most common compromise.
2. Affiliate carve-outs: Most license agreements treat sublicenses to affiliates as automatic or notice-only, while sublicenses to non-affiliates require consent. Define "Affiliate" precisely to address tiered ownership and joint ventures.
3. Flow-down terms: Specify which provisions of the head license must appear in every sublicense. Common minimum set: scope, exclusivity, territory, field of use, IP ownership, confidentiality, audit, reporting, and termination triggers.
4. Sublicensee royalty: If the head licensor receives a share of sublicensee revenue, state the percentage (often 25 to 50 percent of net sublicensee royalties), the calculation method, and whether the head license royalty rate is reduced when sublicensee royalties apply.
5. Sublicense reporting: Require the licensee to deliver a copy of each sublicense to the licensor (with permitted redactions for unrelated commercial terms) within a specified period.
6. Survival on termination: State whether existing sublicenses (a) terminate automatically with the head license, (b) survive but convert into direct licenses with the head licensor, or (c) survive only if the sublicensee is in good standing and pays the head licensor directly.
7. Sublicensee compliance: Require the licensee to enforce sublicensee compliance and remain liable to the licensor for any sublicensee breach. Without this, the licensor must chase the sublicensee directly.
8. Sub-sub-licensing: State whether multi-tier sublicensing is permitted. Many agreements permit only one tier (licensee to sublicensee) and prohibit sub-sublicensing.

‍

Market Position & Benchmarks

Where Does Your Clause Fall?

• Licensor-Favorable: Sublicensing prohibited or only to wholly-owned affiliates with prior written consent. All sublicensee revenue flows back to licensor at the head license royalty rate. Sublicenses terminate immediately on head license termination with no survival.
• Market Standard: Sublicensing permitted to affiliates with notice and to non-affiliates with prior written consent (not to be unreasonably withheld). Flow-down of all material head license terms. Sublicensee royalties paid at 25 to 35 percent of net sublicensee revenue. Survival of sublicenses on head license termination if sublicensee assumes head license obligations directly with licensor.
• Licensee-Favorable: Unrestricted right to sublicense through multiple tiers, including to competitors of licensor. No sublicensee royalty pass-through. All sublicenses survive head license termination as direct licenses with head licensor at the sublicense terms.

Market Data

• The Licensing Executives Society's 2024 license benchmarking survey found that approximately 88 percent of patent license agreements include some sublicensing right, but only 22 percent permit unrestricted sublicensing without consent.
• The most common sublicensee royalty share to head licensor is 30 percent of net sublicensee revenue, with a range of 20 to 50 percent representing the middle 80 percent of agreements.
• Approximately 70 percent of university tech-transfer licenses include sublicense survival language that converts existing sublicenses into direct licenses with the university upon head license termination.
• A 2024 IP litigation survey reported that sublicensing scope disputes accounted for roughly 15 percent of all license-related litigation, second only to royalty calculation disputes.
• Software license agreements show the lowest sublicensing rate (only 12 percent permit any form of sublicensing), reflecting the typical end-user model. SaaS reseller and OEM agreements are the major exceptions.
• Recent enforcement trends show head licensors auditing sublicense agreements approximately every 18 to 24 months to verify scope and royalty compliance, up from every 36 to 48 months a decade ago.

Sample Language by Position

Licensor-Favorable: "Licensee may not sublicense any of its rights under this Agreement, in whole or in part, to any third party (including any Affiliate) without Licensor's prior written consent, which Licensor may withhold in its sole and absolute discretion. Any purported sublicense without such consent shall be void and shall constitute a material breach of this Agreement."

Market Standard: "Licensee may sublicense its rights under Section 2.1 (a) to its Affiliates with prior written notice to Licensor and (b) to non-Affiliate third parties with Licensor's prior written consent (such consent not to be unreasonably withheld, conditioned, or delayed). Each sublicense shall be in writing and shall include flow-down provisions consistent with this Agreement, including without limitation the provisions on confidentiality, IP ownership, audit, and termination. Licensee shall provide Licensor with a copy of each executed sublicense (subject to redaction of unrelated commercial terms) within 30 days. Licensee shall pay to Licensor 30 percent of all Sublicense Revenue within 45 days after the close of each calendar quarter."

Licensee-Favorable: "Licensee may freely sublicense any or all of its rights under this Agreement, through multiple tiers, to any third party without notice to or consent of Licensor. No share of Sublicense Revenue shall be payable to Licensor; the Royalty payable under Section 4.1 shall be the only consideration owed to Licensor in respect of any Sublicensee. Upon any termination or expiration of this Agreement other than for Licensee's uncured material breach, all existing sublicenses shall automatically convert into direct licenses with Licensor on the same terms as the applicable sublicense."

‍

Example Clause Language

Tech-transfer license with sublicense survival pivotal for sublicensee financing:

University Tech-Transfer with Survival: "Licensee may grant Sublicenses under the Licensed Patents to its Affiliates and to bona fide third-party commercial partners on terms consistent with this Agreement. Each Sublicense shall name Licensor as a third-party beneficiary entitled to enforce flow-down provisions directly. Upon any termination of this Agreement, each existing Sublicense, if the Sublicensee is then in compliance with its terms, shall automatically convert into a direct license between Licensor and Sublicensee on the same terms (other than payments, which shall be paid directly to Licensor at the Royalty rates in this Agreement)."

OEM software license with limited sublicense to end customers:

OEM Sublicense to End Customers: "Distributor may grant non-transferable, non-sublicensable end-user licenses to its End Customers solely as embedded within Distributor's products and only on terms substantially equivalent to Licensor's then-current End User License Agreement. Distributor may not grant any other sublicense, redistribute the Software in stand-alone form, or otherwise transfer rights under this Agreement."

Affiliate-only sublicense with structural limits:

Affiliate-Only Sublicense: "Licensee may grant sublicenses under this Agreement only to its Affiliates that are direct or indirect wholly-owned subsidiaries of Licensee. Each such Affiliate sublicense shall terminate automatically when the Affiliate ceases to be a wholly-owned subsidiary. Licensee shall remain primarily liable for performance of all sublicensee obligations."

‍

Common Contract Types

• Patent license agreements: The classic home of sublicensing clauses, especially for early-stage technology that the licensee plans to commercialize through partners or contract manufacturers.
• University tech-transfer licenses: Heavily reliant on sublicensing because spin-out startups need to grant rights to investors, manufacturing partners, and downstream customers.
• OEM and reseller agreements: The OEM or reseller takes a license that includes the right to sublicense to its own end customers, typically through a flow-down EULA.
• SaaS partner programs: Master agreements with channel partners often include limited sublicensing rights for the partner to provision SaaS access to its end customers.
• Trademark license agreements: Sublicensing requires careful quality control flow-downs; naked licensing risk applies to sublicensees as well.
• Know-how and trade-secret licenses: Sublicensing introduces additional confidentiality risk because each sublicensee is a new exposure point for the trade secret.
• Franchise agreements: A specialized form of sublicensing under federal franchise rules and state franchise statutes, with extensive disclosure and registration obligations.
• Open-source compliance agreements: Most open-source licenses (MIT, Apache 2.0, GPL) include their own sublicense terms; commercial agreements layered on top must respect those.

‍

Negotiation Playbook

Key Drafting Notes

• Distinguish sublicensing from assignment: A sublicense creates a new permission for a third party while the head licensee remains in place. An assignment transfers the licensee's entire interest to a successor. The two are governed separately, often by separate clauses.
• Define affiliate precisely: Common definitions cover entities under 50 percent or greater common ownership, but joint ventures, licensees with minority stakes, and acquired entities all create edge cases that should be addressed by formula or by named exclusions.
• Flow-down with care: Listing every head license term as a flow-down requirement is unrealistic; sublicensees would never sign. The minimum flow-down should cover IP ownership, confidentiality, scope, audit, and termination. Negotiable items (royalty rate, exclusivity terms) typically vary between head and sublicense.
• Address sublicensee net sales calculation: If the head license royalty is based on "net sales," sublicensee royalty pass-throughs need to clarify whether the licensor gets a share of sublicensee net sales or sublicensee royalty receipts. The two can differ by an order of magnitude.
• Survival mechanics need detail: If sublicenses survive head license termination, specify how royalties flow, who handles audits, and what reps and warranties apply going forward. Loose survival language has triggered substantial post-termination litigation.
• Coordinate with consent rights: If sublicensing requires consent, the contract should specify the consent process (timeline, documents to be provided, deemed consent if licensor does not respond). Otherwise consent disputes can stall sublicensee transactions for months.

Common Pitfalls

• Silence on sublicensing: A license silent on sublicensing typically prohibits it under default rules. Licensees who assume otherwise often discover the gap when a major customer refuses to accept a sublicense.
• Over-broad flow-down language: Requiring every sublicense to include "all terms of this Agreement" makes sublicensing impractical. Tighten to specific listed sections.
• Royalty pass-through ambiguity: A clause requiring "a fair share of sublicensee revenue" without a specified percentage invites litigation. State the percentage and the basis (revenue versus net sales versus royalty receipts).
• Failure to address sub-sub-licensing: Multi-tier sublicensing creates compounding compliance risk. Most head licenses limit sublicensing to one tier; allow further tiers only with explicit drafting and enhanced flow-down.
• Termination without notice to sublicensee: If the head license terminates and sublicenses fall with it, sublicensees should receive notice and a reasonable wind-down period. Without it, the head licensor faces tort claims from blindsided sublicensees.
• Naked licensing in trademark sublicenses: A trademark license with broad sublicensing rights but weak quality controls invites abandonment. The Lanham Act and recent cases (e.g., Eva's Bridal) make sublicensee quality control mandatory.

‍

Jurisdiction Notes

• U.S.: Federal IP law sets the default. Patents (35 U.S.C. § 261) and copyrights (17 U.S.C. § 204) require written transfers; sublicenses must be express. Trademark sublicenses require quality control under Lanham Act principles. Bankruptcy treatment under 11 U.S.C. § 365(n) protects existing sublicensees if the licensor rejects the head license. Courts in the Federal Circuit have held that an exclusive licensee with the right to sublicense holds "all substantial rights" and may sue for infringement, while a non-exclusive sublicense rarely confers standing.
• U.K.: Patents Act 1977 § 30 permits sublicensing if expressly authorized. Trade Marks Act 1994 § 28(4) requires registration of exclusive sublicenses to bind successors. Courts apply the Belize Telecom test for implied terms, occasionally finding implied sublicense rights in commercial agreements where context demands them.
• Other: EU Technology Transfer Block Exemption (Regulation 316/2014) limits restrictive sublicense terms (e.g., resale price maintenance, exclusive grant-backs of severable improvements). China's Patent Law (2020) and Civil Code (2021) require recordation of sublicenses with CNIPA for enforceability against third parties.

‍

Related Clauses

• License Grant Clause - the head clause from which sublicensing rights flow.
• Royalty Clause - the financial counterpart that often includes sublicensee royalty pass-through provisions.
• IP Clause - the umbrella IP allocation provision.
• Assignment Clause - distinguishes between sublicensing (rights only) and assignment (entire interest).
• Audit Clause - lets the head licensor verify sublicensee compliance and royalty reporting.
• Confidentiality - flow-down obligation that protects know-how passed through to sublicensees.
• Compliance with Laws - flow-down obligation often required to address export control and anti-bribery compliance.
• Successors and Assigns - addresses what happens to sublicenses on a corporate change of control.

‍

This glossary entry is provided for informational and educational purposes only. It does not constitute legal advice, and no attorney-client relationship is formed by reading this content. Consult qualified legal counsel for advice on specific contract matters.