The partner who opens the gate
Prototype teams get built in the wrong order. A prime picks the technical partners it wants, prices the work, writes the volume, and then goes looking for someone to satisfy the nontraditional requirement a week before submission. That order is expensive, because the nontraditional participant is not a signature at the bottom of a page. Under 10 U.S.C. § 4022(d)(1), the Secretary of Defense has to ensure that no official enters into a prototype other transaction unless one of four conditions is met. Without a qualifying condition there is no agreement to sign, however good the technical case is.
That single sentence changes the negotiating position of the smaller firm in the room. On a FAR competition, a small subcontractor is a scoring input and a subcontracting-plan line. On a prototype other transaction, the same firm can be the reason the instrument is available at all. Teams that understand this write the participation case into the proposal on purpose. The rest assert it in a sentence and hope the agreements officer accepts it.
The money involved is not marginal. GAO reported in September 2022 that the Department of Defense obligated more than $24 billion on other transaction awards to consortia for prototyping across fiscal years 2019 through 2021, close to two thirds of all prototype other transaction dollars in that period, across 28 consortia that four organizations largely managed. Every one of those agreements had to clear the same four-condition test.
How well each seat protects the partner at follow-on
Editorial weighting of how durable each position is when a non-competitive follow-on is awarded under § 4022(f). Read from the statutory text, not a measured outcome.
The four conditions, and which one a team is actually using
The conditions at § 4022(d)(1) are short enough to read in full, and the differences between them decide how a team gets built.
(A) A nontraditional or nonprofit participant. "There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project." One qualifying participant is enough. The rest of the team can be anyone, including the largest defense primes in the country.
(B) An all-qualifying team. "All significant participants in the transaction other than the Federal Government are small businesses (including small businesses participating in a program described under section 9 of the Small Business Act (15 U.S.C. 638)) or nontraditional defense contractors." This one reaches every significant participant, so a single traditional prime on the team closes it. The parenthetical pulls SBIR and STTR participants in by name.
(C) One-third non-federal cost. "At least one third of the total cost of the prototype project is to be paid out of funds provided by sources other than the Federal Government." A cost-share route that does not depend on anyone's status.
(D) An exceptional-circumstances determination. The senior procurement executive determines in writing that exceptional circumstances justify innovative business arrangements that would not be feasible under a contract, or that would expand the defense supply base in a way a contract could not. Slow, senior, and uncommon.
For a mixed team with a large integrator on it, condition (A) is the only realistic door, and it swings on one participant. For a team of small firms, condition (B) is often satisfied without anyone doing anything, but only while every significant participant qualifies. Adding one large partner late in the capture moves a team from (B) to (A) without anyone noticing, which is fine if the (A) participant is real and a problem if the only nontraditional on the roster carries two percent of the work.
The status test is cost accounting, not size
The definition sits at 10 U.S.C. § 3014. A nontraditional defense contractor is "an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the Department of Defense for the procurement or transaction, any contract or subcontract for the Department of Defense that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41."
Read that carefully, because almost every common assumption about it is wrong. The test is not company size. It is not revenue. It is not whether the firm has held defense work before, and it is not whether the firm is new. It is a single question about cost accounting standards coverage, applied to the entity, over a one-year lookback.
Run the arithmetic and the population turns out to be enormous. Under 48 CFR 9903.201-2, full CAS coverage attaches to a business unit that receives a single CAS-covered award of $50 million or more, or that received $50 million or more in net CAS-covered awards during its preceding cost accounting period. Below that, coverage is modified rather than full. And 48 CFR 9903.201-1 exempts whole categories outright, including contracts and subcontracts with small businesses, and negotiated contracts at or below the certified cost or pricing data threshold, which FAR 15.403-4 currently states as $2.5 million and which moves with the inflation adjustments at FAR 1.109.
Two consequences follow. A small business is nontraditional as a matter of arithmetic, because its contracts and subcontracts are exempt from CAS entirely, so it cannot be performing work subject to full coverage. And a firm can hold years of defense work, several development awards, and a subcontract on a major program and still qualify, because none of it reached full coverage. Losing the status takes real scale, applied at the business-unit level rather than across a whole corporation.
That last point deserves a diligence step rather than an assumption. A large company can have a business unit that is genuinely nontraditional while other units are not. Confirm which legal entity and business unit is on the team, get the representation in writing, and date it against the solicitation of sources rather than the award.
"Significant extent" is not defined anywhere
Here is the part teams underestimate. The statute requires participation "to a significant extent" and then never says what that means. The Congressional Research Service's standing report on the authority uses the phrase repeatedly without defining it. MITRE's public other transactions reference states the condition and offers no threshold. There is no percentage in the U.S. Code, no floor in dollars, and no bright line in the regulation.
What fills the gap is departmental guidance and the judgment of the agreements officer. The operative document is the DoD Other Transactions Guide, issued by the Under Secretary of Defense for Acquisition and Sustainment, currently the July 2023 edition. The determination lands in the agreement file, and it lands there because someone on the team wrote a case the official could adopt.
So write the case. Not a sentence asserting the status, which is the common failure, but a short passage saying what the participant contributes and how much of the work it holds. Name the entity and the business unit. State the share of the technical scope in hours, dollars, or named work packages. State what the participant brings that the rest of the team does not have. An agreements officer forced to construct that record alone will construct a thinner one than the team could have supplied.
Party, co-participant, subcontractor
This distinction decides what the partner is worth to itself, and it turns on wording in the statute that is easy to read past.
Condition (A) says the nontraditional must be "participating to a significant extent in the prototype project." Condition (B) says all significant participants "in the transaction" must qualify. Those are not the same object. A prototype project is the work; a transaction is the signed agreement. On the face of the text, a firm can participate significantly in the project without signing the transaction, which is why a major subcontractor can open condition (A) at all.
Now look at follow-on production. Section 4022(f)(1) says a prototype transaction "may provide for the award of a follow-on production contract or transaction to the participants in the transaction," and (f)(2) authorizes that award without competitive procedures to the same group. The follow-on provision uses the narrow phrase. Whoever is a participant in the transaction is inside that door. Whoever is only a supplier to a participant holds a commercial subcontract and nothing more.
The consortium model gives a third option. CRS describes arrangements in which members act as co-prime contractors with the government under a base agreement, with project agreements underneath. Where a project agreement names multiple performing members, each named member has a far stronger claim to being a participant in the transaction than a firm sitting one tier down under a single member's subcontract.
None of this makes subcontracting the wrong answer. It is often the right one, for reasons of speed, security, and who wants the administrative burden. It does mean the choice should be deliberate, with the follow-on consequence understood by both sides rather than discovered two years later.
What follow-on production does to the roster
Section 4022(f) is why the seat matters. A follow-on production contract or transaction may be awarded to the participants without competitive procedures if two things are true: competitive procedures were used to select the parties for participation in the transaction, and the participants successfully completed the prototype project.
The current text is broader than a lot of older commentary suggests. Section 4022(f)(2) authorizes the non-competitive follow-on "even if explicit notification was not listed within the request for proposal for the transaction." A missing follow-on notice in the original solicitation is no longer fatal. Getting the language into the agreement remains the better practice, because it sets expectations and makes the eventual determination easy, but the statute does not condition the award on it.
The consortium provisions go further in the team's favor. Section 4022(f)(1) states that a transaction includes all individual prototype subprojects awarded under it to a consortium of United States industry and academic institutions. Subsection (f)(3) allows a follow-on when the department determines that an individual prototype or subproject within a consortium was successfully completed, and (f)(4) states that the award is not contingent on the successful completion of all activities within that consortium. One subproject can succeed and reach production while others do not.
Status is tested at the prototype, not at production
Section 4022(d)(3) states that the requirements of subsection (d) do not apply to follow-on production contracts or transactions under subsection (f). The four conditions gate the prototype agreement. They do not gate the follow-on. A partner whose status opened the door at the prototype stage does not have to still be nontraditional when production is awarded. What has to survive is the participant relationship, not the classification.
Sequence: when each decision has to happen
Most of the damage here comes from ordering, not ignorance. Status, scope split, and the intellectual property schedule all have to be settled before the proposal is written, because each one changes what the proposal says.
Team formation sequence for a prototype other transaction
Step six is the one that gets skipped. The teaming agreement is a private contract between companies. The project agreement is the instrument the government signs. If the teaming agreement says a firm is a participant and the project agreement does not name it, the project agreement wins on every question that involves the government, including the follow-on.
Cost share as the second door
Condition (C) ignores status entirely. If at least one third of the total cost of the prototype project comes from sources other than the federal government, the agreement is available regardless of who is on the team. In practice this is how large firms reach the instrument without a nontraditional partner.
Section 4022(d)(2) sets the counting rule, and it matters for anyone planning contributions. Amounts counted as provided by a party do not include costs incurred before the date the transaction becomes effective. The exception is narrow: costs incurred after the beginning of negotiations may count if the responsible official determines that the party incurred them in anticipation of entering into the transaction and that counting them is appropriate to ensure successful implementation.
Read that as a scheduling instruction. Investment made a year earlier, before anyone was negotiating, is background contribution and does not count toward the one third. Teams planning to rely on cost share should raise the counting question early and in writing.
Intellectual property across a team with no default clauses
An other transaction is not a procurement contract, so the standard DFARS data rights clauses are absent unless the agreement adopts them. On a single-company agreement that is a negotiation. On a team it is a negotiation with more than two sides, because whatever the government gets flows through whoever signed, and whoever signed has to hold the rights to grant it.
Every party attaches its own background IP schedule. Components, models, libraries, datasets, and tools that predate the project, listed by name. Anything unlisted risks being treated as developed under the agreement, and a subcontractor's unlisted asset is the easiest one to lose because the subcontractor is not in the room when the terms are negotiated.
The prime cannot grant what it does not hold. If the government asks for rights in a partner's core model, that grant has to exist in the subcontract before it can exist in the agreement. Discovering the gap after acceptance is a bad outcome for the prime as well as the partner.
Third-party and open-source components get named with their licenses. A copyleft dependency found inside a delivered container is a problem that lands on the signatory regardless of which teammate introduced it.
Data is its own asset. Training sets, fine-tuned weights, evaluation data, and prompt libraries carry separate value, and a clause drafted for technical data often fails to say which of them it reaches. Allocate them explicitly, per party.
What the nontraditional partner should ask for
A firm whose status opens the gate supplies something the team cannot get elsewhere on short notice. The reasonable asks are specific, and a prime can grant all of them without giving up control.
A named role in the signed project agreement, or a written explanation of why not. The follow-on language runs to participants in the transaction. If the answer is subcontract, the teaming agreement should say what happens at follow-on in concrete terms.
A defined, priced scope. Significant participation is easier to defend when it is a work package with a number attached than when it is a paragraph of description.
Commercial treatment where it applies. DFARS 212.102(a)(iv) permits contracting officers to treat supplies and services provided by nontraditional defense contractors as commercial products or commercial services, with the file documented accordingly. That posture carries into related FAR work and is worth raising rather than waiting for someone else to raise it.
Termination terms that both sides can live with. If the partner opening condition (A) can be removed at the prime's convenience, the condition can evaporate mid-performance.
Three ways to seat the partner
| Question | Named party to the project agreement | Co-participant under a consortium award | Subcontractor to a party |
|---|---|---|---|
| Opens condition (d)(1)(A) | Yes, on the plain text | Yes, on the plain text | Yes if participation in the project is significant; the text reaches the project, not only the transaction |
| Named in the signed instrument | Yes | Yes, where the project agreement names performing members | No; the relationship is a private subcontract |
| Standing at follow-on under § 4022(f)(2) | Strongest; the provision runs to participants in the transaction | Strong; (f)(3) and (f)(4) let a single subproject succeed on its own | Depends entirely on the prime's subcontract and its willingness to carry the partner forward |
| Who negotiates IP with the government | The partner, directly | The partner, through the consortium manager and the agreements officer | The prime, on the partner's behalf, using rights the subcontract gave it |
| Administrative burden | Highest; direct reporting, milestones, and invoicing | Moderate; membership plus project administration | Lowest; the prime absorbs the government-facing work |
| Best fit | A distinct, separable deliverable | An existing member with domain-aligned work | A component inside someone else's system |
What belongs in the teaming agreement
- A dated status representation naming the legal entity and business unit, tied to the solicitation of sources rather than the award date
- The technical scope split, with named work packages and a price or hour share for each party
- A background IP schedule per party, with third-party and open-source components and their licenses listed
- The seat decision in writing: party to the agreement, consortium co-participant, or subcontractor, and what changes at follow-on
- Exclusivity scope and duration, stated narrowly enough that it does not foreclose unrelated work
- Data handling, export control, and controlled unclassified information terms, since the FAR clause that would have supplied them is absent
- Termination terms, plus a notice obligation if any party's status changes during performance
Where these awards come from
Two channels carry most of the work. The consortium channel dominates by dollars: a sponsor signs one base agreement with a consortium management firm, and members compete for project agreements underneath it. Advanced Technology International describes managing more than thirty collaborations, among them the National Armaments Consortium, the Medical CBRN Defense Consortium, the Information Warfare Research Project, and the Training and Readiness Accelerator. NSTXL manages S2MARTS, sponsored out of Naval Surface Warfare Center Crane, the Space Enterprise Consortium, and the Microelectronics Commons network. The direct channel is smaller and faster: the Defense Innovation Unit states that it can award prototype agreements in as few as 60 to 90 days, principally using other transaction authority.
Size changes who signs. Under § 4022(a)(2), a prototype transaction between $100 million and $500 million requires a written determination by the head of the contracting activity, or by the agency director for DARPA, the Defense Innovation Unit, and the Missile Defense Agency. Above $500 million, the determination moves to the senior procurement executive and the congressional defense committees get written notice at least 30 days before award. Teams approaching those lines should build the approval time into the schedule.
Common objections, answered plainly
Isn't the nontraditional requirement just a formality?
It is a precondition on the instrument. Section 4022(d)(1) directs that no official enter into the transaction unless a condition is met. A team that cannot support one of the four conditions is not eligible for the authority, which means the requirement is closer to a jurisdictional test than to an evaluation factor.
Can a subcontractor satisfy the nontraditional condition?
The text of condition (A) reaches participation in the prototype project rather than participation in the transaction, and condition (B) uses the narrower phrase, so the drafting distinction is deliberate. Practice still varies by agency and by agreements officer, and the determination goes in the agreement file. Support it with a written participation case rather than an assertion, and confirm the reading with the agreements officer before relying on it.
Does the team have to keep the partner through production?
The conditions do not apply to follow-on production at all, under § 4022(d)(3). What matters at follow-on is who counts as a participant in the transaction and whether the prototype was successfully completed. A partner that is not a participant has no statutory claim on the follow-on, whatever it contributed at the prototype stage.
Bottom line
Three decisions carry most of the value in this kind of teaming, and all three get made before anything is submitted. Which of the four conditions the team is running through, and whether it will still hold if the roster changes. Whether the nontraditional partner is a party to the transaction, a consortium co-participant, or a subcontractor, decided on purpose rather than by default. And whether the participation case is written down in enough detail that the agreements officer can adopt it without inventing a record.
Get those right and the instrument does what it is supposed to do: fast award, negotiated terms, and a production path that does not require a second competition. Get them wrong and the team may still get an agreement, but the partner who opened the gate will be standing outside it when production is awarded. None of it substitutes for a technical case a program office wants. The statute controls who may sign and on what terms. It has never made anyone want the prototype.
Frequently asked questions
Under 10 U.S.C. § 3014, an entity that is not currently performing, and has not performed for at least the one-year period preceding the solicitation of sources, any Department of Defense contract or subcontract subject to full coverage under the cost accounting standards. The test is CAS coverage, not size. Because 48 CFR 9903.201-1 exempts contracts and subcontracts with small businesses from CAS entirely, a small business qualifies as a matter of arithmetic.
The statute does not say, and neither the Congressional Research Service's report nor MITRE's public reference supplies a threshold. The determination is made by the agency and documented in the agreement file, guided by the DoD Other Transactions Guide. Teams should supply the record: named scope, share of the work, and what the participant brings that no one else on the team has.
Under condition (A), yes. One nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project satisfies the condition, and the rest of the team can be traditional contractors of any size. Condition (B) is the opposite: it reaches every significant participant in the transaction, so one traditional participant closes it.
Yes, under 10 U.S.C. § 4022(f)(2), when competitive procedures were used to select the parties for participation in the transaction and the participants successfully completed the prototype project. The current text permits the award even if explicit notification was not listed in the original request for proposals, though including the language remains the better practice.
Generally not. Section 4022(d)(2) excludes costs incurred before the transaction becomes effective, with a narrow exception for costs incurred after negotiations begin on a determination by the responsible official.