Bayh-Dole March-In Rights: What They Mean for University Tech Transfer

March-in rights are the enforcement provision of the Bayh-Dole Act that lets a federal funding agency require the holder of a patent on a federally funded invention to grant additional licenses — or, if the holder refuses, to grant one itself — to a third party. For a university technology transfer office (TTO), march-in has long been less a live operational risk than a background condition that shapes how licenses get drafted, how commercialization diligence gets documented, and how a TTO should be prepared to respond if a petition ever names one of its licenses — though a 2025 Commerce Department compliance proceeding against Harvard University, covered later in this guide, is the closest the mechanism has ever come to an actual test, even though no march-in has been exercised there or anywhere else. This guide covers the full petition history, the formal regulatory procedure an agency must follow, and what it practically means for TTO license drafting and diligence practice. For the underlying statute and government-retained-rights framework generally, see CASRAI’s Bayh-Dole Act entry; for the statutory conditions and the most-litigated case (Xtandi) in more definitional depth, see the March-In Rights dictionary term.

The legal basis: 35 U.S.C. § 203

Bayh-Dole (35 U.S.C. §§ 200–212, enacted 1980) lets universities, nonprofits, and small businesses elect to retain title to inventions made with federal research funding, in exchange for specific obligations — timely invention disclosure, an election-of-title window, a patent-filing deadline, and commercialization diligence. Section 203 is the government’s backstop if that diligence doesn’t happen: an agency may march in only if at least one of four conditions is met — the title-holder has not taken (or is not expected to take) effective steps toward practical application; action is needed to meet health or safety needs the holder isn’t reasonably satisfying; action is needed to meet public-use requirements specified by federal regulation; or the holder hasn’t obtained (or complied with, or been waived from) the U.S.-manufacturing agreement required under 35 U.S.C. § 204 for an exclusive license to sell in the United States. Meeting one condition makes march-in eligible, not automatic — the funding agency retains full discretion over whether to actually act, and to date every agency asked has declined.

The formal procedure: 37 CFR § 401.6

March-in is not a court action in the first instance — it is an agency administrative process, set out at 37 CFR § 401.6, and it is deliberately slow. The regulatory sequence a TTO should understand, because each stage carries a real notice obligation and response window:

1. Informal notice. Before initiating any formal march-in proceeding, the agency must notify the contractor (the university or institution holding title) in writing of the information it has received and request an informal consultation to resolve the matter. The contractor has a real, if short, opening to respond before anything becomes formal.
2. 30-day window. If the contractor doesn’t respond, or the informal consultation doesn’t resolve the concern, the agency may proceed to a formal march-in proceeding.
3. Formal proceeding and written determination. The agency investigates whether a statutory condition is met, gives the title-holder (and any exclusive licensee whose rights would be affected) notice and an opportunity to be heard, and issues a written determination.
4. Appeal. A title-holder or affected licensee can appeal an adverse determination within the agency; if the agency’s final decision still goes against them, 35 U.S.C. § 203(b) gives 60 days to seek review at the U.S. Court of Federal Claims.

No march-in petition has ever proceeded past the agency-decision stage on the merits of an actually-granted march-in — every agency that has been petitioned has declined at step 3, so the appeal mechanism has never been tested against a real march-in grant. A 2025 Commerce Department proceeding against Harvard University (discussed below) differs from this petition-driven pattern in its origin — it was agency-initiated, not petitioner-triggered — but, as of this writing, it likewise has not resulted in an actual march-in grant.

The full petition history, not just Xtandi

Xtandi is the best-known case, but it’s the fourth in a line of march-in petitions stretching back to 1997 — useful context for a TTO because the pattern (petition filed, agency investigates, agency declines, price alone rejected as sufficient grounds) has now repeated for nearly three decades under multiple administrations:

• CellPro (1997). CellPro petitioned HHS to march in on stem-cell separation patents held by Johns Hopkins University and licensed to Baxter Healthcare/Becton Dickinson, arguing Johns Hopkins hadn’t effectively commercialized the invention. NIH declined, finding the university’s commercialization efforts — while slower than CellPro’s own competing product — were reasonable.
• Norvir / ritonavir (2004). AIDS patient-advocacy groups petitioned NIH to march in on Abbott Laboratories’ patents covering ritonavir (Norvir) after Abbott raised the U.S. price roughly fivefold, arguing the drug was no longer available on “reasonable terms.” NIH held that march-in is not an appropriate mechanism for controlling prices and declined.
• Fabrazyme (2010). Patients with Fabry disease petitioned HHS after Genzyme’s manufacturing problems forced it to ration Fabrazyme to a fraction of the recommended dose. The petition centered on a genuine supply shortfall rather than price, but HHS still declined to march in, citing steps Genzyme was already taking to resolve the shortage.
• Xtandi (2016 and 2021–2022). Knowledge Ecology International and Universities Allied for Essential Medicines twice petitioned HHS over enzalutamide (Xtandi), a prostate-cancer drug developed at UCLA with NIH/DoD funding and licensed to Astellas, arguing its roughly 4x higher U.S. price met the practical-application and health-or-safety conditions. NIH denied the petition in March 2023, reasoning that Xtandi was already widely available and that a march-in proceeding’s timeline made it an ineffective tool to lower price given the patents’ remaining life; HHS affirmed on appeal.

Every petition on record involves a drug patent, not a university-held research tool, software, or device patent — the pattern to date is specific to pharmaceutical pricing and access disputes, not technology transfer generally. That doesn’t make march-in irrelevant to a TTO handling, say, a diagnostics or ag-biotech license, but it does mean the realistic exposure is concentrated in life-sciences licensing with a public-health angle.

The 2025 Harvard proceeding: the closest march-in has come

In August 2025, the four-decade petition pattern above was broken in a new way. On August 8, 2025, Commerce Secretary Howard Lutnick sent a letter to Harvard University President Alan Garber alleging that Harvard had failed to meet several Bayh-Dole obligations across its portfolio of federally funded inventions — including untimely invention disclosure and title election, noncompliance with the Section 204 U.S.-manufacturing preference, and failure to achieve practical application for some inventions — and asserting that a march-in process under Section 203 was being initiated. Harvard was given until September 5, 2025 to submit a detailed, portfolio-wide report of its federally funded patents. Unlike every prior matter, this proceeding was not triggered by an outside petition; the Department of Commerce initiated it directly, and scoped it to Harvard’s entire patent portfolio rather than a single license.

As of the most recent public reporting, the matter remains at the compliance-review and notice stage: no march-in license has been reported as granted or exercised, and Harvard’s substantive response and any final agency determination were not publicly available. A TTO reading about this matter should keep two claims distinct: a march-in proceeding being opened against Harvard is now real and unprecedented in scope and origin; march-in rights being exercised — an actual compelled license — still has never happened, in this matter or any other, in the more than four decades since Bayh-Dole was enacted. See CASRAI’s dedicated coverage of the Harvard Bayh-Dole march-in proceeding for the full timeline, the specific allegations, and an open jurisdictional question over whether Commerce (as opposed to the specific agencies that actually funded the research at issue) has authority to initiate march-in at all.

The unresolved question: can price alone trigger march-in?

Every march-in denial to date, including Xtandi, has rested in part on agencies holding that price alone is not a valid basis for march-in — commercialization and availability are the statutory tests, not pricing. In December 2023, the National Institute of Standards and Technology (NIST) released a draft Interagency Guidance Framework for Considering the Exercise of March-In Rights, proposing that price relative to comparable alternatives could be weighed as a factor bearing on whether the practical-application or health-and-safety conditions are met — a real departure from that consistent prior position. The framework drew a very large public comment volume and remains unfinalized and non-binding as of this writing. Because this is one of the fastest-moving, most contested pieces of Bayh-Dole policy, a TTO relying on it for current guidance should re-verify its status directly (via NIST’s Bayh-Dole program page) rather than treat this guide’s description of it as current beyond its publication date.

What march-in rights are not

Three distinct Bayh-Dole mechanisms get conflated with march-in and are worth a TTO keeping straight:

• Title forfeiture is a separate remedy under 37 CFR § 401.14(d)(1) for a recipient’s procedural failure — not disclosing an invention, not electing title within the statutory window, or not filing a patent application in time. Forfeiture is about the recipient’s own compliance failure; march-in is about inadequate commercialization of an invention whose title was validly retained.
• The government’s own royalty-free use license under 35 U.S.C. § 202(c)(4) exists automatically from the moment a subject invention is made, worldwide, with no petition or agency finding required. It lets the government itself practice the invention; march-in, by contrast, is a discretionary action that grants rights to a third party, and only after a formal determination.
• An antitrust or price-control tool. Despite drug-pricing petitions driving most public attention to march-in, no agency has ever granted one on pricing grounds — that’s exactly the open question the unfinalized NIST framework is trying to resolve, not a settled use of the authority today.

What this means practically for a TTO’s license drafting and diligence practice

Given the near-30-year record of zero actual march-ins, the practical relevance for most TTOs isn’t defending against an active petition — it’s the documentation discipline that keeps a license eligible-but-unlikely to ever face one, and that gives the institution a strong factual record if a petition is ever filed:

• Build commercialization diligence obligations into the license itself. Concrete, dated milestones (regulatory filings, first commercial sale, minimum sales/royalty thresholds, sublicense-out deadlines) give the licensee a compliance framework and give the institution a documented, ongoing record of effective steps toward practical application — the exact standard march-in petitions have to overcome. See CASRAI’s guide to license agreement structure for where diligence and milestone clauses typically sit in the document.
• Enforce the diligence clauses you write. A milestone clause that’s never actually tracked or enforced weakens the institution’s factual position if a petition is ever filed — the point isn’t the clause’s existence, it’s a real compliance record behind it.
• File complete, timely iEdison utilization reports. Annual utilization reporting through the federal iEdison system is where an agency first sees whether a licensed invention is actually reaching the market — a thin or late utilization report is a self-inflicted weakness on exactly the question march-in turns on.
• Keep the domestic-manufacturing question resolved, not deferred. For any exclusive license to sell or use a subject invention in the United States, confirm the § 204 U.S.-manufacturing agreement is in place, formally waived, or otherwise compliant before execution — a gap here is a standalone, independently sufficient march-in condition, distinct from the commercialization-pace question altogether.
• If a march-in inquiry does arrive, treat the informal-consultation stage as the real opportunity. Under 37 CFR § 401.6, the agency is required to raise its concern informally before any formal proceeding begins. That is the point to marshal the institution’s diligence and utilization-reporting record — not after a formal proceeding has already started.
• Flag life-sciences and public-health-adjacent licenses for extra diligence-clause rigor. Every petition on record to date targets a pharmaceutical patent; a TTO licensing therapeutics, diagnostics, or vaccine technology carries meaningfully more realistic exposure than one licensing, say, engineering software or a materials-science patent, even though the statute applies identically to both.

None of this is defending against a likely event — it’s the same diligence and reporting discipline a well-run TTO should maintain regardless of march-in, described here at exactly the point where Bayh-Dole gives it statutory teeth.

Frequently asked questions

Has march-in ever actually been exercised?

No. Every documented petition — CellPro (1997), Norvir (2004), Fabrazyme (2010), and the two Xtandi petitions (2016, 2021–2022) — was denied by the funding agency at the administrative-determination stage. No case has reached the U.S. Court of Federal Claims on the merits of an actually-granted march-in. In August 2025, the Department of Commerce opened the first agency-initiated, portfolio-wide Bayh-Dole compliance and march-in proceeding, targeting Harvard University — the closest the mechanism has come to an actual test. As of this writing that proceeding also remains unresolved, with no march-in exercised; see CASRAI’s coverage of the Harvard Bayh-Dole march-in proceeding for details.

Can march-in be used purely to lower a drug’s price?

Not under current agency practice. Every denial to date, including Xtandi, has held that price alone doesn’t satisfy the statutory conditions. NIST’s December 2023 draft framework proposes weighing price as a relevant factor, but it remains unfinalized and non-binding — verify its current status before relying on it.

Does march-in affect inventions the institution hasn’t elected to keep title to?

No. March-in is a check on a title-holder’s use of a subject invention. If the university doesn’t elect title (or the agency takes title through the separate forfeiture process for a disclosure/filing failure), march-in doesn’t apply because there’s no retained title to march in against.

Who can file a march-in petition?

Any interested party — historically patient-advocacy groups, public-interest organizations, competitors, or members of Congress acting on a constituent’s behalf. The funding agency, not the petitioner, decides whether to act.

How does march-in relate to the government’s existing license rights?

They’re separate. The government already holds a royalty-free license to practice any subject invention itself under 35 U.S.C. § 202(c)(4), automatically and without a petition. March-in is a distinct, discretionary mechanism to extend rights to a third party, not the government itself, and only after a formal agency determination.

For the license-drafting mechanics referenced above, see CASRAI’s guides to license agreement structure, patent licensing, and the technology transfer process. For the invention-disclosure and title-election steps that precede a license, see invention disclosure and the Technology Licensing Office (TLO) entry. Return to the tech transfer pillar for the cluster’s full coverage.