Home
Playbooks
Software License Agreement Playbook: Licensee Review Positions
Software license agreement

Software License Agreement Playbook: Licensee Review Positions

By 
Gavel Team
 |  Written for: 
Licensee side
 |  Last reviewed: 
November 17, 2026
Run this playbook on your next contract

Gavel Exec reviews and redlines contracts inside Microsoft Word, checked against your own playbook. Start with 25 free queries, no credit card required.

A software license agreement review for the licensee tests five things in the vendor's paper: who and what the license covers, how use is counted and audited, what maintenance will cost over the years, what happens if the vendor fails, and whether the license survives a merger, a divestiture or the end of support.

Key takeaways

  • Write the grant to reach affiliates, contractors, virtual machines and disaster recovery copies.
  • Limit the license audit clause: notice, one audit a year, an independent auditor under a nondisclosure agreement, and the contracted price as the only charge for a shortfall.
  • Cap maintenance increases and set reinstatement terms at signing.
  • For software the business cannot replace quickly, take escrow with release triggers beyond bankruptcy.
  • Draft the transfer clause for mergers and divestitures. A federal appeals court has treated an internal merger as an unlicensed transfer.

Last reviewed November 17, 2026. This playbook is general information for lawyers, not legal advice for a specific matter. Gavel publishes it and makes Gavel Exec.

Installed software: what the licensee holds

Under an on-premises or self-hosted license, the licensee holds copies of the vendor's code on its own systems. The vendor cannot see usage, so it audits. Fees split into a one-time license charge and recurring maintenance. A perpetual license can still be lost to a termination clause, a merger or a support lapse.

For hosted subscriptions, use the software as a service (SaaS) agreement playbook. For liability structure and general vendor terms, see the master services agreement (MSA) playbook; the contract playbooks hub lists the rest.

Reading the table from the licensor's chair

A licensor's first draft runs the other way: the signing entity only, named servers, audits on short notice, list price for any shortfall, and assignment only with consent.

Common Paper's Software License Agreement, version 1.1, a published standard form "made for buying and selling on-prem, downloadable, or self-hosted software," sits between the two. It licenses use "During the Subscription Period," calls its warranty remedy "Customer's exclusive remedy," and lets either party assign on notice after "a merger, change of control." Acting for a licensor, hold three points: indemnity exclusions for modifications, escrow release only on defined failures, and no transfer to a named competitor.

Clause-by-clause table for the licensee

Propose the preferred column in the first markup and concede the fallback without escalating. Anything in the fourth column goes to the lawyer who owns the deal. The numbers are this playbook's suggested positions; scale them to spend and risk.

IssuePreferred positionAcceptable fallbackEscalate or walk away ifWhy it matters
Licensed users and entitiesLicensee, present and future affiliates, and contractors and outsourcers working for them.Affiliates listed in the order form, others added on notice. Contractors use the software only for licensee work.License limited to the signing entity, or outsourcers need their own licenses.Group companies and outsourcers are the first users an auditor counts.
Installation environment and territoryAny hardware, virtual machine, container or cloud tenancy the licensee controls, worldwide, subject to export control law.Listed environments and countries, with moves on notice and no fee.License locked to a named server or site, with a fee per move or for offshore access.Hardware refreshes and cloud moves happen during a perpetual license.
Non-production copiesUnlimited test, development, failover and disaster recovery copies at no charge, outside the metric unless used in production.Non-production copies up to the production count. Cold standby free.Every test or disaster recovery instance priced as production.Section 117 archival rights belong to owners of copies.
License metricDefined in the agreement and fixed for the life of the license. Counting policies apply only as attached at signing.Changes only at a maintenance renewal, with a conversion table that keeps entitlement value.Metric defined by a web page the vendor can revise.A metric change can turn a compliant deployment into a shortfall.
True-upsAnnual self-reported true-up in arrears at the contracted unit price.Contracted price plus 10%, maintenance prorated from the true-up date.Added units at then-current list price plus back maintenance.Growth pricing is set while the licensee still has leverage.
Audit rightOnce a year, 60 days' notice, independent auditor under the licensee's nondisclosure agreement, deployment records only.30 days' notice. Licensee pays audit costs only if the shortfall exceeds 5% of fees for the audited product.Audits at any time, vendor tools on licensee networks, or audit rights lasting more than 12 months after the license ends.Audit findings are where list price and back maintenance get charged.
Remedy for overuseBuy the missing licenses at the contracted price within 60 days, as the sole remedy. No breach or infringement.Contracted price plus back maintenance for up to 12 months.List price, back maintenance from first deployment, penalties, or termination.Mintz and Business Law Today both recommend making payment the exclusive remedy.
Maintenance fees and reinstatementIncreases capped at the lower of 3% or the Consumer Price Index (CPI). Partial reductions allowed. Reinstatement at the lapsed fees.5% cap. Reduced quantities repriced at their discount tier. Reinstatement at back fees plus 10%.Uncapped increases, all-or-nothing support, or reinstatement at 150% of back fees.Oracle's published policy adds a reinstatement fee of 150% of the last annual fee, prorated over the lapse.
Supported releasesEach major release supported for 24 months after its successor ships, with 12 months' notice of end of support.12 months after the successor ships, with 6 months' notice.Short-notice end of support, with a new license fee to stay supported.Upgrading installed software takes planning, testing and downtime.
Performance warrantyConforms to the documentation for 12 months after acceptance. No disabling code. Refund if a defect stays unfixed for 30 days.90 days after acceptance, with the same refund backstop.Warranty runs from delivery, or the only remedy is more repair attempts.Common Paper's form makes its warranty remedy section the customer's exclusive remedy.
Open source componentsA software bill of materials (SBOM) with each release, and a warranty that no component obliges the licensee to disclose its own code.Component list on request, plus notice before a new copyleft component is added.Open source excluded from every warranty and the indemnity, with no list.Section 13 of the Affero General Public License (AGPL) reaches modified versions used over a network.
Source code escrowDeposit within 30 days after each release. Release on bankruptcy, end of business, uncured support failure, or end of life.Release on bankruptcy or cessation of business only. Annual deposits.No escrow for software that runs a core operation and has no ready replacement.11 U.S.C. 365(n) protects rights under agreements supplementary to the license.
Intellectual property (IP) infringement indemnityPatent, copyright and trade secret claims in every licensed country. Exclusions only for licensee changes and undocumented combinations.Patents limited to the United States and listed countries. Refund depreciated over five years.U.S. patents issued at signing only, or exclusions for standard hardware.The licensee runs the copies, so a rights holder can sue the licensee directly.
Liability capGreater of all license fees plus 12 months of maintenance, or a dollar floor. IP indemnity and confidentiality outside the cap.All fees paid in the 24 months before the claim, with a floor. IP indemnity capped at 2 times total fees.A 12-month lookback only, or uncapped licensee liability for breach of license restrictions.After year one, a 12-month lookback captures only maintenance.
Transfer on merger or divestitureAssignment without consent to affiliates and successors by merger, sale or reorganization. Divested units keep allocated licenses.Consent not unreasonably withheld, plus 12 months of transition use after a divestiture.Consent for any change of control or internal merger, or a transfer fee.The Sixth Circuit treated an internal merger as an unlicensed transfer.
Termination and survivalA paid-up perpetual license survives the end of maintenance. Licensor ends it only for uncured material breach of the license restrictions or unpaid license fees (60-day cure). Excess use goes through the audit remedy.30 days to cure. Buying the missing licenses cures excess use.Termination of the license for any breach, including late maintenance.The word perpetual protects nothing if the termination clause reaches the license.

Who may use the copies, where, and how they are counted

A license to "Licensee" alone excludes subsidiaries, and a per-server license can be read to exclude a virtual machine that moves between hosts. Name the affiliates, contractors and outsourcers who may use the software, and list the permitted environments, including any cloud tenancy the licensee controls.

Section 117 of the Copyright Act lets "the owner of a copy of a computer program" make a copy "for archival purposes only". An agreement stating that the licensee takes no title to its copies may put it outside the statute, so grant test, failover and disaster recovery copies expressly and keep them outside the metric.

Fix the metric for the life of the license. If the vendor can move from processors to cores, or from named users to all employees, a compliant deployment becomes a shortfall with no new installs.

Limiting the license audit clause

Common Paper's optional audit language requires "at least 7 days advance notice of an audit" and makes the customer pay for excess use.

A January 2023 article in the American Bar Association (ABA)'s Business Law Today recommends notice of "at least sixty days," audits "no more than once per year," and fees for additional licenses as the vendor's "sole and exclusive remedy" for excess usage. Julie E. Korostoff of Mintz adds an auditor nondisclosure agreement "on the licensee's form."

Preferred: "Licensor may verify Licensee's compliance no more than once in any twelve-month period, on at least sixty days' written notice, through an independent auditor reasonably acceptable to Licensee who has signed Licensee's nondisclosure agreement. The audit will cover only records of deployment of the Software and will not run any tool or script on Licensee systems without Licensee's written approval. If the audit shows use beyond the licensed quantity, Licensee will purchase the additional licenses at the Order Form unit prices within sixty days after the final report. That purchase is Licensor's sole remedy for the excess use, which is neither a breach of this Agreement nor an infringement. Licensor bears the cost of the audit."
Fallback: "...on at least thirty days' written notice... Licensee will reimburse Licensor's reasonable audit costs if the excess use exceeds five percent of the fees for the audited Software..."

A licensor may object that sixty days lets the licensee uninstall copies before the count. Offer to measure usage as of the notice date. SHI suggests shifting audit costs to the vendor unless a variance of 5 to 10 percent is confirmed; the fallback uses the low end.

Maintenance fees, lapses and support for older releases

Oracle's Software Technical Support Policies (effective November 7, 2025) require that "all licenses in any given license set must be supported under the same technical support service level." The fee to reinstate lapsed support is "150% of the last annual technical support fee you paid for the relevant program," prorated over the lapse, plus the new period's fee. Put the terms that matter into the order itself.

Preferred: "Annual Support Fees will not increase by more than the lesser of three percent or the twelve-month increase in the Consumer Price Index. Licensee may end Support for any number of licenses at a renewal date, with a proportional fee reduction, and may reinstate lapsed Support by paying the fees for the lapsed period with no reinstatement charge. Licensor will support each major release for at least twenty-four months after the next major release becomes generally available."
Fallback: "...not more than five percent... Fees for the remaining licenses may be adjusted to the price list discount tier for the reduced quantity... reinstatement at the lapsed fees plus ten percent..."

A vendor may resist partial reductions because the discount assumed the full quantity. Accept repricing at the smaller quantity's tier.

Open source inside the delivered code

Common Paper's form provides that open source license terms "will apply to that Open Source Software instead of this Agreement." That leaves the licensee holding whatever duties those licenses attach to its use. For installed software, the sharpest is Section 13 of the GNU Affero General Public License, version 3: "if you modify the Program, your modified version must prominently offer all users interacting with it remotely" a way to get its source code.

Ask for a software bill of materials. The National Telecommunications and Information Administration (NTIA) defines an SBOM as "a formal record containing the details and supply chain relationships of various components used in building software".

Preferred: "With each release, Licensor will deliver a software bill of materials identifying every open source component and its license. Licensee's use of the Software as delivered and as permitted by this Agreement, including any modifications Licensor makes, will not require Licensee to disclose, license or distribute any of its own source code."
Fallback: "On request, Licensor will list open source components and their licenses, and will give thirty days' notice before adding any component whose license requires disclosure of source code."

A vendor may ask to exclude open source from the infringement indemnity. Limit that exclusion to components on the list at signing.

Source code escrow and the licensor's insolvency

If a bankrupt licensor rejects the license, 11 U.S.C. 365(n) lets the licensee elect "to retain its rights" under the license "and under any agreement supplementary to such contract," and on written request the trustee must provide intellectual property it holds to the extent those agreements provide. Draft the escrow agreement as supplementary to the license, and put the right to use, modify and compile released materials in the license itself.

The federal banking agencies' June 2023 third-party risk guidance tells a banking organization buying software to consider provisions to "establish escrow agreements to provide for the banking organization's access to source code and programs" under conditions such as insolvency.

Preferred: "Within thirty days after each release, Licensor will deposit the complete source code for that release with the Escrow Agent, with build scripts, dependencies and instructions sufficient for a skilled programmer to compile and deploy it. The Escrow Agent will release the deposit to Licensee if Licensor (a) becomes subject to a bankruptcy or insolvency proceeding, (b) ceases to do business in the ordinary course, (c) fails to correct a Severity 1 error within thirty days after notice, or (d) ends Support without a successor product on the same terms. Licensee may then use, modify and compile the deposit solely to support its licensed use."
Fallback: "...deposits at least once every twelve months... release only on events (a) and (b)..."

A vendor may offer release on bankruptcy alone. Vendors can abandon a product without filing, so keep trigger (d) for core systems.

Mergers, internal reorganizations and divestitures

In Cincom Systems, Inc. v. Novelis Corp. (6th Cir. 2009), the licensee merged into an affiliate while the software stayed on the same computer at the same plant. The license barred transfer without Cincom's written approval. Applying a federal presumption that intellectual property licenses are nontransferable, the court held that "[a] transfer is no less a transfer because it takes place by operation of law" and found infringement. Damages were stipulated at $459,530, the original license fee.

In Meso Scale Diagnostics, LLC v. Roche Diagnostics GmbH (Del. Ch. 2013), the Delaware Court of Chancery read Delaware's merger statute to support the position that "a reverse triangular merger generally is not an assignment by operation of law or otherwise" and declined to follow SQL Solutions, a federal decision applying California law. Results turn on the clause, the structure and the governing law, so write the answer into the contract.

Preferred: "Licensee may assign this Agreement, or any licenses under it, without consent to an Affiliate or to a successor to all or the relevant part of its business, by merger, sale of stock or assets, reorganization or operation of law. A divested Affiliate or business unit may keep using the licenses Licensee allocates to it, on these terms, after signing a joinder."
Fallback: "...with Licensor's consent, not to be unreasonably withheld, conditioned or delayed... the divested entity may use its allocated licenses for twelve months while it obtains its own."

If the licensor fears transfer to a competitor, exclude a short list of named competitors.

Liability, infringement indemnity and keeping the perpetual right

Licensed software front-loads its fees: a large license fee in year one, then maintenance. A 12-month lookback shrinks the cap to one year of maintenance from year two on, so measure it on all license fees plus a year of maintenance, with a dollar floor. A licensor carve-out for the licensee's "breach of license restrictions" makes overuse uncapped; route overuse through the audit remedy.

The licensee runs the copies, so a patent or copyright holder can sue the licensee directly. Cover every licensed country, and limit exclusions to the licensee's own changes and undocumented combinations.

A paid-up perpetual license should survive the end of maintenance, and the licensor should be able to end it only for an uncured material breach of the license restrictions or unpaid license fees, with excess use handled through the audit remedy. Check the license key terms too: a key that expires when support lapses ends a perpetual license in practice.

Industry and buyer profiles that change the license terms

Licensee profileWhat changesWhy
Hospital or health tech companyIf vendor support staff will receive or keep protected health information (PHI), for example in databases or logs sent for troubleshooting, sign a business associate agreement (BAA), log remote sessions and keep PHI out of audit data.45 C.F.R. 164.502(e) requires a written contract documenting a business associate's assurances.
Bank or other federally supervised banking organizationEscrow for software the bank depends on, audit and remediation rights, regulatory examination, and continuity planning.The federal banking agencies' June 2023 guidance lists these among contract terms to consider.
Manufacturer or laboratory running software on equipmentLicense tied to the equipment and transferable with it, offline activation, and support for the equipment's service life.Equipment outlives release cycles.
Acquisitive company or private equity portfolio companyConsent-free assignment to affiliates and successors, a divestiture split, no transfer fees.Courts treat mergers differently depending on structure and governing law.
Startup licensee compared with an enterprise licenseeA startup on the vendor's order form secures affiliate coverage, transfer to an acquirer and a maintenance cap. An enterprise adds an audit protocol and escrow.Spend buys negotiation, and a startup's acquisition is the event its transfer clause must survive.

Sources: 45 C.F.R. 164.502(e) and the banking agencies' guidance. For health data terms, see the business associate agreement playbook. The other rows are this playbook's practice suggestions.

Checklist for the execution copy

  1. Map every environment where the software will run to the grant and the metric.
  2. Confirm every entity and contractor using the software is covered.
  3. Compare current deployments with entitlements, so the first audit starts from zero.
  4. Attach any vendor counting policy in the version in force at signing.
  5. Price five years of maintenance under the cap, with partial reduction and reinstatement terms.
  6. Read the SBOM for network copyleft licenses.
  7. Check escrow deposit contents, release triggers and the license to use released code.
  8. Test the assignment clause against planned mergers, reorganizations and divestitures.
  9. Confirm that ending maintenance cannot end the perpetual license.
  10. Calculate the liability cap in dollars for year three.

License terms that warrant a call to the vendor

  • "Licensor may audit Licensee's use at any time," or audit tools that run on licensee networks without consent.
  • Counting rules incorporated from a web page "as updated from time to time."
  • License keys that expire when maintenance lapses on a license sold as perpetual.
  • "Any transfer, including by merger or operation of law, requires Licensor's prior written consent," with no affiliate exception.

Reviewing a vendor license in Word with Gavel Exec

Copy this page's table into a spreadsheet, or upload licenses your company has already signed, and Gavel Exec (Gavel's AI contract review and drafting software, which runs inside Word) turns either one into playbook rules. It can also build rules from a written checklist; source files can be .docx, PDF or .csv. Details are on the Gavel Exec playbooks page.

Run those rules on a licensor's draft, and the add-in marks up the document with tracked changes ranked by priority, each explained. The web app's benchmarking then tags every provision as on-market, off-market or missing. A seat costs $160 a month, or $1,740 billed yearly; new users start with 25 queries free and no card on file.

Frequently asked questions

What should a software license agreement review cover?

Check the grant (users, affiliates, environments and territory), the metric and true-ups, the audit clause, maintenance fees, the warranty, open source, escrow, the IP indemnity, the liability cap, transfer on a merger, and whether termination can reach a perpetual license.

How can a licensee limit a software license audit clause?

Ask for advance written notice (the ABA's Business Law Today suggests at least sixty days), one audit a year at most, an independent auditor under a nondisclosure agreement, and the purchase of additional licenses as the vendor's sole remedy for overuse.

Does a perpetual software license end if you stop paying maintenance?

Only if the agreement or the license key terms say so. Require that the perpetual license survive the end of maintenance, and fix the price to reinstate lapsed support in advance.

Does a software license transfer in a merger or acquisition?

It depends on the contract, the deal structure and the governing law. The Sixth Circuit held in Cincom v. Novelis that an internal merger transferred a nontransferable license, while the Delaware Court of Chancery reasoned in Meso Scale v. Roche that a reverse triangular merger generally is not an assignment by operation of law.

What is source code escrow, and when is the code released?

An escrow agent holds the vendor's source code and releases it to the licensee on listed events, such as bankruptcy or a failure to support. Section 365(n) of the Bankruptcy Code protects a licensee's rights under agreements supplementary to the license.

How is a software license agreement different from a SaaS agreement?

A software license lets the licensee run copies on its own systems, so audits, maintenance, escrow and perpetual rights dominate. Under a software as a service (SaaS) agreement the vendor hosts the software, so uptime and data export dominate.

Related reading: the SaaS agreement playbook for hosted software, the MSA playbook for general vendor terms, and redlining contracts with AI.

Try Gavel Exec free

AI contract review and redlining in Microsoft Word, checked against your own playbook, with the reasoning behind each change.

Start a free trial
25 free queries • No credit card required