Bayh-Dole March-In Rights: The Process for Government-Directed Licensing of Federally Funded Inventions

Why This Case Is Included

March-in rights under the Bayh-Dole Act are a governance process that turns broad statutory standards into case-by-case licensing decisions. The mechanism is structurally useful because it combines (1) legal constraints written as open-ended triggers, (2) agency discretion over fact-finding and interpretation, (3) internal and external oversight pathways (petitions, administrative records, review), and (4) downstream accountability questions about when the government will actually use the tool versus rely on informal pressure or negotiated outcomes.

This site does not ask the reader to take a side; it documents recurring mechanisms and constraints. This site includes cases because they clarify mechanisms — not because they prove intent or settle disputed facts.

What Changed Procedurally

GAO-26-107885 is framed around guidance on government licensing claims under Bayh-Dole, which matters procedurally because march-in rights sit in a broader set of government patent-related authorities that can be confused or blended in practice. Even when the statute is unchanged, procedure can shift through clarification of:

• Which authority is being invoked (Bayh-Dole march-in vs. the government’s nonexclusive license vs. other federal authorities affecting patent use).
• What evidentiary record is expected (utilization reporting, commercialization timelines, supply constraints, manufacturing location, health/safety needs).
• Where decision authority sits inside an agency (program office vs. technology transfer office vs. general counsel vs. political leadership), which shapes internal review and risk posture.
• How “standards” are operationalized without numeric thresholds (e.g., what qualifies as “practical application” or unmet “health or safety needs”).

Some of these details vary by agency and by the terms of the specific funding agreement. Where GAO summarizes agency practices, the case indicates patterns, not universal rules.

Why This Illustrates the Framework

Bayh-Dole’s march-in right (35 U.S.C. § 203) illustrates a recurring framework problem: a high-stakes power is available, but its application depends on standards that do not resolve into a simple checklist. That creates a predictable institutional pattern:

• Pressure without censorship: the existence of march-in can shape negotiations and behavior without a formal order being issued. Formal march-in is not required for the tool to matter; the possibility affects bargaining.
• Accountability becomes negotiable: agencies can point to the statutory test while still exercising discretion over how much evidence is “enough,” how long review takes, and what alternatives count as satisfying the public interest.
• No overt rule change required: interpretive guidance, internal review posture, and case selection can shift outcomes while leaving the statute intact.

This matters regardless of politics. The same mechanism appears anywhere an agency holds a latent enforcement or licensing power that is triggered by qualitative standards and exercised through a multi-step review record.

How to Read This Case

Not as:

• proof that any specific patent holder acted improperly,
• a verdict on whether a particular product price, supply, or access problem is “sufficient” to trigger march-in,
• a claim that agencies will or will not use march-in in future cases.

Instead, watch for:

• Where discretion enters: how an agency defines “practical application,” “reasonable terms,” “health or safety needs,” and “public use requirements.”
• How standards bend without breaking: the statute provides triggers, but agencies must translate them into measurable findings and defensible administrative records.
• Which incentives and constraints dominate: agencies face litigation risk, innovation-policy concerns, interagency coordination limits, and timing constraints that can produce delay or narrow interpretations.

The basic mechanism: what march-in is (and is not)

Under Bayh-Dole, contractors (often universities, nonprofits, and small businesses) can elect to retain title to inventions developed with federal funding, subject to conditions. The government typically receives at least a nonexclusive, nontransferable, irrevocable, paid-up license to practice the invention for or on behalf of the United States. March-in is different: it is a conditional authority for an agency to require licensing to third parties (or to license itself) when statutory triggers are met and the contractor has not adequately addressed them.

March-in is best read as a backstop authority: it sits behind a set of default allocations (contractor title + government license) and activates only through a structured review.

The trigger structure: standards without thresholds

Bayh-Dole’s march-in triggers are written as standards rather than numeric thresholds. Commonly cited triggers include:

• Failure to achieve “practical application”: whether the invention is being utilized and available to the public on “reasonable terms.”
• Health or safety needs: whether action is necessary to alleviate needs not reasonably satisfied.
• Public use requirements: whether requirements set by federal regulations are met.
• U.S. manufacturing preference (for exclusive licenses to use or sell in the U.S.): whether domestic manufacturing requirements are met, absent waiver.

Each trigger requires interpretation. For example, “reasonable terms” can be argued to include price, supply reliability, licensing breadth, or other access conditions; agencies have historically been cautious about converting that phrase into a price-control mechanism, but future interpretations can vary. Where the report discusses “guidance,” the key procedural insight is that guidance can narrow or broaden how these standards are translated into reviewable findings.

The procedural pathway: how a march-in question becomes a decision

A simplified, mechanism-focused pathway looks like this (details can vary by agency and case):

1. Initiation
   • A petition from an outside party, an internal agency review, or an interagency referral raises a march-in question.
2. Authority check
   • The agency determines whether Bayh-Dole applies (federal funding, subject invention, contractor status, applicable funding agreement terms).
3. Fact development / record building
   • The agency requests information (e.g., utilization, efforts to commercialize, manufacturing location, licensing posture, supply constraints).
4. Notice and response
   • The contractor is typically given notice and an opportunity to respond; procedures may include an evidentiary hearing.
5. Trigger analysis
   • The agency applies the statutory standard to the record (often the most discretionary step).
6. Remedy selection
   • If march-in is justified, the agency can require licensing on reasonable terms to responsible applicants; if the contractor refuses, the agency may grant licenses itself.
7. Review / challenge
   • The decision may be subject to internal appeals and judicial review, depending on the posture and governing administrative-law pathways.

Two practical implications flow from this pathway:

• Delay is a feature: because the agency needs a defensible record and must manage procedural fairness, march-in is rarely a rapid intervention.
• The remedy is indirect: the tool works by altering licensing rights rather than directly ordering production, pricing, or distribution (though licensing can affect all three).

The broader “government licensing claims” frame

GAO’s focus on “government licensing claims” matters because Bayh-Dole march-in can be conflated with other tools. In practice, agencies and stakeholders may discuss “government rights in patents” as a single bucket, even though the mechanisms differ:

• Government’s paid-up license (default Bayh-Dole right): lets the government use the invention for government purposes.
• March-in (conditional Bayh-Dole right): compels or enables licensing to others when triggers are met.
• Exceptional circumstances determinations (Bayh-Dole-related): can alter default allocations in advance for a class of funding agreements.
• Other federal authorities (outside Bayh-Dole): can affect government use of patented inventions, contracting outcomes, or compensation rules, depending on context.

A recurring gray zone is the boundary between (a) asserting an existing government license for governmental use and (b) attempting to leverage march-in-like outcomes through contract negotiation, procurement decisions, or interpretive guidance. GAO-style guidance can reduce confusion by separating these mechanisms and clarifying the procedural prerequisites for each.

Where to go next

• Start Here
• The Framework
• Governance
• Why pressure beats censorship