Other Transaction Agreements vs FAR Contracts

An executive comparing an OTA vs FAR contract should evaluate whether the proposed terms fit the work and the company's finances. A flexible agreement with uncertain payment criteria can be harder to finance than a familiar procurement contract. Conversely, a carefully negotiated prototype OTA may accommodate development and licensing arrangements that are difficult to fit into a standard solicitation.

On This Page

• What each vehicle authorizes
• Compare the business consequences
• Eligibility and the 2026 compliance picture
• Negotiate payment and intellectual property together
• Production is a separate business decision
• Choose the opportunity by its terms

What each vehicle authorizes

An other transaction, or OT, is a statutory agreement outside the conventional procurement-contract, grant, and cooperative-agreement categories. “OTA” is used for both other transaction authority and an other transaction agreement. The authority belongs to the government; the agreement is the instrument a company signs. It remains a binding agreement, even though it is not a FAR procurement contract.

For defense work, distinguish three uses:

• Research OTs: 10 U.S.C. 4021 authorizes basic, applied, and advanced research. Its research cost-sharing provisions have their own practicability qualification.
• Prototype OTs: Section 4022 covers defense-relevant prototyping, including software, processes, and demonstrations, subject to statutory conditions.
• Production OTs: Section 4022(f) provides a route from successful prototyping into follow-on work. It is not a general authorization to label any purchase an OTA.

A FAR contract is a procurement contract governed by the FAR, with relevant agency supplements, deviations, and clauses. FAR 1.104 states the regulation's general applicability. In defense procurement, the Defense Federal Acquisition Regulation Supplement, or DFARS, adds agency-specific requirements.

FAR does not mean fixed-price. FAR Part 16 includes fixed-price, cost-reimbursement, and incentive arrangements. An OTA's legal flexibility and a contract's pricing arrangement answer different questions. Compare who absorbs extra work and cost, not simply the instrument's name.

Compare the business consequences

Use the same questions for both proposed awards. The table summarizes the authorities and official guidance cited throughout this article; its final column gives editorial recommendations, not mandatory contract language. Source position checked September 7, 2026.

Business issue	Prototype OTA	FAR procurement contract	What to resolve before committing
Entry	Project and participation conditions matter	Eligibility follows the solicitation and applicable rules	Confirm that the actual company and proposed work qualify
Terms	Considerable scope for tailored provisions	Prescribed clauses plus negotiated terms and applicable exceptions	Read the complete award, including incorporated documents
Payment risk	The negotiated payment structure controls	The contract type and payment clauses control	Identify the event that earns payment and who verifies it
Intellectual property	Rights must be addressed in the agreement	Applicable data-rights clauses establish a starting position	Separate ownership, delivery obligations, and license rights
Disputes	Do not assume conventional contract remedies apply	FAR Part 33 addresses protests, disputes, and appeals	Identify the available forum and escalation procedure
Production	A potential follow-on route, subject to conditions	Production can be acquired through a procurement contract	Establish the next award's scope, funding, and terms

The OTA's advantage is meaningful when the team uses its flexibility to solve a specific problem. That might be a development milestone that recognizes technical uncertainty, or a license that permits government use without surrendering unrelated commercial assets. Merely shortening the document does not resolve either issue.

The distinction also affects recourse. FAR Part 33 describes the conventional procurement protest and contract-dispute structure. DARPA notes that the Contract Disputes Act does not generally apply to OTs and that some challenges to statutory compliance have been reviewed. Do not interpret “outside FAR” as “immune from challenge.” Resolve dispute procedures, termination consequences, and responsibility for unfinished work before signature.

Eligibility and the 2026 compliance picture

Under Section 4022(d), a prototype OT must meet at least one condition:

• Significant participation by a nontraditional defense contractor or nonprofit research institution.
• All significant nongovernment participants are small businesses or nontraditional defense contractors.
• Nongovernment sources cover at least one-third of total project cost.
• The senior procurement executive makes the required exceptional-circumstances determination.

The one-third contribution is an alternative eligibility route, not a charge automatically imposed on every prototype award. Procurement-integrity requirements still apply, and competitive procedures are required to the maximum extent practicable.

Nontraditional does not mean newly founded. Section 3014 bases the definition on whether an entity currently performs, or performed during the preceding year, a defense contract or subcontract subject to full Cost Accounting Standards coverage. A business can have government experience and still qualify. Evaluate the relevant legal entity and performance history rather than relying on a startup label.

The current comparison also needs a 2026 qualification. Section 1826 of the FY2026 National Defense Authorization Act, reproduced in the statutory notes to Section 3014, establishes exemptions for nontraditional contractors from listed requirements, including certain business-system provisions, certified cost or pricing data, and FAR Part 31. It permits specified written determinations to waive, modify, or partially apply those requirements. Consequently, a conventional defense contract need not carry every compliance burden assumed in older OTA comparisons. Check which exemptions and determinations affect the proposed award.

There is a second moving part: the FAR overhaul. Acquisition.gov explains that model deviation text becomes applicable through agency adoption; it is distinct from formal regulatory revision and from nonmandatory buying guides. Ask for the solicitation's applicable FAR and DFARS deviations. Comparing a current OTA against an obsolete FAR checklist can produce the wrong investment decision.

Negotiate payment and intellectual property together

Payment depends on what the milestone actually promises

DARPA's OT proposer instructions require milestone descriptions, completion criteria, due dates, and payment schedules. This is a concrete agency example of how flexibility becomes an enforceable delivery arrangement, not a universal payment template for every defense OTA.

For a hypothetical software prototype, “demonstrate the interface” leaves important questions open. Does completion mean running the agreed test, achieving a performance result, delivering documentation, or obtaining written acceptance? Who supplies the test environment? What happens if government access arrives late? Put those answers beside the payment schedule before estimating the working capital needed to perform. A technically unsuccessful experiment and an uncompleted contractual milestone need not mean the same thing; the agreed completion criteria determine the distinction.

Under a firm-fixed-price FAR contract, the contractor generally bears the cost risk for the agreed work. Cost-reimbursement arrangements operate differently and impose their own conditions. An OTA can also place substantial performance risk on the company. Negotiate responsibility for changes and failed milestones with the same care as the headline amount.

Ownership and government usage rights are separate

An OTA does not automatically preserve every commercial right, and a FAR contract does not automatically transfer ownership of all intellectual property. For noncommercial technical data, DFARS 227.7103-5 describes different government licenses and permits specifically negotiated rights in defined circumstances. Funding history and the kind of data matter; software and commercial data require their applicable provisions.

DARPA's OT instructions likewise require identification of intended restrictions, including subcontractor assertions. For either vehicle, prepare a deliverables list that separates pre-existing material, newly developed material, and third-party components. Then specify who may use, modify, disclose, or authorize others to use each item.

For a company planning future commercial sales, the practical review question is whether the proposed license or delivery requirement reaches assets outside the funded effort. For the government customer, it is whether the rights support deployment and sustainment. Negotiate both sides of that boundary while defining the work. Waiting until final delivery turns a business-model question into an acceptance dispute.

Production is a separate business decision

Section 4022(f) permits a follow-on production contract or transaction without another competition when the required conditions are met, including competitive selection for the prototype and successful completion. The agreement must provide for follow-on production; the statute does not make explicit notice in the original request for proposals an absolute prerequisite. A qualifying consortium subproject can transition without waiting for all consortium activities to finish.

That legal route should be reflected in opportunity planning, but it is not a production order. Ask who documents successful completion, which prototype result the follow-on scope will implement, and whether the next stage has a buyer and funding. Keep the prototype award, a possible production ceiling, and currently funded work separate in the business case. Do not base factory expansion or permanent staffing on the existence of follow-on authority alone.

The transition can also change the commercial arrangement. In its September 2025 review of OTAs, GAO found that 10 of 18 selected weapon-system efforts planned to switch to standard contracts for production. Officials cited reasons including better visibility into costs. Those selected efforts were not representative of all OTA projects, so that result is not an industry-wide transition rate.

For a prototype supplier, the implication is to cost the transition itself: production pricing, reporting, licensing, subcontract terms, and delivery obligations may need a new negotiation. Prototype success and an attractive production business are separate achievements. GAO also found gaps in tracking transitions to FAR contracts, which limits confident claims that OTA use alone predicts capability delivery.

Choose the opportunity by its terms

Pursue an OTA when the work fits the authority and the proposed flexibility solves a real development, funding, or licensing problem. A FAR opportunity can be equally attractive when its actual clauses, exemptions, and pricing arrangement suit the company's delivery model. Those are editorial judgments from the comparison above, not a rule that assigns all innovative work to one vehicle.

Before a bid or signature decision, put four answers in front of the responsible executives:

1. Qualification: Which authority and eligibility conditions support this award, and which exceptions apply to this company?
2. Cash: What must happen before each payment, and how much work must the company finance first?
3. Rights and recourse: What must be delivered or licensed, and what happens if the parties disagree or stop work?
4. Transition: What specific action would turn this award into the next funded stage?

An opportunity becomes investable when those answers are credible. The OTA or FAR label is the starting point for that review.

Source notes

• DARPA, What are OTs? Official explanation of OT instruments and the distinction from conventional procurement rules.
• 10 U.S.C. 4021. Statutory authority and conditions for research OTs.
• 10 U.S.C. 4022. Prototype eligibility, competition, procurement integrity, and follow-on authority.
• 10 U.S.C. 3014 and statutory notes. Nontraditional contractor definition and FY2026 NDAA Section 1826 exemptions.
• FAR 1.104. General applicability of the FAR.
• FAR Part 16. Procurement contract types and allocation of cost risk.
• FAR Part 33. Procurement protests, contract disputes, and appeals.
• Acquisition.gov, FAR Overhaul FAQs. Official guidance on agency deviations and nonregulatory resources.
• DARPA, OT Proposer Instructions. Agency requirements for milestones and intellectual-property assertions, updated September 25, 2025.
• DFARS 227.7103-5. Government license rights in noncommercial technical data.
• GAO-25-107546. September 2025 oversight report on OTA data and selected prototype-to-production transitions.

Last checked: September 7, 2026.