Examples
Worked examples
- Is an instance
A public-interest group petitions HHS to march in on a federally funded drug patent, arguing the licensee is not meeting unmet health needs because of the drug's U.S. price relative to other countries -- the 2016 and 2021-2022 Xtandi (enzalutamide) petitions to NIH/HHS are the best-documented real instance of this pattern.
- Is an instance
An agency's own march-in regulations (e.g., 37 CFR part 401 for most civilian agencies) set out the procedural steps -- petition, agency investigation, notice to the title-holder, an opportunity to respond, and a written determination -- that must occur before any march-in decision, even one that ultimately denies the petition.
Counter-examples
Looks similar, but isn't
- Not an instance
An agency taking title to an invention because the recipient failed to disclose it or elect title in time is title forfeiture under 37 CFR 401.14(d)(1), not march-in -- a different remedy for a different, procedural failure.
- Not an instance
The government exercising its own automatic, royalty-free license to practice a subject invention under 35 U.S.C. 202(c)(4) is not march-in -- that license requires no petition, no agency finding, and benefits the government itself rather than a third-party licensee.
Editorial commentary
Note: this term extends the government-retained-rights coverage already on the Bayh-Dole Act page with a fuller treatment of march-in specifically — the statutory conditions, the petition process, a real worked example, and the current status of the contested 2023 NIST pricing framework.
March-in rights are the enforcement mechanism written into the Bayh-Dole Act at 35 U.S.C. § 203: the statutory authority letting a federal funding agency require the holder of a patent on a federally funded “subject invention” to grant additional licenses — or, if the holder refuses, to grant a license itself — to a responsible third party. It is one of several rights the government retains under Bayh-Dole even after a university, nonprofit, or small business has elected to keep title to an invention it developed with federal funds. March-in does not transfer or revoke that title; it compels additional, non-exclusive-or-broader licensing around it under narrow, statutorily defined circumstances.
What makes something an instance of march-in rights
An agency may only invoke Section 203 if the title-holder is not already satisfying at least one of four statutory conditions:
- Practical application. The holder has not taken, and is not expected within a reasonable time to take, effective steps to achieve practical application of the invention — i.e., to make its benefits reasonably available to the public.
- Health or safety needs. Action is necessary to alleviate health or safety needs that are not reasonably satisfied by the holder.
- Public-use requirements. Action is necessary to meet requirements for public use specified by federal regulation, and those requirements are not reasonably satisfied.
- U.S.-manufacturing agreement. The holder has not obtained the domestic-manufacturing agreement required for an exclusive license to sell or use the invention in the United States under 35 U.S.C. § 204, or has not obtained a waiver of it, or has not complied with it.
A single satisfied condition is enough to trigger eligibility for march-in; the agency is not required to find all four. But eligibility is not the same as a march-in actually being granted — the agency retains discretion, and as discussed below, no federal agency has ever exercised march-in rights to actually compel a license, even where petitioners argued one or more conditions were met. A 2025 Commerce Department proceeding against Harvard University, discussed below, is the closest any matter has come, but it too remains unresolved as of this writing, with no march-in granted.
How a march-in proceeding works
The process is agency-driven and procedurally slow by design:
- Any party (commonly a public-interest organization, a patient-advocacy group, or a member of Congress acting on a constituent’s behalf) can petition the funding agency to exercise march-in.
- The funding agency — not a court, in the first instance — investigates and decides whether one of the four conditions is met and whether march-in is warranted.
- The title-holder receives notice and an opportunity to respond before any determination.
- If the agency does move to march in, the title-holder (or an exclusive licensee whose rights would be affected) can appeal within the agency, and a party adversely affected by a final agency march-in decision has 60 days to seek review at the U.S. Court of Federal Claims.
In practice, every march-in petition filed to date has ended at the agency-decision stage: the funding agency has declined to march in, so the appeal-to-the-Court-of-Federal-Claims step has never actually been reached on the merits of a granted march-in. A 2025 Commerce Department proceeding against Harvard University breaks from this petition-driven pattern — it was agency-initiated rather than triggered by an outside petition — but, as of this writing, it too remains open rather than resolved, and no march-in has been granted (see below).
Worked example: the Xtandi petitions
The most litigated real-world test of march-in rights concerns enzalutamide (marketed as Xtandi), a prostate-cancer drug developed with NIH and Department of Defense funding at the University of California, Los Angeles and licensed to Astellas Pharma. Beginning in 2016 and again in 2021-2022, advocacy groups including Knowledge Ecology International and Universities Allied for Essential Medicines petitioned the Department of Health and Human Services to march in on the Xtandi patents, arguing the drug’s U.S. price — reported at roughly four times the price charged in other high-income countries — meant the “practical application” and “health or safety needs” conditions were met. In March 2023, NIH denied the petition, stating that Xtandi was widely available on the market and that, given the patents’ remaining life and the length of a march-in proceeding, using march-in authority would not be an effective way to lower the drug’s price. HHS affirmed that denial on appeal. The Xtandi case remains the clearest illustration both of how the four statutory conditions get argued in practice and of how consistently, so far, agencies have declined to march in even when petitioners frame a case as meeting them.
The 2025 Harvard compliance proceeding: the closest test yet
In August 2025, the Department of Commerce opened a Bayh-Dole compliance review of Harvard University’s entire portfolio of federally funded inventions and asserted that a march-in process under Section 203 was being initiated — the first time any march-in matter has been agency-initiated rather than triggered by an outside petition, and the first scoped to an institution’s whole patent portfolio rather than a single license. On August 8, 2025, Commerce Secretary Howard Lutnick wrote to Harvard President Alan Garber alleging 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 set a September 5, 2025 deadline for Harvard to submit a detailed portfolio report. 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, and no final agency determination has been made public. It is the most significant real-world test the march-in mechanism has faced since Bayh-Dole’s 1980 enactment, but — consistent with every matter described above — it has not resulted in march-in rights actually being exercised. See CASRAI’s dedicated coverage of the Harvard Bayh-Dole march-in proceeding for the full timeline and open questions, including whether Commerce has authority to initiate march-in for inventions funded by other agencies.
The 2023 NIST draft framework on price
In December 2023, the National Institute of Standards and Technology released a draft Interagency Guidance Framework for Considering the Exercise of March-In Rights, proposing that agencies could weigh a product’s price, relative to comparable alternatives, as one factor bearing on whether the “practical application” or “health and safety” conditions are met — a significant departure from the position, taken consistently by NIH in the Xtandi denials and by prior administrations, that price alone is not a valid basis for march-in. The comment period drew tens of thousands of submissions. As of this writing the framework remains in draft, unfinalized form; it has not been adopted as binding agency policy. Anyone citing the framework’s status should re-check it directly, since it is one of the more actively contested and fastest-moving pieces of Bayh-Dole policy.
What march-in rights are not
March-in is easy to conflate with other Bayh-Dole mechanisms it is not:
- Not title forfeiture. A funding agency can separately take title to an invention if the awardee fails to disclose it, fails to elect title within the statutory window, or fails to file a patent application in time (37 CFR § 401.14(d)(1)). That is a distinct remedy for a procedural failure by the recipient; march-in addresses inadequate commercialization or availability of an invention whose title the recipient validly holds.
- Not the government-use license. Under 35 U.S.C. § 202(c)(4), the government automatically keeps a royalty-free license to practice any subject invention itself, worldwide, regardless of who holds title. That license exists from the moment the invention is made and requires no petition or agency finding — march-in, by contrast, is a discretionary, conditions-triggered action benefiting a third party, not the government.
- Not an antitrust or price-control tool in current practice. Despite the drug-pricing petitions that have driven most public attention to march-in, no agency has yet granted a march-in on pricing grounds alone, and whether price can properly support a march-in determination is exactly what the unfinalized NIST framework is contesting.
Why it matters for research administration
March-in rights are rarely exercised but shape how technology transfer offices negotiate and document licenses: because an unexercised statutory threat still exists, many license agreements for federally funded inventions include explicit commercialization milestones, diligence obligations, and reporting requirements that are, in part, designed to demonstrate the “effective steps toward practical application” that keeps march-in eligibility from arising in the first place. Understanding march-in is also essential context for anyone tracking the broader drug-pricing and IP-policy debate, since it is one of the few statutory levers a funding agency has to act on an invention’s commercial terms after title has already passed to a university or company.
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="March-In Rights"
vocab-term-identifier="https://casrai.org/dictionary/term/march-in-rights" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/march-in-rights",
"name": "March-In Rights",
"identifier": "https://casrai.org/dictionary/term/march-in-rights",
"description": "March-in rights are the authority under 35 U.S.C. § 203 letting a federal funding agency require the holder of a patent on a federally funded “subject invention” to grant additional licenses to a responsible third party -- or grant one itself -- when the holder isn't achieving practical application, isn't meeting unmet health/safety needs, isn't satisfying regulation-specified public-use requirements, or hasn't met the Section 204 U.S.-manufacturing agreement. Title is not transferred or revoked; only additional licensing is compelled, and only at the funding agency's discretion after a petition and agency review.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/compliance-regulatory#set",
"url": "https://casrai.org/dictionary/term/march-in-rights",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"dateModified": "2026-07-24T07:43:53",
"inLanguage": "en"
}
