The award nobody has to compete for
Almost everything the Department of Defense buys has to be competed, and the exceptions are narrow, documented, and publicly justified. The follow-on production authority at 10 U.S.C. § 4022(f) is the widest of them. A firm that won a prototype other transaction competitively, and finished it, can receive a production contract or transaction "without the use of competitive procedures, notwithstanding the requirements of chapter 221" of title 10. No new solicitation. No new field of offerors. No Federal Acquisition Regulation Part 6 justification. The statute sets no ceiling on the size of that follow-on.
That is a large amount of authority resting on a small number of facts, and the facts are set years before anyone invokes them. By the time a program office wants to use § 4022(f), the answer already sits in a file: how the prototype participants were selected, what the solicitation said, what the signed agreement said, and whether the prototype was finished. None of it can be repaired afterward.
This is a piece about that file: the chain of documents that makes a no-recompete award lawful and lets it survive scrutiny.
The two conditions in the statute
Paragraph (f)(1) is the enabling sentence. A transaction entered into for a prototype project "may provide for the award of a follow-on production contract or transaction to the participants in the transaction." Paragraph (f)(2) is the operative one. The follow-on may be awarded without competitive procedures, and the statute now adds "even if explicit notification was not listed within the request for proposal for the transaction," provided two things are true:
(A) Competitive procedures were used for the selection of parties for participation in the transaction. This is about how the prototype was awarded, not how the production is awarded.
(B) The participants in the transaction successfully completed the prototype project. This is about performance, and it is judged by the government against whatever the agreement says completion means.
Both conditions are backward-looking. Neither can be satisfied by anything a firm does after the prototype ends. That is the whole strategic point of the provision and the reason it is worth negotiating carefully at the front.
Condition A has a definitional seam in it
"Competitive procedures" is a defined term. Chapter 221 of title 10 defines it as procedures under which the head of an agency enters into a contract pursuant to full and open competition, plus a short list of enumerated alternatives. An other transaction is not a contract, so the definition does not map onto one on its own terms, and § 4022 supplies no clause saying a competitive request for prototype proposals counts. In practice the government treats a genuine competition as satisfying (f)(2)(A): a consortium request distributed to the full membership with a real field of respondents, or a general solicitation with published evaluation criteria and a documented down-select. The gap is bridged by the record, not by a citation.
The commercial solutions opening authority handles this more cleanly. Under 10 U.S.C. § 3458(b), use of the general solicitation competitive procedures in that section "shall be considered to be use of competitive procedures for purposes of chapter 221." That sentence has no counterpart in § 4022. Where a prototype was selected out of a commercial solutions opening, the competition question answers itself.
The practical consequence runs one direction. A prototype other transaction awarded sole source, on an unsolicited proposal, or through a directed selection can never produce a no-recompete follow-on under (f)(2). The chain breaks at the first link. Before signing, establish that the selection is competitive and that the agreements officer's file will say so.
Condition B is the one that fails
The leading decision is Oracle America, Inc., B-416061 (May 31, 2018), and it remains the clearest description of how this authority breaks. The Army had awarded a follow-on production other transaction to REAN Cloud with a not-to-exceed value of $950 million, later reduced under direction from the department to $65 million. The Government Accountability Office sustained the protest on two independent grounds.
The first was documentary. The prototype agreement itself contained no provision for a follow-on production award. GAO rejected the argument that references in the earlier commercial solutions opening cured it, holding that the "transaction" the statute speaks of is the legal instrument itself, and not the solicitation documents.
The second ground is the one that still decides cases. The prototype agreement had been modified to add enclave migration work, and that work was unfinished when the production award issued. GAO found the agency's position internally inconsistent: it could not treat the modifications as validly extending the scope and the period of performance while also treating the prototype as complete. Finishing parts of a project is not finishing the project.
Congress has since overtaken the first ground, at least in the statute. Nothing has overtaken the second. "Successfully completed" is not defined anywhere in § 4022, which means it is defined in the agreement or by whoever holds the pen at the end of the period of performance. Public guidance frames the determination around meeting the key technical goals of the project, satisfying success metrics written into the prototype agreement, or achieving a particularly favorable result — all of which point back at metrics the agreement has to contain in the first place.
Two things follow. Write completion as measurable, testable results: a detection rate at a stated false-alarm rate, a latency budget under a stated load, an integration verified by a named test against a named system. And treat every modification as a moment to restate what completion means for the changed scope, because a growing statement of work moves the finish line.
The clause the statute stopped requiring and the regulation still wants
Here is the seam most firms miss. The statutory text permits the follow-on "even if explicit notification was not listed within the request for proposal." The regulation on the FAR side has not moved with it.
DFARS 206.001-70 excepts follow-on production contracts for products developed under § 4022 prototype authority from the competition requirements of FAR Part 6, but only where the contracting officer receives sufficient documentation from the agreements officer who issued the other transaction showing two things: that the other transaction solicitation and the agreement included provisions for a follow-on production contract, citing § 4022(f)(1); and that, where applicable, the threshold at § 4022(a)(2)(C) and the requirements at § 4022(f)(2)(A) and (B) have been met. Further direction sits in the corresponding PGI section.
Read the two texts together and the answer is unambiguous in practice even though they are not aligned in theory. A contracting officer works from the regulation. The regulation asks for the provision. If the provision is not there, the file stalls while lawyers argue about which text governs, and the schedule pressure that made an other transaction attractive evaporates. Put the follow-on production provision in the solicitation and carry it into the signed agreement. It costs nothing at negotiation and it is the single cheapest piece of insurance in the instrument.
Competition, and nothing else
DFARS 206.001-70 removes the follow-on from Part 6 competition requirements. It removes nothing else. Where the follow-on is a FAR contract, the rest of the regulation arrives with it: pricing rules for the contract type, Cost Accounting Standards coverage once the thresholds are met, certified cost or pricing data where applicable, and the standard DFARS data rights clauses. Separately, § 4022(c)(1) requires any agreement providing for payments over $5,000,000 to carry a clause giving the Comptroller General access to records. Non-competitive is not unexamined.
Consortium subprojects, after the 2025 rewrite
Most prototype dollars under this authority move through consortia: a base agreement between the government and a consortium manager, with individual project agreements awarded to member firms underneath it. That structure used to raise an ugly question. If the follow-on depends on completion of "the prototype project," and the transaction is the base agreement, does one member's failed subproject block everyone?
Three paragraphs added by the FY2025 National Defense Authorization Act settle it. Paragraph (f)(1) now states that a transaction includes all individual prototype subprojects awarded under the transaction to a consortium. Paragraph (f)(3) permits a follow-on award when the department determines that an individual prototype or prototype subproject as part of a consortium was successfully completed. Paragraph (f)(4) states that such an award is not contingent upon the successful completion of all activities within a consortium.
For a member firm the reading is favorable and specific: the completion determination is made at the level of the subproject the firm actually performed. Confirm it in the project agreement anyway, because the determination still has to be written by someone, and the language that governs it is the language in front of them.
Who counts as a participant
The statute says the follow-on may be awarded "to the participants in the transaction." That phrase does real work. The parties to the prototype agreement are participants. A firm that performed as a subcontractor to a prototype awardee, without being a party to the transaction, is not obviously inside that phrase, and the question gets decided by the agency against the instrument as written.
That changes how a teaming conversation should go when production is the point. A firm bringing the differentiating technology into someone else's prototype bid has two structural options: become a party to the transaction, or accept that its access to production runs through a commercial agreement with the prime rather than through the statute. Both are workable. Only one is under the firm's own control later, and the difference stays invisible until the follow-on is on the table.
The approval ladder above $100 million
Non-competitive does not mean unapproved, and the approvals for the follow-on are separate from the approvals for the prototype.
On the prototype side, § 4022(a)(2)(A) requires a written determination by the head of the contracting activity, or by the agency director for the Defense Advanced Research Projects Agency, the Defense Innovation Unit, and the Missile Defense Agency, for a prototype expected to cost more than $100,000,000 but not more than $500,000,000. Above $500,000,000, subparagraph (B) moves the determination to the senior procurement executive designated under 41 U.S.C. § 1702(c), and requires written notice to the congressional defense committees at least 30 days before the authority is exercised.
Subparagraph (C) is the one that governs the follow-on. For a follow-on production contract or transaction above $100,000,000 including all options, a covered official must determine in writing that the requirements of the prior prototype project were met, that the requirements of subsection (f) will be met, and that use of the authority is essential to meet critical national security objectives — and must notify the congressional defense committees in writing of those determinations. DFARS 206.001-70 points the contracting officer at that same threshold.
For schedule planning this is the item most often left out of a transition plan. Below the threshold the path is short. Above it, the file has to travel to a named official and then to Capitol Hill, and neither of those steps moves on a program manager's calendar.
The instrument on the other side is the government's choice
Paragraph (f)(5) lets the follow-on be awarded using the other transaction authority in subsection (a), under chapter 137 of title 10 as an ordinary procurement contract, or under such procedures, terms, and conditions as the Secretary of Defense may establish. The firm does not pick.
Public reporting says which way the department leans on larger programs. In a September 3, 2025 report, GAO found that ten of eighteen selected weapon systems using prototype other transactions planned to switch to standard contracts for production. GAO also found that the department does not track the FAR production contracts that result from prototype other transactions, and recommended it build a systematic process to do so.
That second finding is a fact about the evidence rather than about the authority, and it matters when someone quotes a conversion rate. Nobody inside or outside the department can currently state how often prototype other transactions become production awards through this provision. Any number offered as that rate is an estimate.
Four ways to get a production award without a new competition
Section 4022(f) is not the only route, and picking the right one is a question about what the underlying work is rather than about which authority sounds strongest.
| Axis | § 4022(f) follow-on | § 3458(c) CSO follow-on | SBIR Phase III sole source | FAR 6.302 justification |
|---|---|---|---|---|
| What it rests on | A competitively selected prototype other transaction that was successfully completed | A competitive general solicitation for commercial products, commercial services, or nondevelopmental items | Work that derives from, extends, or completes a prior SBIR or STTR award by the same firm | An agency finding that one of the enumerated circumstances applies to this requirement |
| Competition record needed | Documentation that competitive procedures selected the prototype parties | Settled by statute: § 3458(b) deems the general solicitation procedures to be competitive procedures | The earlier competitive SBIR selection carries forward; no new competition contemplated | None; the justification explains why competition is not being used |
| Paperwork that unlocks it | Agreements officer documentation under DFARS 206.001-70; no Part 6 justification required | Approval under the section, with congressional notification for awards over $100 million within 45 days | Competition authority at FAR 6.302-5(b)(4), invoking 15 U.S.C. § 638(r)(4) | Written justification, approved at a level tied to value, made publicly available after award |
| Ceiling | None in the statute; a written determination and congressional notice apply above $100 million | None stated for the follow-on; awards over $100 million trigger notification | No dollar ceiling, no time limit, any funding source, any agency | Set by the requirement, not the authority |
| Instrument | Government's choice under (f)(5): other transaction, chapter 137 contract, or established procedures | Contract, required to be fixed-price including fixed-price incentive | A FAR contract with SBIR clauses and SBIR data rights | A FAR contract |
| Where it usually breaks | The completion determination, or a missing follow-on provision in the agreement | Fit: the item has to be commercial or nondevelopmental | Proving the derivation from the earlier award | The justification has to survive review on the merits |
The commercial solutions opening route got wider
The FY2026 National Defense Authorization Act, Public Law 119-60, signed December 18, 2025, rewrote 10 U.S.C. § 3458. The word "innovative" came out of the scope, so the section now reaches commercial products, commercial services, and nondevelopmental items acquired through competitive selection of proposals resulting from a general solicitation and a peer review, technical review, or operational review. The review requirement is stated in the alternative, which lets a program office pick the one that fits.
Subsection (c) carries follow-on production authority, including a sole source contract, out of a competitively conducted opening. Contracts under the section are required to be fixed-price, including fixed-price incentive, and awards exceeding $100 million carry a congressional notification requirement within 45 days.
For a firm selling something already commercial, this is the cleaner story. The § 4022 route requires characterizing the work as a prototype project, an awkward fit for a product that already exists and already sells. Section 3458 asks a different question and settles the competitive-procedures point by statute. The tradeoff is the fixed-price requirement, which is a pricing discipline rather than a paperwork one and favors firms that know their own cost structure well.
What a competitor can still reach
A no-recompete award is not an unreviewable one, and the review surface concentrates here.
GAO's description of its own jurisdiction is narrow and stable: because an other transaction is not a procurement contract, GAO does not review the award itself, but it does "review protests alleging that an agency is improperly using a non-procurement instrument to procure goods or services," examining whether the agency's use of its discretionary authority was proper. That is the door the 2018 decision walked through to reach a follow-on worth nearly a billion dollars at its ceiling. The narrowness of the jurisdiction did not protect the award. The defects in the file decided it.
The Court of Federal Claims is the other forum, with jurisdiction under 28 U.S.C. § 1491(b)(1) over any alleged violation of statute or regulation "in connection with a procurement or a proposed procurement." A follow-on production award is the point in the life of an other transaction that looks most like a procurement, which is why it draws attention.
The defense is the same in both forums and it is documentary. A follow-on resting on a competitive selection recorded in the agreements officer's file, a follow-on production provision present in both the solicitation and the signed agreement, and a completion determination written against measurable criteria is a hard target. One resting on any of those being assumed is not.
The record, in the order it gets created
Seven documents, and when each one has to exist
Items one through three are negotiable. Item four is a discipline. Items five through seven belong to government officials, and the only influence a firm has over them is the quality of the first four.
What to fix in the agreement, plainly
- A follow-on production provision in the solicitation and repeated in the signed agreement, even though the statute no longer conditions the award on the notification
- Completion criteria stated as measurable results with named thresholds, named test conditions, and a named verifying activity
- A restatement of the completion standard attached to every scope-changing modification
- Confirmation, for consortium work, that the completion determination is made at the subproject level under § 4022(f)(3)
- Party status for any firm whose access to the production work should not depend on somebody else's goodwill
- A background intellectual property schedule and per-deliverable license grants, since the follow-on inherits whatever the prototype established
- An early answer on whether the follow-on will exceed $100 million, which changes who signs and how long it takes
Common objections, answered plainly
Isn't this just sole-source contracting with a different label?
The outcome resembles it; the mechanism does not. A FAR sole-source award requires a written justification explaining why competition is not being used, approved at a level tied to value and made publicly available after award. A § 4022(f) follow-on requires no such justification, because DFARS 206.001-70 takes it outside Part 6 entirely. What replaces it is documentation from the agreements officer that a competition already happened and the prototype was completed. The competition is not waived. It is relocated to an earlier date.
Our prototype was awarded without competition. Is the follow-on still available?
Not under this provision. Paragraph (f)(2)(A) conditions the no-competition follow-on on competitive procedures having selected the parties. A directed award, an unsolicited-proposal award, or a sole-source prototype fails that condition permanently. The production work would have to be competed, justified under FAR Part 6 on its own facts, or reached through a different authority such as SBIR Phase III where the firm's history supports it.
If both conditions are met, does the government have to award the follow-on?
No. Section 4022(f) removes a barrier; it creates no entitlement. The government may award, may compete the production work anyway, or may do nothing. The authority is permissive throughout, and using it still depends on a sponsor and an appropriation that no statutory language supplies.
Does a consortium teammate's failure block our follow-on?
Not under the current text. Paragraph (f)(3) allows the determination at the level of an individual prototype or subproject within a consortium, and (f)(4) states that the award is not contingent upon successful completion of all activities within the consortium. Those paragraphs were added for exactly this problem.
Bottom line
The no-recompete follow-on is one of the strongest positions in defense acquisition, and it is won at the beginning rather than at the end. Two facts control it: a competitive selection for the prototype, and a documented completion of the work. A regulation that has not caught up with the statute adds a third practical requirement, a follow-on production provision written into the solicitation and the agreement. Above $100 million, a named official and the congressional defense committees join the sequence.
Everything a firm can influence sits in the negotiation and in the discipline of restating what completion means each time the work changes. That is unglamorous drafting, done under schedule pressure, at a moment when production feels far away. It is also the difference between a production award made on a memo and one competed against a field that watched the prototype from the outside.
Frequently asked questions
Yes, where the two conditions in 10 U.S.C. 4022(f)(2) are satisfied: competitive procedures selected the parties to the prototype transaction, and the participants successfully completed the prototype project. DFARS 206.001-70 then takes the resulting contract outside FAR Part 6 once the contracting officer receives the required documentation from the agreements officer.
A provision stating that a follow-on production contract or transaction may result, and measurable criteria defining successful completion. The statute now permits the award even where explicit notification was absent from the request for proposals, but DFARS 206.001-70 still directs the contracting officer to obtain documentation that both the solicitation and the agreement included follow-on production provisions. Write the provision in.
The government, through a written determination by the responsible approving official, judged against what the agreement says. The statute does not define the phrase. Public guidance frames the determination around meeting the key technical goals of the project or satisfying success metrics written into the prototype agreement, which is why the metrics belong in the agreement rather than in correspondence.
No ceiling appears in 10 U.S.C. 4022(f). Above $100,000,000 including all options, subparagraph (a)(2)(C) requires a covered official to determine in writing that the prior prototype requirements were met, that the subsection (f) requirements will be met, and that use of the authority is essential to meet critical national security objectives, with written notification to the congressional defense committees. That is an approval step, not a limit.
The statute speaks of awarding the follow-on to "the participants in the transaction." A firm that performed under a prototype awardee without being a party sits outside that phrase on its face, and the agency resolves the question against the instrument as written. Where production access matters, the two clean answers are party status on the transaction or a commercial agreement with the prime that survives into production.