License Agreement Structure & Key Clauses

A university or research institution rarely sells its intellectual property outright. Instead, it grants a license — a contract that lets a company, spinout, or other party make, use, or sell a technology under specific conditions, while the institution keeps title to the underlying patent, copyright, or know-how. This guide walks through the standard clause-by-clause structure of a technology license agreement: what each section does, the choices a technology transfer office (TTO) typically negotiates within it, and how the pieces fit together. It covers licenses generally — patents, know-how, biological materials, and non-software IP — as a companion to CASRAI’s dictionary entry on the Software License Agreement, which addresses the terms specific to licensing code (open-source compatibility, source-code escrow, warranty disclaimers under 17 U.S.C. § 102(b)). For the negotiation economics behind these clauses, see CASRAI’s guide to patent licensing: exclusive terms, royalties, and startup vs. established deals.

Where a License Agreement Fits in the Tech Transfer Process

A license agreement is typically the last document in a sequence that starts with an invention disclosure, moves through a patentability and marketability assessment, and often involves a non-disclosure agreement (NDA) while a prospective licensee evaluates the technology. Once a licensee is identified, many institutions first exchange a due diligence questionnaire — see CASRAI’s guide on the due diligence questionnaire in technology licensing — before drafting the license itself. Under the Bayh-Dole Act (35 U.S.C. §§ 200-212), a university that elects to retain title to a federally funded invention has both the right and, functionally, the expectation to license it out for commercial development; the license agreement is the mechanism that carries out that obligation.

The Typical Structure of a License Agreement

Format varies by institution and technology, but most university technology license agreements follow a recognizable structure:

Recitals / background — identifies the parties, the licensed patent(s) or technology, and the general purpose of the agreement.
Definitions — pins down terms used throughout, most importantly “Licensed Patents,” “Licensed Products,” “Net Sales,” and “Field of Use,” since royalty and scope obligations all key off these definitions.
Grant of rights — the operative clause: what is licensed, how exclusively, in what field, and where.
Sublicensing — whether and how the licensee may extend rights to a third party.
Consideration / payment structure — upfront fees, running royalties, minimum annual royalties, milestone payments, equity, patent cost reimbursement.
Diligence obligations — development milestones and reporting the licensee must meet to keep the license, particularly if exclusive.
Reporting and audit rights — periodic sales/royalty reports and the institution’s right to audit the licensee’s records.
Patent prosecution and maintenance — who controls filing decisions and who pays ongoing patent costs.
Representations, warranties, and disclaimers — typically narrow; see the discussion of freedom-to-operate below.
Indemnification and insurance — allocates liability for product-related claims and requires the licensee to carry adequate coverage.
Term and termination — how long the license runs and the conditions under which either party can end it early.
Boilerplate — governing law, assignment restrictions, dispute resolution, notices, and integration clauses.

Grant of Rights: Exclusive, Non-Exclusive, and Field-of-Use

The grant of rights clause is the core of the agreement, and it is defined along several independent dimensions that combine to set the license’s actual scope:

Exclusivity. An exclusive license means the institution grants rights to only one licensee (and typically gives up its own right to practice the invention, though many agreements carve out a reserved right for the institution’s own research and educational use). A non-exclusive license permits the institution to license the same technology to multiple parties simultaneously. A sole license sits between the two: only one commercial licensee, but the institution retains its own right to practice. Exclusive licenses are far more common for early-stage, capital-intensive technologies (e.g., a drug candidate requiring years of clinical development) because a licensee generally will not invest heavily in development without exclusivity protecting the eventual market.
Field of use. Rights can be limited to a specific application — for example, licensing a diagnostic platform “solely for use in veterinary diagnostics” while the institution retains the right to license the same underlying patent separately for human diagnostics. Field-of-use restrictions let a single invention support multiple, non-competing licensees.
Territory. Rights can be limited geographically (e.g., North America only), which matters most for institutions holding foreign patent rights via a PCT application.
Field/territory combined with exclusivity. These dimensions are independent and stack — an agreement might grant an exclusive license limited to a specific field and territory, non-exclusive outside it.

For a fuller comparison of exclusive vs. non-exclusive economics and how the choice shapes negotiation leverage between a startup licensee and an established company, see CASRAI’s patent licensing guide.

Royalty and Payment Structure

Consideration in a license agreement is rarely a single number; it is usually a combination of several payment types, each serving a different purpose:

Upfront/execution fee. A one-time payment due on signing, partly compensating the institution for patent costs incurred to date and partly signaling the licensee’s commitment.
Running royalty. A percentage of the licensee’s net sales of licensed products, paid periodically (typically quarterly) for the life of the agreement. The definition of “Net Sales” — what deductions are allowed (returns, freight, taxes) before the royalty percentage applies — is itself a heavily negotiated definition.
Minimum annual royalty (MAR). A guaranteed minimum payment regardless of actual sales, which protects the institution from an exclusive licensee that stops actively commercializing the technology without formally terminating the license.
Milestone payments. Fixed payments triggered by development events — first patient dosed, regulatory approval, first commercial sale — common in life-sciences licenses where development timelines span years.
Sublicense income share. If the licensee is permitted to sublicense (see below), the institution typically receives a percentage of any sublicense fees or royalties the licensee collects.
Equity. For a spinout licensee, the institution may take an equity stake in lieu of or alongside cash consideration — see CASRAI’s guide to funding options for a university spinout for how licensing fits alongside other spinout capital sources.
Patent cost reimbursement. Separate from royalties, licensees are typically obligated to reimburse the institution’s past and ongoing patent prosecution costs.

Actual royalty rates vary enormously by field, exclusivity, stage of development, and negotiating leverage — reported industry surveys (e.g., from the Association of University Technology Managers) show wide ranges rather than a single benchmark rate, so treat any specific percentage you see quoted as directional, not a norm to anchor to. CASRAI’s guide on royalty rate-setting methodology covers the analytical approaches (25% rule, comparable-transaction analysis, discounted cash flow) institutions and licensees use to arrive at a defensible number.

Diligence and Milestone Obligations

Because an exclusive license blocks the institution from licensing the same technology elsewhere, most exclusive agreements include diligence obligations requiring the licensee to actively develop and commercialize the technology — not simply sit on the rights defensively. Typical diligence provisions include:

A development plan submitted at signing, often with specific dated milestones (e.g., “complete proof-of-concept prototype within 18 months”).
Periodic written progress reports.
Minimum spending commitments on development.
A defined remedy if milestones are missed — commonly conversion from exclusive to non-exclusive, a right for the institution to terminate the field(s) where diligence failed, or a cure period followed by termination.

Diligence clauses are the institution’s primary protection against granting exclusivity to a licensee that never actually brings the technology to market — a standard concern given the institution’s mandate (particularly under Bayh-Dole) to see federally funded inventions actually reach practical application.

Sublicensing Rights

Whether a licensee may sublicense the technology to a third party is a separate, explicitly negotiated grant — it is not implied by an exclusive license. When sublicensing is permitted, the agreement typically specifies:

Whether the institution must approve each sublicense or consent is not required below defined conditions.
That any sublicense must include terms consistent with (or no less protective than) the head license — particularly audit rights, reporting, and indemnification flow-through.
That the licensee remains responsible for a sublicensee’s performance and payment obligations.
How sublicense income is shared with the institution (see Royalty and Payment Structure above).
What happens to sublicenses if the head license terminates — many agreements provide for surviving sublicensees to step into a direct license with the institution rather than losing their rights entirely.

Representations, Warranties, and Freedom to Operate

University license agreements are typically conservative in what the institution represents and warrants. As a matter of common drafting convention (not a specific statutory requirement), most institutional licensors disclaim any warranty of freedom to operate — that is, the institution does not represent that practicing the licensed patent won’t infringe a third party’s separate patent. Freedom-to-operate depends heavily on the licensee’s own eventual product design, which the institution does not control, so this analysis is left to the licensee. What the institution typically does represent is narrower: that it owns or controls the rights being licensed, and that it is not aware of any then-pending claim challenging that ownership. See CASRAI’s due diligence questionnaire guide for how a licensee typically investigates FTO and related risk before signing, separately from what the license agreement itself represents.

Indemnification and Insurance

Because the institution is not in the business of manufacturing or selling products, license agreements typically place product liability risk on the licensee. Standard provisions include:

An indemnification clause requiring the licensee to defend and hold the institution harmless from third-party claims arising out of the licensee’s use, manufacture, or sale of licensed products.
A requirement that the licensee carry commercial general liability and, where relevant, product liability insurance meeting specified minimum coverage amounts, naming the institution as an additional insured.
A disclaimer of the institution’s own liability for consequential or incidental damages.

Term and Termination

The term of a license agreement is usually tied to the life of the last-to-expire licensed patent (or, for know-how/trade-secret licenses with no patent, a fixed term or until the information enters the public domain). Termination provisions typically address:

Termination for breach — a cure period (commonly 30-60 days) after written notice of a material breach, after which the non-breaching party may terminate.
Termination for failure to meet diligence milestones — often handled separately from general breach, since the remedy may be narrower than full termination (see Diligence above).
Termination for convenience — many agreements let the licensee terminate on notice (e.g., 90 days) if the technology is no longer commercially viable for them.
Bankruptcy/insolvency — institutional termination rights if the licensee becomes insolvent, subject to the limits Section 365(n) of the Bankruptcy Code places on terminating IP licenses.
Survival clauses — which obligations continue after termination: accrued but unpaid royalties, confidentiality, indemnification for pre-termination sales, and any sublicensee step-in rights.

How This Differs From a Software License Agreement

CASRAI’s dictionary entry on the Software License Agreement covers the same general clause categories described above, but with software-specific additions that a patent or materials license doesn’t need: source code escrow and delivery terms, open-source component disclosure and license compatibility (a program built on GPL-licensed components carries different obligations than one that is not), warranty disclaimers grounded in the software-specific carve-out at 17 U.S.C. § 102(b) (copyright protects the expression of code, not the underlying method or idea), and maintenance/support terms that patent and biological-material licenses typically don’t include. If the technology being licensed is code, start with that entry; this guide is the general-purpose reference for the clauses common to license agreements across IP types.

Frequently Asked Questions

What is the difference between a license agreement and an assignment?

An assignment transfers ownership of the IP itself to the assignee. A license leaves ownership with the institution and grants only the specific rights described in the grant-of-rights clause, for the term and under the conditions the agreement sets out. Universities license far more often than they assign, in part because Bayh-Dole’s march-in and government-use rights, and the institution’s own reporting obligations, attach more naturally to a license structure.

Does a university license agreement need to be notarized?

Generally no. A license agreement is a standard contract; it is valid once signed by authorized representatives of both parties. Some institutions require the agreement to be countersigned by a specific delegated signing authority (e.g., the vice president for research) under internal signature-authority policy, which is an institutional governance requirement, not a legal notarization requirement.

Can a license agreement be amended after signing?

Yes — license agreements routinely include an amendment clause requiring any modification to be in writing and signed by both parties. Field-of-use expansions, added milestones, or updated royalty terms are commonly handled through a formal amendment rather than a new agreement.

What happens to a license if the underlying patent application is abandoned or rejected?

This depends on how the agreement defines “Licensed Patents” and what it says about patent prosecution control. Many agreements give the licensee the right to take over prosecution (at its own cost) if the institution decides to abandon an application, and some include a royalty step-down or termination right if no patent ever issues, since the value of an exclusive license is materially different for an issued patent versus a pending application with no guaranteed claims.

Is a license agreement the same as a material transfer agreement (MTA)?

No. An MTA governs the transfer of physical research materials (cell lines, reagents, biological samples) between institutions, typically for research use only, and does not grant commercial rights. A license agreement grants rights to make, use, or sell a technology commercially. A biological material that has commercial potential may move from an MTA (during early evaluation) to a license agreement (once a party wants commercial rights).

For related tech-transfer documentation, see CASRAI’s guides on NDAs in research and technology transfer, industry-university research partnership agreement structures, and the Technology Transfer & Innovation pillar for the full cluster of related content.