The traditional defense acquisition system was not designed for the pace at which the UAS threat environment evolves. A program of record that takes five years from requirements generation to initial fielding is not a useful vehicle for acquiring a capability that needs to be in the hands of operators in eighteen months. The threat does not wait for the acquisition system to catch up.
Other Transaction Authority — OTA — exists precisely to solve this problem. It is a legitimate, congressionally authorized acquisition pathway that operates outside the Federal Acquisition Regulation, allows rapid prototyping and follow-on production, and has been used successfully by DoD components to field UAS capability at a pace the traditional system cannot match.
It is also widely misunderstood. Procurement teams either avoid it because it feels unfamiliar, misapply it in ways that create legal exposure, or use it for the wrong part of the acquisition lifecycle. This post is a practical explanation of what OTA is, what it is not, when it is the right tool, and how to use it effectively for UAS procurement.
What OTA Actually Is
Other Transaction Authority is statutory authority granted by Congress to specific federal agencies to enter into agreements that are not contracts, grants, or cooperative agreements under the standard legal framework. For DoD, the primary OTA authorities live in 10 U.S.C. § 4021 (prototype projects) and 10 U.S.C. § 4022 (follow-on production).
The critical word is “agreements.” An OTA agreement is not a FAR-based contract. It is not subject to the Cost Accounting Standards, the Truth in Negotiations Act, or most of the regulatory apparatus that governs traditional defense contracts. This is not a loophole — it is the design. Congress created OTA specifically to allow DoD to engage with nontraditional defense contractors and move at commercial speed without the compliance overhead that makes traditional contracting hostile to companies that do not derive most of their revenue from government work.
For UAS procurement, this matters enormously. The domestic UAS industry — the one building platforms that are NDAA-compliant and free of foreign hardware supply chain risk — is largely composed of companies that do not have the infrastructure to navigate a traditional FAR-based acquisition. They have not invested in government accounting systems, they do not have DCAA-audited cost structures, and they cannot afford the compliance overhead of a cost-plus contract. OTA removes those barriers while preserving the government’s ability to get real capability quickly.
What OTA Is Not
OTA is not a blank check. It is not a way to avoid competition. It is not an appropriate vehicle for every acquisition, and misusing it creates legal exposure that can unwind an agreement after the fact.
Several common misconceptions are worth addressing directly.
OTA is not a sole-source workaround. Prototype OTAs require a competitive process unless the agency can justify a noncompetitive award under specific statutory criteria. “We already know who we want” is not one of those criteria. Procurement teams that treat OTA as a vehicle for predetermined awards are creating bid protest risk and potentially Antideficiency Act exposure.
OTA prototype authority does not automatically convert to production. The follow-on production authority under 10 U.S.C. § 4022 requires that the prototype OTA was competitively awarded and that the follow-on production is for the same system demonstrated in the prototype. Using a prototype OTA as a foot in the door for a production award that was the real objective from the start is a misuse that has been successfully protested before the GAO.
OTA does not eliminate oversight. Agreements must be reported to Congress above certain thresholds. The agency’s legal counsel must review and approve the agreement. The requirement for at least one nontraditional defense contractor participant — or a cost share from a traditional contractor — is a statutory requirement, not a suggestion.
Understanding the boundaries is as important as understanding the authorities. OTA used correctly is a powerful tool. OTA misused creates problems that are more expensive than the traditional acquisition path it was meant to shortcut.
When OTA Is the Right Vehicle for UAS Procurement
OTA is not always the right answer. It is the right answer when the acquisition meets specific criteria that align with the statutory authority and the practical advantages of the mechanism.
Prototype and Demonstration Requirements
The prototype OTA authority is strongest when the requirement genuinely involves prototyping — evaluating whether a technology or system meets a defined operational need before committing to production. For UAS procurement, this maps naturally to capability evaluations: does this platform perform as specified in the operational environment the unit actually faces?
If your requirement involves bringing multiple vendors in for a structured evaluation against defined performance criteria, with the intent to down-select to a production award, prototype OTA is well-suited to that process. It allows you to structure the evaluation as a competition, engage vendors who would not qualify as traditional defense contractors, and move from competition to award on a timeline that reflects operational urgency rather than administrative process.
We covered the evaluation criteria that matter for UAS platforms in detail in our counter-UAS procurement guide — the same principles apply here. Define what the platform needs to do against realistic threat surrogates before you structure the OTA, not after.
Nontraditional Contractor Engagement
If the capability you need exists primarily in companies that do not have traditional defense contractor infrastructure, OTA is often the only practical path to engaging them. The domestic UAS industry is a clear example. The companies building the most capable, most supply-chain-secure platforms are frequently small businesses without DCAA-audited accounting systems, without cleared facilities, and without the administrative infrastructure to execute a traditional cost-plus contract.
OTA allows those companies to compete on the merits of their technology rather than the depth of their compliance infrastructure. For procurement teams that have identified a specific capability gap — persistent low-altitude ISR in a denied environment, for example, or a battlefield mapping software platform that operates fully offline — OTA is often the mechanism that makes engaging the right vendor actually possible.
Speed-to-Fielding Requirements
When operational urgency is genuine and documentable, OTA provides a timeline advantage that the traditional system cannot match. A well-structured prototype OTA can move from solicitation to award in sixty to ninety days. A FAR-based competitive acquisition for the same requirement will rarely close in under a year, and complex requirements often take longer.
The urgency has to be real and documented. Manufactured urgency that is constructed after the fact to justify OTA use is exactly the kind of thing that surfaces in audits and protests. But when the operational requirement is genuine — when the unit needs capability before the next deployment cycle, when the threat has evolved faster than the program of record can respond — OTA is the mechanism that exists for that situation.
How to Structure an OTA for UAS Procurement
The mechanics of structuring an OTA vary by agency and by the specific consortium or agreement vehicle being used, but the core elements are consistent.
Define the Prototype Objective Precisely
The prototype OTA lives or dies on the clarity of the prototype objective. Vague objectives — “evaluate UAS platforms for ISR applications” — create ambiguity about what success looks like, complicate down-select decisions, and invite protests from vendors who disagree with how the evaluation was scored.
A well-defined prototype objective specifies the operational environment (altitude range, operating temperature, terrain type), the mission profile (endurance requirement, sensor payload, communication architecture), the threat environment the platform must operate in without signature compromise, and the supply chain requirements that reflect NDAA compliance obligations. If you have a specific C2 integration requirement — ATAK compatibility, NATO interface standards, a specific data format — it belongs in the prototype objective, not in a post-award negotiation.
The more precisely the objective is defined, the more useful the prototype evaluation results are, and the more defensible the down-select decision becomes.
Use an Existing Consortium Where Possible
Most DoD components access OTA through existing consortium agreements managed by nonprofit consortium management firms. These consortia — NSTXL, DEFENSEWERX, the National Security Technology Accelerator, and others — maintain pre-vetted pools of nontraditional contractors and provide administrative infrastructure that individual program offices do not have to build from scratch.
Using an existing consortium compresses the timeline significantly. The legal framework is already established. The vendor pool is already vetted. The administrative process is already defined. The program office defines the requirement, the consortium issues the solicitation to its member companies, and the competition runs within the established framework.
If your agency does not already have relationships with relevant consortia, establishing them before you have an urgent requirement is worth doing. The time to learn how a consortium works is not when you are trying to close an award in sixty days.
Structure the Evaluation Against Operational Performance
The evaluation criteria for a UAS prototype OTA should reflect operational performance, not technical specifications alone. A platform that meets every specification on paper but fails in the actual operating environment is not a successful prototype.
Structure the evaluation to include field demonstrations against realistic threat surrogates, in conditions representative of the actual operational environment. Require vendors to demonstrate the supply chain documentation that reflects your NDAA compliance requirements. Evaluate the software stack in an offline environment that reflects denied communications conditions. Score sustainment at the operator level — can a field-grade operator perform the maintenance tasks required to keep the platform mission-capable without depot support?
The SOF-specific evaluation criteria we have written about separately apply here as well, particularly for units with austere logistics requirements. The evaluation should surface the platform that performs in the field, not the one that performs best in a briefing.
Plan the Follow-On Production Path Before You Award the Prototype
The follow-on production authority under 10 U.S.C. § 4022 requires that the production award is for the same system demonstrated in the prototype OTA. This means the production requirement needs to be thought through before the prototype is awarded, not after.
If the intent is to use the prototype OTA to down-select to a single vendor and then execute a follow-on production award, the prototype solicitation needs to reflect that intent from the start. The evaluation criteria, the prototype scope, and the down-select process all need to be structured with the production award in mind. Retrofitting a production rationale onto a prototype OTA that was not structured for it is where legal exposure accumulates.
Work with your legal counsel and contracting officer to document the production intent before the prototype solicitation goes out. The documentation burden at the front end is far lighter than the remediation burden if the follow-on production award is protested.
Common Failure Modes
Procurement teams that have used OTA unsuccessfully tend to fail in predictable ways. Recognizing these patterns is useful before you start.
Scope creep between prototype and production. The follow-on production award must be for the same system. Adding requirements after the prototype — even requirements that seem minor — can break the legal link between the prototype OTA and the production authority. Define the production requirement carefully before the prototype is awarded and resist the pressure to expand it after.
Inadequate competition documentation. OTA competition requirements are real, and the documentation of how competition was conducted matters when awards are protested. Maintain a clear record of who was solicited, how proposals were evaluated, and why the down-select decision was made. The informality of OTA does not extend to the documentation of competitive process.
Treating OTA as a relationship vehicle rather than a competition. The most common misuse pattern is using OTA to formalize a vendor relationship that was decided before the solicitation. This is the version that surfaces in protests and audits. Run a real competition, document it properly, and let the evaluation results drive the award.
Ignoring the nontraditional contractor requirement. The statutory requirement for nontraditional contractor participation is real. If the proposed awardee is a traditional defense contractor without a cost share or a nontraditional subcontractor in a meaningful role, the OTA authority may not apply. Confirm this with legal counsel before award, not after.
The Bottom Line
OTA is not a shortcut. It is a different path — one that is faster and more accessible to nontraditional vendors than the FAR-based system, but one that has its own rules and its own failure modes.
Used correctly, it is the most effective mechanism available for procuring UAS capability at the pace the operational environment demands. The domestic UAS industry has the technology. The OTA framework has the authority. The gap between them is almost always a procurement team that has not yet learned how to use the tool.
If you are working through a UAS procurement requirement and want to discuss how OTA might apply to your specific situation, contact our team. We work with procurement teams regularly on structuring evaluations and can provide documentation of our supply chain, software architecture, and platform performance that supports the prototype OTA process.
For further reading, our procurement guide to the Blue UAS Cleared List and our overview of OTA agreements cover adjacent topics that are relevant to any team building a UAS acquisition strategy.