Last verified: August 16, 2026. This page explains Other Transaction (OT) authority as a general federal award instrument for research administrators evaluating an OT agreement (OTA) alongside a grant or contract offer. It is not legal advice — the specific terms of any OT agreement are negotiated document by document, and your institution’s sponsored programs office and general counsel should review the actual agreement text before signing.
What “Other Transaction Authority” means
Other Transaction (OT) authority is statutory authority Congress has given to specific federal agencies to enter into agreements that are, by design, not procurement contracts, grants, or cooperative agreements. The name is literal: an “other transaction” is legally defined by what it is not. Agencies use OT authority when the standard instruments — bound by the Federal Acquisition Regulation (FAR) for contracts, or by 2 CFR Part 200 (the Uniform Guidance) for grants and cooperative agreements — are seen as too rigid, slow, or unattractive to reach commercial and non-traditional performers who would otherwise not compete for federal work at all.
For a university research office, the practical framing is this: an OT agreement is a negotiated, largely non-standard contract awarded by a federal agency for research, prototyping, or production, where the agency has deliberately opted out of most of the regulatory scaffolding that normally comes with federal money. That flexibility is the entire point of the authority — and it is also exactly what makes an OT agreement a different risk profile to manage than a grant.
Which agencies hold OT authority, and for what
OT authority is not one law — it is a patchwork of separate statutory grants, each agency-specific, each with its own scope and dollar thresholds. There is no single “Other Transaction Act.” The best-established and most litigated authority is the Department of Defense’s:
- DoD — research OTs, codified at 10 U.S.C. § 4021 (renumbered from the former 10 U.S.C. § 2371, following the Title 10 recodification), for basic, applied, and advanced research projects.
- DoD — prototype and follow-on production OTs, codified at 10 U.S.C. § 4022 (formerly § 2371b), for prototype projects directly relevant to enhancing the mission of DoD, with a statutory ceiling of $500 million per prototype OT, and follow-on production OTs (awarded without further competition to the same performer that completed the prototype) capped at $100 million unless waived.
- NASA — under 51 U.S.C. § 20113(e), used for programs such as Commercial Orbital Transportation Services (COTS) and Commercial Crew.
- DOE — under provisions of the DOE Organization Act (42 U.S.C. § 7256 and related sections), used by ARPA-E and by EERE/IARPA-adjacent programs for R&D and demonstration agreements.
- HHS / BARDA — under 42 U.S.C. § 247d-7e (Public Health Service Act §319L, added by the Pandemic and All-Hazards Preparedness Act), used for medical countermeasure development where speed and access to non-traditional biotech/pharma performers matters more than procurement uniformity.
- DHS, FAA, and NIH each hold narrower OT-like authorities, granted through their own enabling or appropriations legislation, generally scoped to research and technology-demonstration work rather than production. ARPA-H, created in 2022 within HHS, was built around OT-style flexible agreements from the outset as its primary funding mechanism, reflecting the DARPA model it is explicitly patterned on.
The Congressional Research Service tracks OT authority centrally in its “Defense Primer” series and periodic reports on alternative acquisition mechanisms; GAO has issued multiple reports evaluating how DoD and other agencies use the authority. Because each grant of authority is separate legislation, the purposes, dollar caps, and required findings differ by agency — always confirm the specific statute cited in the solicitation or agreement rather than assuming DoD’s rules apply elsewhere.
Research, prototype, and production OTs are not the same thing
Within DoD’s authority in particular, the three OT categories carry meaningfully different rules:
- Research OTs (10 U.S.C. § 4021) fund basic, applied, or advanced research — the category most relevant to university performers, and the closest in spirit to a research grant, though the agreement’s terms are still negotiated rather than templated.
- Prototype OTs (10 U.S.C. § 4022) fund a prototype project addressing a specific technology or capability need. These generally require either significant participation by a nontraditional defense contractor or cost-sharing, and are frequently structured as competitive solicitations run through a consortium (below).
- Follow-on production OTs can be awarded, without a new competition, to the entity that successfully completed a related prototype OT — a pathway that does not exist under the FAR or under standard grant mechanisms, and is one of the most distinctive features of the authority.
Universities participate almost exclusively in the first category, and occasionally as a named sub-performer inside a prototype OT led by an industry partner.
How universities typically access OT funding: the consortium model
Most agency OT programs, especially DoD’s, do not run a normal, general-public solicitation process. Instead, the agency contracts with a consortium management organization — a nonprofit or industry association that holds a base agreement with the agency — and individual OT awards (called “task” or “project” agreements) are then made to consortium members under that base agreement’s pre-negotiated terms. A university typically joins one or more relevant consortia (there are dozens, organized by technology area — for example, biotechnology, autonomy, hypersonics, or medical countermeasures) as a prerequisite to being eligible to respond to a specific OT solicitation.
This matters operationally for a research office in three ways:
- Membership terms get negotiated once, awards get negotiated many times. The consortium’s base agreement (intellectual property defaults, general terms and conditions) is usually negotiated once by the consortium manager on behalf of all members; the specific project agreement for an individual award can still vary those terms, so read each one rather than assuming the base agreement covers everything.
- The consortium manager, not the agency, is often the university’s direct contracting counterparty for administrative purposes, which changes who signs, who invoices, and who the point of contact is for modifications.
- Membership itself sometimes carries a fee or minimum commitment, which is a cost a proposal budget needs to account for before assuming an OT opportunity is “free” to pursue the way a grant application is.
What’s actually negotiable that would not be under a grant or FAR contract
The core legal fact that makes OT agreements different is that they are exempt from the FAR and, in most cases, from the standard grant/cooperative-agreement statutes and their implementing regulations. That exemption doesn’t mean “no rules” — it means the rules are whatever the specific agreement text says, subject to the negotiation authority Congress granted the agency. In practice, that opens negotiation on terms that are otherwise fixed or heavily constrained under a grant or contract:
- Payment structure — OT agreements are frequently structured around milestone or deliverable payments rather than the cost-reimbursement model standard to federal research grants.
- Termination and modification terms — negotiated case by case rather than governed by the uniform termination clauses found in the FAR or 2 CFR 200.
- Data rights and technical data delivery — the government’s rights in data and software generated under the agreement are a negotiated allocation, not a default clause.
- Patent and invention rights — see below; this is the highest-stakes negotiable item for a university.
- Audit rights — the government’s access to a performer’s records and books is negotiated rather than automatically flowing from the Single Audit Act framework.
The flip side of this flexibility is that a university cannot assume any of its standard, FAR- or Uniform-Guidance-trained negotiating positions apply by default. Every one of those terms has to be affirmatively negotiated into the specific agreement — silence does not default in the university’s favor the way it might under a familiar grant template.
Intellectual property and data rights: why Bayh-Dole is the highest-stakes difference
This is the single point a research office cannot afford to get wrong. The Bayh-Dole Act and its implementing regulations (37 CFR Part 401) govern invention ownership and march-in rights for inventions made under federal grants, cooperative agreements, and contracts. An OT agreement is, by statutory definition, none of those three things — so Bayh-Dole does not automatically apply to inventions made under an OT agreement. Neither do the FAR patent-rights clauses that would otherwise govern a procurement contract.
That does not mean the university loses invention rights by default. It means invention ownership, government license rights, and any march-in-style provisions exist only to the extent the specific OT agreement’s text creates them. In practice, many agencies — particularly DoD, through standard consortium base agreements — voluntarily write Bayh-Dole-like invention rights provisions into their OT terms, because performers (including universities) generally expect and require them before agreeing to sign. But that outcome is a matter of contract drafting and negotiation, not statutory guarantee. A research office reviewing an OT agreement should specifically confirm, in the agreement text itself:
- Who owns inventions conceived or first reduced to practice under the agreement.
- What license, if any, the government retains, and on what terms.
- Whether any march-in-style rights exist for the government, and under what triggering conditions.
- What happens to background IP the university brings into the collaboration versus IP developed under the award (foreground IP).
- Data rights separately from patent rights — technical data and software delivery obligations are typically addressed in a distinct clause and negotiated independently.
Do not assume the university’s standard Bayh-Dole invention-reporting workflow (iEdison, standard patent rights clauses) applies to an OT-funded invention until the specific agreement confirms it does.
Cost principles and cost-share
Because an OT agreement is not a grant or cooperative agreement, the cost principles in 2 CFR Part 200 — allowability, allocability, reasonableness as codified, the specific treatment of items like indirect cost recovery under a negotiated rate — do not automatically apply either. Many OT agreements instead use simplified, commercial-style cost reporting, or a fixed milestone-payment structure that sidesteps detailed cost accounting entirely. Others incorporate cost principles by reference as a matter of the specific agreement’s drafting, which effectively re-imports Uniform Guidance-like rules by contract rather than by statute.
Cost-share is common in prototype OTs in particular — sometimes as a statutory expectation tied to the type of performer involved (nontraditional defense contractors may have reduced or no cost-share expectations specifically to lower their barrier to participation, while traditional contractors more often face a meaningful cost-share requirement). Research OTs used by universities carry cost-share expectations that vary by program and should never be assumed absent from the solicitation.
Audit and reporting
An OT agreement generally sits outside the Single Audit Act framework that governs federal grant expenditures, because Single Audit applies to federal financial assistance (grants and cooperative agreements) — not to OT agreements, which Congress deliberately structured as a separate category. This does not mean an OT-funded project is unaudited. The specific agreement typically negotiates its own audit-access and records-retention terms, and DoD Inspector General and GAO both retain oversight interest in how OT authority is used agency-wide, even where an individual award’s day-to-day audit rights are lighter than a Single Audit. A research office should treat “no automatic Single Audit inclusion” as a difference in mechanism, not an absence of accountability, and should read the specific audit clause in its agreement rather than assuming either the grant-style or contract-style default.
Grant vs. contract vs. Other Transaction: side-by-side comparison
| Dimension | Grant / Cooperative Agreement | FAR Contract | Other Transaction (OT) |
|---|---|---|---|
| Governing regulation | 2 CFR Part 200 (Uniform Guidance) plus agency-specific grant regulations | Federal Acquisition Regulation (FAR) and agency FAR supplements | Neither — governed by the specific authorizing statute and the negotiated agreement text |
| Cost principles | 2 CFR 200 Subpart E applies (allowability, allocability, reasonableness) | FAR Part 31 cost principles apply | Not automatic; simplified or milestone-based reporting is common, or cost principles may be incorporated by reference |
| IP / invention rights default | Bayh-Dole Act and 37 CFR Part 401 apply | FAR patent-rights clauses (e.g., FAR 52.227-11) apply | No statutory default — Bayh-Dole and FAR clauses do not automatically apply; rights are whatever the specific agreement negotiates |
| Audit framework | Single Audit Act (2 CFR 200 Subpart F) for entities meeting the expenditure threshold | Defense Contract Audit Agency (DCAA) or agency audit rights per FAR clauses | Not automatically Single Audit-covered; audit access is a negotiated term of the specific agreement |
| Payment structure | Typically cost-reimbursement against an approved budget | Fixed-price, cost-reimbursement, or other FAR-defined types | Frequently milestone- or deliverable-based; structure is negotiable |
| Competition / access route | Standard funding-opportunity announcement and peer review | Standard procurement competition under FAR Part 15 or similar | Often via a consortium base agreement; competition rules are set by the specific OT program, not the FAR |
| Flexibility to negotiate terms | Low — terms are largely standardized by regulation | Low — terms are largely standardized by the FAR | High — nearly every substantive term (IP, data rights, termination, payment) is negotiated case by case |
| Typical use for universities | Standard federal research funding | Deliverable-based federal work not structured as research funding | Agency research programs seeking non-traditional performers or faster, more flexible terms than a grant or contract allows |
Practical risks a research office should watch for
- Assuming default rights that don’t exist. The most common and highest-consequence mistake is treating an OT agreement’s silence on IP, cost principles, or audit terms as equivalent to the grant or FAR default the office is used to. It is not — silence in an OT agreement usually just means the term was not negotiated, not that a favorable default applies.
- Under-resourcing the negotiation. Because OT agreements are individually negotiated rather than templated, they typically require more contracts-office and legal review time per award than a standard grant, not less — despite the “streamlined” reputation of the mechanism.
- Consortium membership terms getting stale or unreviewed. Because the base agreement is often negotiated once and then reused across many task awards, an office that signed a consortium membership agreement years ago may not have revisited whether its terms still reflect the university’s current IP or data-rights policies.
- Confusing cost-share expectations across performer types. Reduced cost-share treatment for nontraditional contractors under prototype OTs does not automatically extend to a university partner in the same award; check the specific solicitation.
- Treating “no Single Audit” as “no accountability.” Reporting and audit obligations still exist — they are just defined by the agreement rather than by 2 CFR 200 Subpart F, and need to be tracked as carefully as any Single Audit-covered award.
- Assuming one agency’s OT practice generalizes to another’s. DoD’s OT authority is the most mature and most litigated; a DoD-experienced contracts officer’s assumptions do not automatically transfer to a DOE, NASA, or BARDA OT agreement operating under separate authorizing statutes.
Frequently asked questions
What is Other Transaction Authority (OTA)?
Other Transaction (OT) authority is statutory authority given to specific federal agencies — including DoD, NASA, DOE, HHS/BARDA, ARPA-H, DHS, FAA, and NIH — to enter into agreements for research, prototyping, or production that are not procurement contracts, grants, or cooperative agreements, and are therefore not automatically governed by the FAR or by 2 CFR Part 200.
What is an OT agreement (OTA)?
An OT agreement is the actual negotiated document awarded under OT authority. It functions similarly to a contract in that it’s a bilaterally negotiated instrument, but its specific terms — payment structure, IP rights, audit access, termination — are set by negotiation rather than by standard regulatory clauses, because OT agreements sit outside the FAR and, in most cases, outside 2 CFR 200.
Does Bayh-Dole apply to Other Transaction agreements?
Not automatically. Bayh-Dole governs inventions made under grants, cooperative agreements, and contracts; an OT agreement is legally none of those. Many agencies voluntarily write Bayh-Dole-like invention rights into their standard OT terms, but that protection exists only if the specific agreement’s text creates it — always confirm the actual IP clause rather than assuming Bayh-Dole applies.
How do universities usually get access to OT funding?
Most commonly through membership in a technology-focused consortium that holds a base agreement with the sponsoring agency. The university joins the consortium, then responds to specific OT solicitations (“project” or “task” agreements) issued to consortium members, rather than applying to the agency directly the way it would for a standard grant.
Is an OT agreement subject to a Single Audit?
Not automatically. The Single Audit Act framework in 2 CFR 200 Subpart F applies to federal financial assistance — grants and cooperative agreements — not to OT agreements, which are a statutorily distinct category. Audit access and reporting obligations under an OT agreement are instead set by the specific agreement’s negotiated terms.
What is the difference between a research OT and a prototype OT?
A research OT (for example, DoD’s under 10 U.S.C. § 4021) funds basic, applied, or advanced research and is the category most relevant to university performers. A prototype OT (10 U.S.C. § 4022) funds a specific prototype project, often requires nontraditional-contractor participation or cost-share, and can lead to a follow-on production OT awarded without a new competition — a pathway that doesn’t exist under grants or the FAR.
Related CASRAI resources: NSF X-Labs and OT Authority: Milestone Funding Explained covers one specific agency’s recent, program-level use of OT authority in depth. See also Bayh-Dole March-In Rights: What They Mean for University Tech Transfer, Cooperative Agreement, Bayh-Dole Act, and The Single Audit (2 CFR 200 Subpart F): Requirements and Thresholds.
