Diligence Milestones and Termination-for-Failure-to-Commercialize Clauses in University Exclusive Licenses

An exclusive license takes a technology off the market for everyone except the licensee — which is exactly why most university exclusive licenses do not stop at granting rights and setting royalties. They also impose diligence obligations: contractual commitments that the licensee will actually spend money, hit development milestones, and move the technology toward commercial availability, backed by a termination-for-failure-to-commercialize remedy if it doesn’t. This guide is a clause-level deep dive into how those two provisions are drafted, negotiated, and enforced. For the surrounding structure of a license agreement as a whole — grant of rights, royalties, sublicensing, indemnification — see CASRAI’s guide to license agreement structure, which introduces diligence and termination as two of many clause categories; this page goes substantially deeper into just these two, matching the level of detail CASRAI’s guides to field-of-use restrictions, MFN and anti-stacking clauses, and grant-back clauses already provide for those individual mechanics.

Why Exclusive Licenses Need a Diligence Clause

A non-exclusive license carries little commercialization risk for the licensor: if one licensee sits on the technology, the institution can license it to someone else. An exclusive license removes that fallback — for the life of the exclusivity, the technology can only reach the market through this one licensee, in whatever field and territory the grant covers. If the licensee stops actively developing the technology, whether because a corporate priority shifted, funding dried up, or the licensee simply lost interest, the invention sits idle and the institution has no other outlet to license it. Diligence and termination-for-failure-to-commercialize clauses exist to prevent exactly that outcome: they give the institution a contractual basis to reclaim exclusivity (or the license outright) from a licensee that isn’t developing the technology, without having to prove a conventional breach of contract.

This is also a mission consideration, not just a commercial one. Universities that elect to retain title to a federally funded invention under the Bayh-Dole Act (35 U.S.C. §§ 200-212) take on an implicit obligation to see those inventions reach practical use — the statute’s own policy declaration in 35 U.S.C. § 200 calls for using the patent system “to promote the utilization of inventions arising from federally supported research.” A diligence clause is the institution’s day-to-day mechanism for meeting that obligation; it operates entirely at the contract level, between the institution and its licensee, and is legally distinct from — though closely related in purpose to — the federal government’s own march-in rights under 35 U.S.C. § 203, which let a funding agency itself step in if a recipient organization fails to take effective steps to achieve practical application. See that guide for the federal-level remedy; this page covers the contractual remedy the institution itself holds and exercises directly.

What a Diligence Clause Actually Requires

A diligence clause is rarely a single sentence promising “best efforts.” Institutions that rely on best-efforts language alone generally find it difficult to enforce, because “best efforts” is inherently hard to measure and even harder to prove a licensee fell short of. The more enforceable pattern — and the one most university technology transfer offices (TTOs) use for exclusive licenses — combines several elements:

• A development plan. Submitted at signing or shortly after, describing the steps and approximate timeline the licensee intends to follow to bring the licensed technology to market. In life-sciences licenses this plan often maps onto a regulatory pathway (preclinical work, IND filing, clinical phases); in other fields it maps onto product development and go-to-market milestones.
• Dated, objective milestones. Specific, checkable events with dates attached — not aspirational language. “Complete a working prototype by [date],” “file an IND with FDA by [date],” or “achieve first commercial sale by [date]” are enforceable because either the event happened by the date or it didn’t. “Use commercially reasonable efforts to develop the technology” is not, on its own, similarly checkable.
• Periodic written progress reports. Typically annual or semi-annual, giving the institution visibility into whether development is actually proceeding between milestone dates, not just a pass/fail check at each deadline.
• Minimum development spend or minimum annual royalties. A dollar floor on development spending, or a minimum annual royalty (MAR) payable regardless of actual sales, gives the institution a financial signal — and some compensation — even before a milestone date arrives, and discourages a licensee from holding the license purely to block competitors.
• A defined consequence for missing a milestone. The clause needs to specify what happens if a milestone is missed — see below — rather than leaving the remedy to be litigated after the fact.

The specificity of the milestones matters more than their number. A handful of genuinely dated, checkable milestones spanning the expected development timeline is more enforceable — and easier for both sides to negotiate around in good faith — than a long list of vague developmental goals.

Types of Milestones by Development Stage

Milestone content varies substantially by field, but most exclusive licenses draw from three broad categories, often combined within a single development plan:

• Technical/development milestones. Prototype completion, successful scale-up, design freeze, or completion of a defined testing protocol. Common in physical-technology and device licenses where the main uncertainty is engineering feasibility rather than regulatory approval.
• Regulatory milestones. Filing an IND or IDE, completing specific clinical trial phases, or securing marketing authorization/FDA approval. Dominant in pharmaceutical, biologic, and medical-device licenses, where regulatory clearance — not engineering — is the long pole in the timeline, and where a single milestone (e.g., “dose first patient”) can span a multi-year gap from the previous one.
• Commercial milestones. First commercial sale, minimum sales thresholds by a given year, or securing a specified level of investment or a distribution partner. These sit closest to actual market availability and are usually the last milestones in the sequence, often paired with royalty step-ups or milestone payments (see the payment-structure discussion in CASRAI’s license agreement structure guide).

Because regulatory and clinical timelines are inherently uncertain, licensees in life-sciences deals routinely negotiate for milestone dates tied to events (e.g., “within 12 months of completing Phase 1”) rather than fixed calendar dates, and for a mechanism to request an extension supported by documented, good-faith development effort. A milestone schedule with no extension mechanism at all tends to produce disputes the first time a milestone is missed for reasons genuinely outside the licensee’s control (e.g., an FDA clinical hold), which is one reason most negotiated schedules build in some flexibility rather than treating every missed date as an automatic default.

Remedies When a Milestone Is Missed

Termination is the remedy of last resort, not the automatic first response to a missed milestone. Most university license agreements structure a graduated set of remedies, roughly in order of severity:

1. Notice and cure period. The institution notifies the licensee of the missed milestone; the licensee has a defined window (commonly 30-90 days, sometimes longer for milestones requiring substantial new work) to cure — either by meeting the milestone late or by presenting a revised, mutually acceptable development plan.
2. Milestone extension or renegotiation. If the licensee shows documented good-faith development effort and a credible reason for the delay, many agreements allow the parties to agree on a revised milestone date rather than triggering a default, sometimes in exchange for an additional payment or an accelerated later milestone.
3. Conversion from exclusive to non-exclusive. Rather than terminating the license outright, the institution converts the licensee’s rights from exclusive to non-exclusive, preserving the licensee’s existing position while restoring the institution’s ability to license the same technology to others. This is a common middle-ground remedy because it punishes the failure to commercialize without destroying the licensee’s sunk investment in whatever development work it has already done.
4. Field- or territory-specific termination (a “field carve-back”). If the license spans multiple fields of use or territories and the licensee is only failing to commercialize in some of them, the institution terminates the license in the underperforming field(s)/territory(ies) only, leaving the rest of the grant intact. This tracks the field-of-use logic covered in CASRAI’s field-of-use restrictions guide — diligence milestones are frequently set on a per-field basis for exactly this reason, so that underperformance in one field doesn’t automatically put the whole license at risk.
5. Full termination. Reserved for a licensee that has failed to cure after notice, shown no good-faith development effort, or missed a foundational early milestone (e.g., never actually starting development). Full termination returns all licensed rights to the institution, subject to whatever survival clause covers accrued royalties, confidentiality, and — where sublicenses exist — sublicensee step-in rights.

Which of these a given agreement uses, and in what order, is itself a negotiated point. Licensees generally push for graduated remedies (extension, then conversion) before termination becomes available at all; institutions — particularly for a technology with real market interest from other parties — push for a shorter path to at least a field-specific termination right, since the cost of a stalled exclusive license compounds the longer it sits unaddressed.

Drafting the Termination-for-Failure-to-Commercialize Clause Itself

The termination clause that operationalizes all of the above typically needs to specify, precisely:

• What counts as a diligence failure — usually cross-referenced directly to the milestone schedule or development plan (as an exhibit/appendix to the agreement) rather than restated in the termination clause itself, so the two stay in sync if milestones are later amended.
• Notice requirements — written notice, specifying which milestone was missed and by how long.
• The cure period length — and whether it differs from the general breach cure period elsewhere in the agreement (diligence cure periods are often longer, since curing usually means completing substantive development work, not simply paying an overdue invoice).
• Whether the remedy is automatic or discretionary — some clauses give the institution the right, but not the obligation, to terminate or convert on a missed milestone (preserving flexibility if the institution would rather negotiate than terminate); others make a specific consequence automatic once the cure period lapses.
• Post-termination obligations — return or destruction of confidential materials, survival of accrued payment obligations, and, if sublicenses exist, whether sublicensees can step into a direct license with the institution rather than losing their rights when the head license terminates for the head licensee’s own diligence failure (a scenario sublicensees will specifically negotiate protection against, since it is otherwise entirely outside their control).

Because a termination-for-failure-to-commercialize clause operates independently of the agreement’s general breach/cure provisions, it is normally drafted as its own numbered section rather than folded into the standard “Termination for Breach” clause — see the structural walkthrough in CASRAI’s license agreement structure guide for where this sits in a full agreement’s clause sequence.

How This Differs From Bayh-Dole March-In Rights

It’s worth being precise about a distinction that’s easy to blur: diligence and termination-for-failure-to-commercialize clauses are a contractual remedy the institution itself holds against its licensee. March-in rights under 35 U.S.C. § 203 are a separate, statutory remedy the federal funding agency holds against the institution (the contractor), exercisable only in narrow circumstances and, in practice, exceedingly rarely invoked. A licensee failing to hit a milestone is a routine, contract-level event the institution handles directly under its own license agreement; it does not by itself trigger a federal march-in proceeding, and march-in has essentially never been successfully exercised despite periodic petitions asking an agency to do so. The two mechanisms serve a related policy goal — inventions reaching practical use — but operate at different levels and with very different procedural weight. An institution’s diligence clause is the mechanism that, in the overwhelming majority of cases, does the actual enforcement work.

Negotiation Dynamics: What Each Side Actually Wants

Diligence and termination provisions are consistently among the more heavily negotiated sections of a university exclusive license, because the two sides’ interests are directly opposed on several specific points:

• Milestone specificity. Institutions want dated, objective, checkable milestones; licensees — especially early-stage startups with genuinely uncertain development timelines — want language flexible enough to survive an unpredictable R&D or regulatory path without triggering a default through no fault of their own.
• Consequence severity. Institutions want termination or at least field-specific conversion available relatively early; licensees want graduated remedies and generous cure periods, particularly for a well-capitalized, actively-developing licensee that simply hit an unanticipated technical setback.
• Extension mechanics. How easy it is to get a missed milestone date pushed back, and on what showing, is often a bigger practical battleground than the milestone dates themselves — a lenient extension mechanism can functionally neutralize an otherwise strict milestone schedule.
• Startup-specific accommodation. A cash-constrained university spinout may negotiate for milestones tied to funding events (e.g., closing a Series A) rather than fixed calendar dates, or for a longer initial development period before the diligence clock starts running, in recognition that spinouts often need time to secure capital before substantive development work can begin — see CASRAI’s guide to university spinout companies for the broader spinout-formation context this negotiation typically sits within.

Institutions weigh these requests against a real cost: an unenforceable or endlessly extendable diligence clause functionally converts an exclusive license into an option the licensee can hold indefinitely without developing the technology — precisely the outcome the clause exists to prevent.

Frequently Asked Questions

Do non-exclusive licenses need diligence clauses?

Rarely, and when they appear at all they’re typically far lighter. Because a non-exclusive license doesn’t block the institution from licensing the same technology to other parties, the institution’s exposure to one licensee’s inaction is much lower — there’s no exclusivity being “wasted” while the technology sits undeveloped. Diligence and termination-for-failure-to-commercialize provisions are, in practice, almost exclusively a feature of exclusive (and sometimes sole) licenses.

What happens to a milestone schedule if the licensee is acquired?

This depends on the agreement’s assignment clause, but the milestone schedule itself typically survives an acquisition unchanged unless the agreement is amended — an acquiring company takes on the existing license, including its diligence obligations, as part of what it acquires. Some agreements require the institution’s consent before an assignment via acquisition takes effect, partly so the institution can assess whether the acquirer intends to continue development or is more likely to shelve the technology, which is itself a diligence-adjacent risk.

Can a licensee negotiate diligence milestones out of the agreement entirely?

For an exclusive license, this is uncommon — most institutions treat some form of diligence obligation as a non-negotiable floor precisely because of the exclusivity/commercialization-mandate concern described above. What is negotiable is the specificity, generosity, and consequence structure of the milestones themselves, not usually whether any diligence obligation exists at all.

Is a missed milestone the same thing as a material breach of the license?

Not necessarily, and well-drafted agreements keep the two concepts distinct. A missed milestone triggers whatever specific remedy the diligence/termination clause specifies (notice, cure, conversion, field carve-back, or termination, per the schedule above); it does not automatically constitute the kind of general material breach that would trigger the agreement’s separate breach-and-cure provisions, unless the agreement specifically says diligence failures are treated as a material breach. Treating the two as identical in drafting can produce unintended results, since general breach clauses are often written with different cure periods and consequences in mind.

For the rest of a license agreement’s clause structure, see CASRAI’s guide to license agreement structure. Related clause-level deep dives: field-of-use restrictions, MFN and anti-stacking clauses, and grant-back and improvement clauses. For the government’s own separate remedy, see Bayh-Dole march-in rights. For the negotiation economics of exclusivity generally, see CASRAI’s patent licensing guide and the exclusive vs. non-exclusive license comparison. For the full cluster, see the Technology Transfer & Innovation pillar.