The Government Accountability Office has repeatedly examined the Army’s use of Other Transaction Authority for prototype projects under 10 U.S.C. 4022. The statute authorizes transactions other than contracts, grants, or cooperative agreements for prototype projects that are directly relevant to enhancing the mission effectiveness of military personnel and supporting platforms, systems, components, or materials. It also sets conditions for follow-on production awards without further competition.

According to GAO reports issued over several years, Army organizations, including Program Executive Offices and the Army Contracting Command, expanded OTA use for software, sensors, munitions-related prototypes, and command-and-control tools. Officials said OTAs allowed faster award than Federal Acquisition Regulation contracts. The record shows GAO did not dispute the existence of the authority. It questioned whether particular awards met the statute’s tests.

10 U.S.C. 4022 requires that a prototype project be directly relevant to enhancing mission effectiveness. GAO found that some Army files described work that resembled sustainment, integration of already-fielded systems, or production-like quantities rather than a discrete prototype. In those cases, according to the reports, documentation did not always show how the effort differed from a conventional procurement. The Army, in agency comments summarized by GAO, said program offices applied internal guidance and that prototypes can include iterative development.

Competition is not forbidden under OTAs, but the statute and DoD implementing guidance expect agencies to use competitive procedures to the maximum extent practicable. GAO found that a substantial share of Army prototype OTAs went to a single performer or to a consortium after limited outreach. The reports described notices posted for short periods, statements of work tailored to a known vendor, or reliance on a consortium’s internal down-select that the Army did not independently document. Officials said consortia provide industry access and that follow-on work stays with the performer that successfully completed the prototype.

Follow-on production under 4022(f) is the flashpoint. The statute permits a follow-on production transaction without the use of competitive procedures if competitive procedures were used for the prototype and the participants in the prototype successfully completed it. GAO found Army files in which the prototype phase was not clearly competed, completion was not defined in measurable terms, or the follow-on effort expanded scope and quantity beyond what the prototype file described. In some dockets, according to GAO, the follow-on resembled a sole-source production contract without the justifications required under the FAR.

Public IG material and congressional testimony have tracked the same pattern. The Department of Defense Inspector General has reported that some Other Transaction files lacked evidence that the prototype was completed as defined, or that the follow-on was limited to the successful prototype. The Army’s position, as paraphrased in those reviews, is that OTAs are intended to be flexible and that consortium models satisfy competition when multiple members can bid internally.

Budget exhibits and Selected Acquisition Reports show growth in Army OTA obligations relative to traditional contracting in several portfolios. GAO did not claim that growth itself violated 4022. It said the statute’s conditions do not scale automatically with dollar volume. Where awards exceeded typical small-prototype ranges, the reports said files should show why the effort remained a prototype and why follow-on production without competition was authorized.

GAO recommendations have been consistent: define prototype completion in the agreement; document competitive procedures used for the prototype; and, before a noncompetitive follow-on, record that the statutory predicates were met. The Army has concurred with some recommendations and described policy updates, including additional legal review for follow-on production. Subsequent GAO work has found partial implementation. Some commands improved file checklists. Others, according to later reports, still awarded follow-ons on files that did not show independent Army assessment of consortium competitions.

Court and GAO bid-protest dockets add a narrower slice. Protesters have argued that an Army OTA was a procurement contract in substance or that a follow-on production award should have been competed. GAO’s bid-protest jurisdiction over OTAs is limited; many protests are dismissed for lack of jurisdiction. Where GAO reached the merits of related FAR awards or where courts described the statutory scheme, the opinions have cited 4022’s prototype and follow-on tests rather than inventing a new standard.

The record does not show a finding that every Army OTA was unlawful. It shows a recurring documentation and definition problem: awards labeled prototypes under 4022, then converted to production-scale work without a file that tracks the statute’s competition and completion requirements. Named institutions in the reviews include the Department of the Army, Army Contracting Command, selected Program Executive Offices, GAO, and the DoD IG.

Congress has amended Other Transaction statutes more than once, including dollar thresholds and reporting. 10 U.S.C. 4022 remains the prototype authority the Army cites. GAO’s findings, as published, are that citing the statute is not the same as meeting it. Public budgets, IG reports, and dockets already show the gap between the authority as written and the files as kept.