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.
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 three different things. Exclusive can even 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 usually defaults against the licensee.
- 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.
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 gets acquired. If the grant is "non-transferable" and there is no change-of-control carve-out, the license may not survive the deal, and the acquirer inherits a product it cannot legally ship.
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
| Licensee (getting the rights) | Licensor (owns the IP) | |
|---|---|---|
| Exclusivity | Exclusive, to lock out competitors | Non-exclusive, to license widely |
| Territory | Worldwide | Narrow, defined regions |
| Field of use | Broad, "any purpose" | Narrow, one defined use or market |
| Term | Perpetual or long, with renewal | Short, tied to fees |
| Sublicense | Right to sublicense affiliates and customers | None, or tightly controlled |
| Transferability | Assignable, survives change of control | Non-transferable, terminates on assignment |
| Reservation of rights | Minimal | Broad, all rights not expressly granted reserved |
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
| Issue | Opening position | Fallback both accept | Walk-away |
|---|---|---|---|
| Exclusivity | Exclusive in licensee's field | Sole, or exclusive in a narrow field for a fee premium | Non-exclusive when the licensee built a business on it |
| Territory | Worldwide | Defined regions with expansion rights | Single country with no path to expand |
| Field of use | Any purpose | Defined products and markets, with room to grow | Internal use only when distribution is the point |
| Term | Perpetual | Initial term with renewals | Short term with no renewal certainty |
| Sublicense | To affiliates and end users | To end users via EULA; affiliates on notice | No sublicense when the model requires it |
| Transferability | Freely assignable | Assignable in a change of control to a non-competitor | Non-transferable with no change-of-control carve-out |
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. A sole license lets the licensor keep using the IP itself but grant it to no one else. An exclusive license can be drafted to exclude even the licensor. If you are paying for exclusivity, confirm which one you are getting.
- 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. Most 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, and a few principles govern how they hold up:
- Unstated rights are reserved. US courts generally read license grants narrowly against the licensee: what is not expressly granted is reserved to the owner. A right you assume but do not write down is usually not granted.
- Exclusive copyright licenses need a signed writing. Under the US Copyright Act, a transfer of exclusive rights, including an exclusive license, generally must be in a signed writing to be effective. Non-exclusive licenses can be oral or implied, but never rely on that.
- Patent license defaults differ. A bare patent license is a covenant not to sue; an exclusive patent license can carry standing to enforce. The wording controls what the licensee can do about infringers.
- Anti-assignment defaults can trap licenses. US law often treats patent and copyright licenses as personal and non-assignable absent consent, even in a change of control, unless the contract says otherwise. Build in the change-of-control carve-out.
- Antitrust limits exist on field and territory. Most field-of-use, territory, and exclusivity restrictions are enforceable, but unusually broad tying or market-allocation terms can raise competition concerns. Keep restrictions tied to a legitimate business purpose.
This is general information, not legal advice for a specific deal. 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 dies in an acquisition.
- 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.
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. Sole means only the licensee plus the licensor itself, with no one else added. Exclusive means only the licensee, and can be drafted to exclude even the licensor. Confirm which one you are paying for.
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? Only if the contract allows it. US law often treats IP licenses as personal and non-assignable without consent, even in a change of control. If a non-transferable license has no change-of-control carve-out, it can fail to pass to the acquirer, leaving them with a product they cannot legally use.
Do I need a sublicense right? You need one if your business model requires giving rights to affiliates, distributors, or end users. Without an express sublicense right, you generally cannot pass any of the license down. Distribution and embedded-software models in particular fail without it.
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, which is a different mechanism handled by the IP clause.
Why does an exclusive copyright license need a writing? Under the US Copyright Act, a transfer of an exclusive right, including an exclusive license, generally must be in a signed writing to be valid. A non-exclusive license can be oral or implied, but relying on that is risky. For any meaningful license, put the grant and its scope in writing.
Related clauses
Clauses that get negotiated alongside this one.
