License Grant Clause: The Dials of Scope (Exclusivity, Territory, Field, Term, Sublicense)

A license grant clause gives one party the right to use another's intellectual property without transferring ownership. Its entire value lives in the scope dials: whether the license is exclusive, where it applies (territory), what uses are allowed (field of use), how long it lasts (term), whether it can be passed down (sublicense), and whether it can be sold or moved (transferability). Get one dial wrong and you either pay for rights you cannot use or give away rights you meant to keep.

Reviewed and corrected on 12 October 2026. This is general information, not legal advice; check the cited statute or opinion before relying on it.

TL;DR

• A license grant transfers a right to use, not ownership. Every word of the grant either widens or narrows what the licensee can do.
• Six dials set the value: exclusivity, territory, field of use, term, sublicense rights, and transferability. Read each one; a license is exactly as broad as its narrowest dial.
• Exclusive, sole, and non-exclusive are used as three different things, but usage varies, so define each one in the grant. In common drafting usage, exclusive can lock out the licensor itself; sole lets the licensor keep using the IP but grant no one else.
• Sublicense and assignment rights decide whether the license survives a sale or can be pushed down to affiliates and customers. Silence often defaults against the licensee: courts read copyright licenses to prohibit uses not authorized, and in some circuits federal common law presumes a patent or copyright license cannot be transferred without consent (see the jurisdiction notes).
• Read the grant with the IP, assignment, and change of control clauses. A license that cannot move with a corporate transaction can quietly die in an acquisition.

What a license grant clause actually does

The clause defines a permission and its limits. The grant sentence does most of the work, and each modifier is a dial you can turn.

1. The grant verb and rights. What the licensee may do: use, copy, modify, distribute, display, perform, make, sell. A license to "use" software is narrower than one to "use, modify, and distribute" it.

2. Exclusivity. Whether others can hold the same right. Non-exclusive lets the licensor grant the same rights to many. Sole means only the licensee and the licensor. Exclusive means only the licensee, sometimes locking out even the licensor. These labels are drafting conventions, not fixed legal categories, so define them in the grant.

3. Territory and field of use. Where the license applies (a country, a region, worldwide) and for what purpose (internal use, a specific product, a specific market). A narrow field is how a licensor licenses the same IP to different industries.

4. Term, sublicense, and transferability. How long the right lasts, whether the licensee can grant rights to others (sublicense), and whether the license itself can be assigned or moved.

Why it matters: the dollars at stake

Picture a company (the licensee) that pays $250,000 a year to license a data analytics engine to embed in its own product, which it sells to enterprise customers.

Here is the example math on how the scope dials decide whether that money buys a usable right.

• With a grant to "use the Software for Licensee's internal business purposes," the licensee cannot embed the engine in a product it sells. The field of use is internal only. The $250,000 bought the wrong license.
• With a grant to "use, reproduce, and incorporate the Software into Licensee's Products and distribute it to End Users, with the right to sublicense to End Users," the license actually covers the business model.
• Now the licensee is acquired. If the deal is a merger that moves the license to a different entity, the grant is "non-transferable" and there is no change-of-control carve-out, the license may not survive, and the acquirer may inherit a product it cannot lawfully ship. A stock purchase that leaves the licensee as the contracting party is a different case (see the jurisdiction notes).

Same IP, same fee. Whether the license fits the business and survives a transaction comes down to the field-of-use, sublicense, and transferability dials. That is why in-house counsel map the dials against the actual use case before signing.

Who wants what

The pattern: the licensee wants the widest grant that fits its business and survives change; the licensor wants the narrowest grant that still closes the deal so it can license the same IP elsewhere.

Market-standard language

A typical license grant for embedded software reads close to this:

LICENSE GRANT.

(a) Grant. Subject to the terms of this Agreement and Licensee's payment
of all fees, Licensor grants Licensee a non-exclusive, worldwide,
non-transferable (except as provided in Section [Assignment]) license,
during the Term, to use, reproduce, and incorporate the Software into
Licensee's Products and to distribute the Software, in object code form
only, as embedded in Licensee's Products to End Users.

(b) Sublicense. Licensee may sublicense the rights in (a) to its End Users
solely through an end-user license agreement no less protective of Licensor
than this Agreement, and to its Affiliates for use consistent with this
Agreement. Licensee remains responsible for its sublicensees' compliance.

(c) Restrictions. Licensee will not (i) use the Software outside the scope
granted; (ii) decompile or reverse engineer the Software except as
permitted by law; or (iii) remove any proprietary notices.

(d) Reservation. Licensor reserves all rights not expressly granted. No
rights are granted by implication or estoppel.

Read subsection (a) as a sentence of dials: non-exclusive (exclusivity), worldwide (territory), incorporate into Products and distribute to End Users (field of use), during the Term (term), non-transferable except as provided (transferability), object code only (form). Change any one and the deal changes.

The negotiation: standard, fallback, walk-away

The standard compromise on exclusivity is a narrow exclusive (exclusive only in the licensee's defined field or territory) for a premium, leaving the licensor free to license other fields. The standard compromise on transferability is non-transferable in general, with a carve-out allowing assignment in a merger or sale to a non-competitor.

Common carve-outs and variations

The variations that change how the grant behaves:

• Sole versus exclusive. In common drafting usage, a sole license lets the licensor keep using the IP itself but grant it to no one else, and an exclusive license can be drafted to exclude even the licensor. That is a convention, not a rule of law, and we did not find a case fixing the meanings. If you are paying for exclusivity, write out which one you are getting and whether the licensor keeps any right to use the IP.
• Affiliate use. Licensees often want their affiliates covered. Define affiliate clearly and decide whether affiliates are sublicensees (licensee stays liable) or direct licensees.
• Object code versus source code. Many software licenses grant object code only. Source code access, if needed, comes through a separate license or source code escrow.
• Most-favored terms. A licensee with leverage may want assurance the licensor will not grant better terms to others in the same field. That is a separate, heavily negotiated commitment.

A licensee-protective transferability fallback looks like this:

Notwithstanding the foregoing, Licensee may assign this Agreement and the
license granted in it, without Licensor's consent, to a successor in a
merger, acquisition, or sale of all or substantially all of its assets,
provided the successor is not a competitor of Licensor and agrees in
writing to be bound by this Agreement.

Jurisdiction and enforceability notes

License grants are creatures of contract and IP law. The points below are the ones we read primary sources for in October 2026. Circuits and states we did not read are not covered, so confirm against the controlling law.

• Unstated rights may not be granted. The Ninth Circuit has said that "copyright licenses are assumed to prohibit any use not authorized," and refused to apply a state rule construing the contract against the drafter so as to give the licensee every right the licensor did not expressly retain (S.O.S., Inc. v. Payday, Inc., 886 F.2d 1081 (9th Cir. 1989), a software case). Write down every use you need.
• Exclusive copyright licenses need a signed writing. A "transfer of copyright ownership" is not valid unless the instrument or a note or memorandum of the transfer "is in writing and signed by the owner of the rights conveyed" (17 U.S.C. 204(a)), and the statute defines the term to include an "exclusive license" but not "a nonexclusive license" (17 U.S.C. 101). A nonexclusive license "may be granted orally, or may even be implied from conduct," in the Ninth Circuit's words quoting a treatise, and that court found implied nonexclusive licenses on its facts (Effects Associates, Inc. v. Cohen, 908 F.2d 555 (9th Cir. 1990)). Do not rely on that for a license that matters. Patents and applications "shall be assignable in law by an instrument in writing" (35 U.S.C. 261).
• Patent licenses: scope and standing. The Supreme Court has held that a restrictive license is legal and that making and selling outside the licensed field is the same as having no license at all (General Talking Pictures Corp. v. Western Electric Co., 305 U.S. 124 (1938), which affirmed after rehearing a case about amplifiers licensed for home use and sold for theaters). What a licensee can do about infringers depends on the rights it holds. The Federal Circuit recognizes three categories: a patentee, meaning a party with all substantial rights, who can sue in its own name; a licensee with "exclusionary rights," who can sue along with the patentee; and a licensee without exclusionary rights, who cannot assert the patent (Lone Star Silicon Innovations LLC v. Nanya Technology Corp., 925 F.3d 1225 (Fed. Cir. 2019)). The wording of the grant decides which category you are in.
• Transferability: a federal presumption in some circuits. In the Sixth Circuit, federal common law treats a patent or software license as personal and non-assignable unless the contract says otherwise, even where a state merger statute would pass it to the surviving company (PPG Industries, Inc. v. Guardian Industries Corp., 597 F.2d 1090 (6th Cir. 1979); Cincom Systems, Inc. v. Novelis Corp., 581 F.3d 431 (6th Cir. 2009)). In the Ninth Circuit, under the 1976 Copyright Act "an exclusive licensee has the burden of obtaining the licensor's consent before it may assign its rights, absent explicit contractual language to the contrary" (Gardner v. Nike, Inc., 279 F.3d 774 (9th Cir. 2002)). We did not review other circuits. A stock purchase that leaves the licensee as the contracting party is different from a merger: under Delaware law "stock purchase transactions, by themselves, do not result in an assignment by operation of law" (Meso Scale Diagnostics, LLC v. Roche Diagnostics GmbH, 62 A.3d 62 (Del. Ch. 2013)). See the assignment, successors and assigns and change of control pages, and build in a change-of-control carve-out.
• Field and territory limits meet antitrust and patent-misuse law. Field-of-use limits in patent licenses are enforceable (see above), but an agreement among competitors to divide territories is a per se violation of section 1 of the Sherman Act (United States v. Topco Associates, Inc., 405 U.S. 596 (1972)). In patent licensing, conditioning a license on taking another license or buying a separate product is not patent misuse "unless, in view of the circumstances, the patent owner has market power in the relevant market for the patent or patented product on which the license or sale is conditioned" (35 U.S.C. 271(d)(5)). Whether a particular restraint is lawful is fact-specific, so get antitrust review for restrictions between competitors.
• If the licensor goes bankrupt. Section 365(n) of the Bankruptcy Code lets a licensee of intellectual property keep its rights when the trustee rejects the license. Official text, as read on Cornell LII on 12 October 2026: 11 U.S.C. 365(n)(1)(B) lets the licensee elect "to retain its rights ... under such contract and under any agreement supplementary to such contract, to such intellectual property (including any embodiment of such intellectual property to the extent protected by applicable nonbankruptcy law)" for the duration of the contract and any extension the licensee has as of right (text). The licensee must keep paying royalties and waives set-off (365(n)(2)). "Intellectual property" is defined in 11 U.S.C. 101(35A) as trade secrets, inventions, processes, designs and plants protected under title 35, patent applications, plant varieties, works of authorship protected under title 17, and mask works. Trademarks are not on that list, but the Supreme Court held that rejection of a trademark license has the same effect as a breach outside bankruptcy and does not rescind rights the contract previously granted (Mission Product Holdings, Inc. v. Tempnology, LLC, No. 17-1657 (U.S. May 20, 2019)). See source code escrow for how 365(n) interacts with escrow.
• If the licensee goes bankrupt. Section 365(c)(1) bars the trustee from assuming or assigning an executory contract, without the other party's consent, where applicable law excuses that party from accepting performance from someone other than the debtor. How courts apply that to IP licenses was not surveyed.

This is general information, not legal advice. The scope and enforceability of a license turn on the governing law and the facts, so confirm against the controlling law before relying on the grant.

Review checklist: red flags to catch

• The field of use is "internal" or "internal business purposes" when you intend to distribute or commercialize.
• Exclusivity is claimed but the verb is "sole" (or vice versa), so the licensor can still use or grant it.
• No sublicense right when your model requires giving rights to affiliates, customers, or end users.
• The license is "non-transferable" with no change-of-control carve-out, so it may not survive an acquisition structured as a merger.
• Territory is narrower than your market, with no expansion path.
• The term is short or auto-terminating with no clear renewal.
• The grant covers object code only when you need source-code access or modification rights.
• A broad reservation of rights that walks back what the grant appears to give.
• Affiliate use undefined, leaving it unclear whether your group companies are covered.

How it interacts with other clauses

The license grant does not stand alone. Read it together with:

• Intellectual property: the IP clause sets ownership; the license grant covers everything not assigned. The two must fit without gaps or overlaps.
• Assignment: a non-transferable license plus a broad anti-assignment clause can prevent the license from surviving a sale; align the two.
• Change of control: confirm the license is not terminable, and is assignable, when the licensee is acquired.
• Source code escrow: an object-code-only license often pairs with escrow so the licensee can reach source code if the licensor fails; the escrow page covers how 365(n) bears on it.

For the broader workflow, see the in-house contract review playbook.

FAQ

What is a license grant clause? It is the contract provision that gives one party the right to use another's intellectual property without transferring ownership. The grant sentence sets the scope through dials: exclusivity, territory, field of use, term, sublicense rights, and transferability.

What is the difference between exclusive, sole, and non-exclusive? Non-exclusive lets the licensor grant the same rights to many parties. In common drafting usage, sole means only the licensee plus the licensor itself, and exclusive means only the licensee, which can be drafted to exclude even the licensor. Usage is not uniform, so define each term in the grant and confirm which one you are paying for. For copyright, an exclusive license counts as a transfer of copyright ownership and needs a signed writing (17 U.S.C. 101, 204(a)).

What is a field-of-use restriction? A field-of-use restriction limits the license to a defined purpose, product, or market, such as "internal use only" or "for use in the healthcare market." It lets a licensor license the same IP to different industries and is a common way to keep a grant narrow. Map it against what you actually plan to do.

Can a license survive an acquisition of the licensee? It depends on the deal structure and the contract. A stock purchase leaves the licensee as the contracting party and, under Delaware law, is not by itself an assignment (Meso Scale, 62 A.3d 62). A merger that moves a patent or software license to a different entity can be a prohibited transfer in the Sixth Circuit (PPG, 597 F.2d 1090; Cincom, 581 F.3d 431). Check the license's own transfer and change-of-control wording, and add a carve-out if you expect a sale.

Do I need a sublicense right? You need one if your business model requires giving rights to affiliates, distributors, or end users. Courts read licenses narrowly (S.O.S., 886 F.2d 1081) and the Ninth Circuit requires licensor consent before an exclusive copyright licensee transfers its rights absent contrary contract language (Gardner, 279 F.3d 774), so do not assume you can pass rights down. We did not survey sublicensing rules in other circuits or for patents, so write the right in.

Does a license transfer ownership of the IP? No. A license is a right to use; ownership stays with the licensor. If you need to own the IP rather than use it, that requires an assignment in a signed writing (17 U.S.C. 204(a) for copyright, 35 U.S.C. 261 for patents), which is a different mechanism handled by the IP clause.

Why does an exclusive copyright license need a writing? Section 204(a) of the Copyright Act makes a transfer of copyright ownership invalid unless it is in a writing signed by the owner, and section 101 defines that term to include an exclusive license but not a nonexclusive license. A nonexclusive license can be oral or implied from conduct (Effects Associates, 908 F.2d 555), but relying on that is risky. For any meaningful license, put the grant and its scope in writing.

Arshita Anand

Co-Founder & CEO · Attorney

Arshita leads product and strategy at Vaquill AI, the US primary law data API. As an attorney, she decides which law we carry, how each section is sourced and cited, and what legal AI and compliance teams need from the data.