Other Transaction Authority is a statutory power that allows the Department of Defense (DoD) to enter into binding agreements other than standard procurement contracts, grants, or cooperative agreements. Codified in federal law, this authority exempts the military from the Federal Acquisition Regulation (FAR) so it can design, test, and buy hardware and software at commercial speed.
Congress created Other Transaction Authority to help defense agencies bypass the administrative friction of standard defense contracting and attract nontraditional commercial companies that refuse to operate under military cost-accounting rules. By replacing formal procurement procedures with flexible terms, the Pentagon uses other transactions to field experimental prototypes and scale successful systems into production.
What Other Transaction Authority Means in Practice
An Other Transaction Authority (OTA) agreement is a legally binding instrument between the federal government and a commercial or academic partner that is not governed by standard procurement rules. The term defines what the instrument is not: it is not a standard procurement contract, it is not a grant, and it is not a cooperative agreement. Because it falls outside those three traditional categories, an other transaction is exempt from the FAR and dozens of associated federal acquisition statutes.
The primary motivation behind other transactions is accessing commercial technology that the military cannot easily buy through traditional pathways. Commercial software developers, venture-backed startups, and commercial aerospace manufacturers often avoid traditional defense contracting. Standard procurement rules require government-unique accounting systems, lengthy audit requirements, and rigid intellectual property disclosures that commercial firms view as unacceptable business risks.
An other transaction operates more like a commercial partnership contract. Contracting personnel can tailor terms around intellectual property, milestone payments, accounting methods, and performance deliverables directly to the project. Instead of requiring companies to submit formal, hundreds-of-page proposals responding to prescriptive technical requirements, agencies running an other transaction solicitation can evaluate short white papers, slide decks, or in-person technical demonstrations.
The Defense Innovation Unit (DIU) relies heavily on this flexibility to bring commercial capability into the armed forces. DIU reports that it uses prototype other transaction authority to award agreements in as few as 60 to 90 days. That cadence contrasts sharply with traditional military acquisition programs, where developing a solicitation, conducting source selection, and awarding a contract can take anywhere from 18 months to several years.
The Statutes and Regulations Excluded from Other Transactions
Exemption from standard procurement laws is the defining operational feature of an other transaction agreement. According to the Congressional Research Service (CRS), other transaction agreements bypass a wide collection of statutory and regulatory mandates that apply to standard military contracts.
Five major procurement statutes do not apply to other transaction agreements:
- The Competition in Contracting Act (CICA): Standard procurements require full and open competition under strict statutory guidelines, governed by formal competition notices and administrative protest channels. Other transactions require competitive procedures only to the extent practical, permitting flexible solicitation formats.
- The Truth in Negotiations Act (TINA): Traditional defense contracts require contractors to submit certified cost or pricing data, disclosing internal cost structures to government auditors. Other transactions eliminate this requirement, allowing price evaluations based on market research, commercial pricing, or negotiated milestone value.
- Cost Accounting Standards (CAS): Traditional defense contractors must implement federal cost-accounting systems that track allowability, allocability, and indirect overhead rates. Commercial companies without dedicated defense accounting infrastructure are exempt from CAS under an other transaction.
- The Contract Disputes Act (CDA): Standard contract disputes follow formal administrative appeal procedures through the Armed Services Board of Contract Appeals or the U.S. Court of Federal Claims. Dispute resolution mechanisms under an other transaction are negotiated directly within the agreement itself.
- Select Intellectual Property Statutes: Traditional procurement contracts require standard Defense Federal Acquisition Regulation Supplement clauses governing technical data rights, patent allocations, and commercial software licenses under the Bayh-Dole Act. In an other transaction, the government and the vendor negotiate customized data rights that protect commercial proprietary technology while securing necessary government operational licenses.
In place of formal Requests for Proposal (RFPs) published through standard channels, defense organizations can accept oral presentations, slide demonstrations, and technical white papers. As noted in the CRS analysis IF12856, agencies can also advertise solicitations outside traditional government media. However, other transactions do not operate outside all federal law. Parties to an other transaction remain bound by federal criminal laws, national security directives, export control regulations, and federal ethics requirements.
The Statutory Basis Under Title 10
The Department of Defense derives its other transaction authorities from two specific sections of Title 10 of the United States Code. Readers reviewing older defense acquisition literature often encounter older statutory references, as Congress reorganized these provisions under Public Law 116-283, effective January 1, 2022.
The two governing statutes sit within Title 10:
- 10 U.S.C. § 4021 (Research Authority): As maintained by the Office of the Law Revision Counsel, Section 4021 authorizes the Secretary of Defense to enter into transactions other than contracts, grants, or cooperative agreements to carry out basic, applied, and advanced research projects. Prior to January 1, 2022, this authority was codified at 10 U.S.C. § 2371.
- 10 U.S.C. § 4022 (Prototype Authority and Follow-On Production): Maintained by the Office of the Law Revision Counsel, Section 4022 authorizes the Department of Defense to carry out prototype projects directly relevant to enhancing the mission effectiveness of military personnel, platforms, systems, components, or materials. Prior to the 2022 renumbering, this provision existed as 10 U.S.C. § 2371b.
The following table summarizes the statutory renumbering and primary purpose of each provision:
| Current Citation | Former Citation | Authority Type | Primary Objective |
|---|---|---|---|
| 10 U.S.C. § 4021 | 10 U.S.C. § 2371 | Research | Basic, applied, and advanced research projects |
| 10 U.S.C. § 4022 | 10 U.S.C. § 2371b | Prototype | Developing and evaluating physical or virtual models |
| 10 U.S.C. § 4022(f) | 10 U.S.C. § 2371b(f) | Follow-On Production | Non-competitive production scaling after successful prototype |
Section 4022 serves as the engine for modern defense prototyping. The statute defines a prototype broadly, encompassing physical systems, computer software, virtual models, materials, and operational concepts. According to CRS report R45521, a prototype for other transaction purposes is a physical, virtual, or theoretical model used to evaluate technical or manufacturing feasibility, or the operational effectiveness of a technology intended to be fielded later.
The Three Categories of Other Transactions
The Department of Defense uses other transaction authority across three distinct project phases: research, prototyping, and follow-on production. Each phase operates under different legal rules and serves a distinct point in the technology development lifecycle.
Research Transactions
Research other transactions carry out basic, applied, and advanced scientific research under 10 U.S.C. § 4021. Defense research labs, including the Defense Advanced Research Projects Agency (DARPA), use research other transactions to explore speculative scientific concepts alongside universities, nonprofit laboratories, and private industry consortia.
Research agreements remove standard federal grant administration rules and allow flexible cost-sharing models. They are designed to explore early scientific questions where definitive deliverables cannot be specified in advance.
Prototype Transactions
Prototype other transactions under 10 U.S.C. § 4022 fund the development and testing of specific military hardware, software, and systems. These agreements evaluate whether an emerging technology can solve an operational problem before the Department of Defense commits to buying it in large volumes.
Agencies use prototype other transactions for diverse defense systems, including tactical communication gear, space domain tracking sensors, autonomous ground vehicles, and predictive maintenance algorithms. Programs using modern pathways, such as the Middle Tier Acquisition framework and the Software Acquisition Pathway, frequently execute their rapid prototyping efforts through prototype other transactions.
Follow-On Production Transactions
Follow-on production authority under 10 U.S.C. § 4022(f) bridges the gap between successful prototype demonstration and military fielding. Under this provision, the military can award a follow-on production agreement or contract without using competitive procedures if two statutory criteria are met:
- Competitive procedures were used when awarding the initial prototype other transaction agreement.
- The participating contractor successfully completed the prototype project.
This statutory mechanism provides a transition path for commercial companies. A startup that proves its prototype in an initial competitive evaluation does not need to submit to a second, multi-year competitive source selection to manufacture the resulting product. According to DIU’s commercial guidance, 10 U.S.C. § 4022 explicitly protects this direct path from prototype success into production.
Eligibility Conditions and Approval Thresholds
Congress established specific statutory conditions that a project must satisfy before the Department of Defense can execute a prototype other transaction under 10 U.S.C. § 4022. These conditions ensure that other transactions advance technological innovation rather than serving as an arbitrary detour around standard acquisition laws.
To use prototype other transaction authority, a defense project must satisfy at least one of four statutory conditions:
- Nontraditional Defense Contractor Participation: At least one nontraditional defense contractor or nonprofit research institution must participate to a significant extent in the prototype project.
- Small Business Participation: All significant participants in the transaction must be small businesses or nontraditional defense contractors.
- One-Third Cost Share: If traditional defense contractors perform the work without significant participation from a nontraditional firm, at least one-third of the total project cost must come from non-federal funds.
- Exceptional Circumstances: A senior procurement executive determines in writing that exceptional circumstances justify using an other transaction to obtain capabilities that would otherwise be unavailable under a traditional procurement contract.
Prototype other transactions are subject to internal approval tiers based on total expected dollar value. While agreements under $100 million can be executed by designated contracting personnel with other transaction authority, higher dollar values require executive-level justification:
- $100 Million to $500 Million Tier: The head of the contracting activity must determine in writing that the statutory conditions are met and that the use of an other transaction is essential to promoting the success of the project.
- Over $500 Million Tier: The senior procurement executive for the military department or agency must determine that using an other transaction is essential to meet critical national security objectives. In addition, the Department of Defense must provide written notice to congressional defense committees at least 30 days prior to awarding the transaction.
The Role of Nontraditional Defense Contractors
The concept of the nontraditional defense contractor is the cornerstone of modern other transaction policy. Congress created this designation to open defense acquisition to commercial engineering talent and commercial supply chains.
Under Title 10 and related acquisition guidance, a nontraditional defense contractor is defined as an entity that has not worked on a Department of Defense contract or subcontract subject to full Cost Accounting Standards coverage for at least one year prior to the solicitation.
This definition includes several types of commercial enterprises:
- Venture-backed commercial software and hardware startups that have never sold products to the federal government.
- Large, established commercial technology companies that sell consumer electronics, cloud computing services, or automotive hardware but refuse to accept standard defense accounting rules.
- Commercial suppliers and component manufacturers that participate as subcontractors or subsystem providers in larger defense projects.
By requiring either significant participation from a nontraditional defense contractor or a 30 percent private cost-match, 10 U.S.C. § 4022 encourages traditional defense primes to partner with commercial firms. When a traditional aerospace contractor wants to use the speed and flexibility of an other transaction, it must partner with commercial technology companies and incorporate their commercial subsystems into the project.
In a comprehensive review of early prototype trends (GAO-20-84), the Government Accountability Office (GAO) found that 88 percent of prototype other transactions awarded between fiscal years 2016 and 2018 went to companies that did not typically do business with the Pentagon. This confirmed that the statutory mechanism succeeded in attracting nontraditional commercial vendors into defense projects.
Growth and Spending Trends Across Defense Agencies
Department of Defense spending through other transactions has expanded from a specialized niche into an enterprise acquisition pipeline. Between fiscal years 2016 and 2024, the military increased its financial commitments under other transaction agreements tenfold.
A September 2025 performance review by the Government Accountability Office (GAO-25-107546) documented the scale of this expansion. Total military obligations through other transactions for prototyping and production grew from $1.8 billion in fiscal year 2016 to over $18 billion in fiscal year 2024. Of that $18 billion total in fiscal year 2024, prototype other transactions accounted for over $16 billion, while production other transactions represented approximately $2 billion.
The number of individual agreement actions mirrored this financial growth. According to CRS report IF12856, the total count of other transaction actions across the Department of Defense grew from 496 actions in fiscal year 2017 to 4,391 actions in fiscal year 2022. An earlier CRS analysis (R45521) revealed that in the early years of the authority, between fiscal years 2013 and 2017, new prototype agreements rose from 12 to 94, an increase of more than 650 percent.
The rapid growth in other transaction volume is particularly visible in programs delivering orbital hardware and space sensors. Organizations like the Space Development Agency have leaned on rapid commercial development cycles to field proliferated low Earth orbit satellite constellations. Similarly, enterprise software and infrastructure programs, including efforts that integrate with the Joint Warfighting Cloud Capability, share the technological focus on commercial code and rapid capability loops that prototype other transactions are designed to purchase.
To reflect ongoing changes enacted by Congress across recent National Defense Authorization Acts, the Department of Defense published a proposed rule in the Federal Register on September 4, 2024 (Document 2024-19457). The rulemaking updates defense regulations governing follow-on production agreements and incorporates explicit guidance for small businesses, nontraditional contractors, research institutions, and industry consortia.
Oversight Gaps and GAO Audit Findings
The rapid growth of other transaction spending has prompted ongoing scrutiny from federal auditors and congressional committees. While other transactions provide clear speed advantages, Government Accountability Office investigations have highlighted persistent record-keeping deficiencies, consortium tracking gaps, and compliance oversights.
Three primary GAO investigations document the operational and administrative challenges associated with other transactions:
Production Tracking and Transition Disconnects
In report GAO-25-107546, released in September 2025, the Government Accountability Office examined whether prototype other transactions successfully transition into military production programs. The review revealed that the Department of Defense does not systematically know the full extent to which prototype other transactions lead directly to production contracts.
Auditors reviewed 18 selected weapon system programs that used prototype other transactions. Among those 18 programs, 10 planned to switch back to traditional FAR-based contracts for their production phase rather than executing an other transaction follow-on production agreement under 10 U.S.C. § 4022(f). The GAO recommended that the Pentagon establish systematic data tracking to monitor standard production contracts that emerge from completed prototypes, a measure to which the defense agency agreed.
Heavy Reliance on Consortia and Award Visibility
A major portion of defense other transaction spending flows through industry consortia rather than direct bilateral awards between an agency and a single company. Under a consortium model, a defense organization enters into an overarching agreement with an administrative consortium manager, which then distributes project awards to member firms.
In report GAO-22-105357, auditors found that between fiscal years 2019 and 2021, the Department of Defense obligated over $24 billion on other transaction awards to consortia for prototyping efforts. That figure accounted for nearly two-thirds of all military prototype other transaction dollars during that three-year window. The top three consortia alone received $8.0 billion, $5.0 billion, and $2.6 billion respectively.
Despite this concentration of funding, the GAO found that defense officials lacked a systematic method for tracking which individual member companies received awards through these consortia. Because transactions were reported under the consortium management organization rather than the performing vendors, the military lacked visibility into the actual recipients of billions of taxpayer dollars. The GAO recommended that the defense establishment maintain a comprehensive, publicly accessible registry of consortium awards.
Compliance and Procedural Approvals
The absence of rigid FAR regulations does not remove the statutory requirement for procedural compliance. In report GAO-20-84, the GAO audited 11 specific prototype transactions to verify whether contracting personnel followed required administrative processes.
The audit discovered compliance errors in two of the 11 reviewed transactions:
- A DARPA agreement valued at $7.8 million was finalized without obtaining the mandated higher-level administrative review.
- An Army agreement valued at $10 million bypassed the standard review process, using an unauthorized alternative reviewer.
These administrative findings illustrate that while other transactions give contracting officers broad operational discretion, managing them requires rigorous understanding of the statutory boundaries established under Title 10.
Comparing Other Transactions to Traditional Contracts
Understanding when an other transaction agreement makes sense requires comparing it against a standard FAR-based procurement contract. The two mechanisms prioritize different institutional values: traditional contracts emphasize procedural fairness, public auditability, and standardized government data rights, while other transactions emphasize rapid fielding, commercial partnerships, and tailored negotiation.
The table below contrasts how each mechanism handles key procurement dimensions:
| Acquisition Dimension | Traditional FAR-Based Contract | Other Transaction Agreement |
|---|---|---|
| Regulatory Authority | Federal Acquisition Regulation (FAR) | 10 U.S.C. §§ 4021 & 4022 |
| Solicitations | Formal Requests for Proposals (RFPs) | White papers, oral briefs, demonstrations |
| Pricing Rules | Truth in Negotiations Act (certified data) | Commercial market pricing and milestone value |
| Accounting Oversight | Cost Accounting Standards (CAS) | Commercial accounting practices |
| Data Rights | Standard DFARS government-use clauses | Negotiated commercial intellectual property terms |
| Vendor Eligibility | Any qualified government contractor | Nontraditional contractor or 1/3 cost-match |
| Bid Protests | Subject to formal GAO and CICA protests | Protests limited strictly to agency authority |
| Production Scaling | Requires standard competitive RFP | Non-competitive transition under § 4022(f) |
An other transaction agreement is not suitable for every defense procurement requirement. When buying mature commercial off-the-shelf equipment, standard commercial item procedures under FAR Part 12 remain the standard approach. For massive, multi-decade capital construction programs or standard operational support services, traditional procurement contracts provide established accounting and compliance structures that protect government interests over long timelines.
However, when a defense program needs to validate whether emerging commercial technology can survive military deployment, an other transaction provides the statutory flexibility to test the concept in months rather than years.
To evaluate whether a planned research or prototype effort qualifies for other transaction authority, procurement teams and commercial vendors should consult the relevant military command’s other transaction guide, confirm the participation of a qualifying nontraditional defense contractor, and review the statutory guidelines codified under 10 U.S.C. § 4022.