Document Automation
Product features
By practice area
By company size
Contract Review
PRODUCT FEATURES
Resources
LearN
Case Studies
Pricing
How to review IP license agreements with AI: common grant clauses decoded, field of use, royalties after patent expiration, grant-backs, and licensor bankruptcy.
Easy intake and document automation to auto-populate your templates.
Every IP license has a moment of truth, and it usually arrives months after signing. The product team ships a feature, a customer asks for a copy, or an acquirer's diligence team starts asking questions, and someone has to answer whether the license allows it. The answer lives in a grant clause that may be four lines long and spread across three documents.
License review rewards close reading of small words. "Use," "internal," "exclusive," and "improvements" each decide what the licensee actually bought, and each one shows up in a slightly different form in every draft.
The short answer: The best AI tool for reviewing IP license agreements checks the grant of rights against how the business plans to use the IP, applies your team's positions on royalties, sublicensing, and improvements, and returns redlines inside the Word document the license arrived in. Gavel Exec does this as a Microsoft Word add-in: it runs a licensing playbook against the draft, marks each rule as passed or failed with a link to the clause, and proposes tracked-change redlines for every failure.
Most license disputes start with a grant that reads well and covers less than the business assumed. The table below shows common grant language, what it allows, and what a licensee who plans to build on the IP would usually ask for instead. The sample language is illustrative.
| Sample language | What it allows | What a licensee building on the IP usually asks for |
|---|---|---|
| "A non-exclusive license to use the Software for Licensee's internal business purposes" | Running the software inside the company | Rights to copy, modify, and distribute the software as part of Licensee's products, and to let customers use it |
| "A license to make and use the Licensed Products" | Manufacturing and internal use under the patent | The full set of patent rights: make, have made, use, sell, offer to sell, and import |
| "An exclusive license in the Territory" | Unclear whether the licensor keeps its own rights | A definition stating whether the licensor may practice the IP itself and whether it may grant other licenses |
| "In the Field of veterinary diagnostics" | Use limited to one market | A field that matches the product roadmap, or a right of first negotiation for adjacent fields |
| "Licensee may not sublicense" | No rights for anyone outside the licensee entity | Sublicense rights for affiliates, contractors, distributors, and end customers |
| "Licensee shall assign to Licensor all Improvements" | The licensor owns everything the licensee builds on the IP | Ownership stays with whoever creates the improvement, with at most a non-exclusive license back |
| "This license is personal to Licensee" | Rights may not survive a merger or sale | Assignment to a successor in a merger or sale of the business without consent |
| Clause | What to check | Common red flag |
|---|---|---|
| Territory | Where the rights apply | A single-country grant for a business that sells internationally |
| Royalties | Rate, base, minimums, step-downs, and timing | Royalties that continue after the licensed patents expire with no non-patent rights to support them |
| Audit rights | Frequency, notice, who pays, and look-back period | Unlimited audits at the licensee's cost |
| Warranties and indemnity | Non-infringement warranty and IP indemnity exclusions | A broad "combination" carve-out that removes most real claims |
| Challenge clauses | What happens if the licensee challenges validity | Termination or a royalty increase triggered by any challenge |
| Termination effects | Wind-down period and surviving rights | Immediate loss of rights for products already in customers' hands |
These are US rules. Check local law for licenses governed elsewhere.
If a licensor goes bankrupt and rejects the license, Section 365(n) of the Bankruptcy Code lets the licensee elect to keep its rights for the term of the license if it keeps paying royalties. The Code's definition of intellectual property in Section 101(35A) covers patents, copyrights, trade secrets, and mask works but does not list trademarks. In Mission Product Holdings v. Tempnology (2019), the Supreme Court held that rejecting a trademark license breaches the contract but does not rescind the licensee's rights.
Under Kimble v. Marvel Entertainment (2015), a patent holder cannot collect royalties for use of an invention after the patent expires. The Court described lawful alternatives: deferring payments for pre-expiration use, tying post-expiration royalties to non-patent rights such as trade secrets, and stepping the rate down at expiration.
A patent licensee may challenge the validity of the licensed patent (Lear v. Adkins, 1969) and does not need to breach the license before seeking a declaratory judgment of invalidity (MedImmune v. Genentech, 2007). Licensors often respond with termination rights or royalty increases triggered by a challenge.
Under 17 U.S.C. § 203, an author can terminate a copyright grant made on or after January 1, 1978 during a five-year window that begins 35 years after the grant, notwithstanding any agreement to the contrary. Works made for hire are excluded.
Consider the general counsel of a 30-person medical device startup. The company is licensing a sensor patent from a university technology transfer office, and the board wants it signed before the next financing closes.
She opens the university's draft in Word, attaches the term sheet to the chat, and runs her licensee playbook in Gavel Exec. Three rules fail. The field of use covers "cardiac monitoring," while the term sheet and the product roadmap include respiratory monitoring. The improvements clause gives the university an exclusive license to anything the company develops. The royalty runs "for the life of this Agreement," which extends past the last patent's expiration with no trade secret or know-how grant to support it. She asks Exec to draft a step-down at expiration and a non-exclusive, research-only license back to the university, then edits both before applying them.
The tech transfer office accepts the field change and the step-down in the first round. The investors' counsel, who reviews the license in diligence a month later, has no questions about it.
Many companies hold dozens of inbound licenses signed over many years, and the hard questions arrive in diligence: which of our licenses terminate on a change of control, and which ones assign our improvements to someone else? Licensing teams increasingly want AI that answers those questions across the full set of licenses at once. Running every new license through the same playbook and logging the results is the best preparation for that, because the answers are recorded consistently from the start.
Open the license in Word, attach the order form, term sheet, or exhibits to the chat, and run a licensing playbook with licensee-side or licensor-side rules. Ask deal-specific questions such as "If we are acquired, do we keep this license?" Each finding links to the language it relies on, and each proposed redline shows a priority level and its reasoning. Teams can generate a licensing playbook from their template license and negotiation guidelines with AI Playbooks. Gavel Exec is SOC 2 Type II certified, Gavel has zero data retention agreements with its large language model (LLM) providers, and customer documents are not used to train models.
Related reading: AI contract review for music agreements and why precedent-based contract review creates bottlenecks.
For lawyers who negotiate licenses in Microsoft Word, a Word-native tool such as Gavel Exec applies a licensing playbook to the draft, links each finding to the clause, and proposes tracked-change redlines. CLM platforms suit teams whose priority is storing executed licenses and tracking obligations.
A field-of-use restriction limits a license to particular industries, products, or purposes. A licensee should compare it against every planned use of the IP, including future products, before signing.
A grant-back clause requires the licensee to license or assign its improvements back to the licensor. Licensees usually negotiate for a non-exclusive license back, or for improvements to stay with the party that created them.
Not for use of the expired patent. Under Kimble v. Marvel Entertainment, those royalties are unenforceable, although royalties tied to non-patent rights or deferred payments for pre-expiration use can be structured lawfully.
Under Section 365(n), a licensee of patents, copyrights, or trade secrets can elect to keep its rights for the term of the license if it keeps paying royalties. Trademarks fall outside Section 365(n), but Mission Product Holdings v. Tempnology held that rejecting a trademark license does not rescind the licensee's rights.
This article provides general information and is not legal advice.
Guides to AI contract review by practice area, covering data privacy, IT managed services, IP licensing, construction, music, investment funds, procurement, and private equity.
How to review LPAs and side letters with AI: the LPA provisions LPs negotiate, how MFN elections work, an MFN tracker you can copy, and the 2026 regulatory context.
How to review music agreements with AI: a worked recoupment example, cross-collateralization, controlled composition at the 2026 mechanical rate, 360 deals, and the seven-year rule.
