The door a prime cannot open by itself
A large contractor decides to run a prototype effort as an other transaction. The technical plan is written, a program office wants the capability, and the money is identified. Then someone in the contracts shop asks which condition at 10 U.S.C. § 4022(d)(1) the project qualifies under, and the honest answer comes back: none of them, not as the team is currently drawn. That is not a filing error. It is the design of the statute: Congress attached the flexibility of the instrument to a condition about who is on the team, and made the presence of a qualifying participant a precondition of using the authority at all.
Most writing on this subject is aimed at the company that wants to be the qualifying participant. This one is aimed at the party across the table: the prime, the integrator, the consultancy standing up a delivery team, or the program office working out why its preferred contractor cannot carry the agreement alone. The question is not whether a nontraditional partner is nice to have. It is which of four statutory doors the project is going through, what each costs, and whether the partner named on the agreement will still look like a participant when a senior official has to sign a determination saying so.
Where a nontraditional participant carries the most weight for a prime
Editorial weighting from the statutory text. Illustrative rather than measured; each row is explained below.
What the statute actually requires
DoD's authority to award a prototype other transaction sits at 10 U.S.C. § 4022, recodified from the old § 2371b when Title 10 was reorganized. Subsection (d)(1) is the gate. An agency official may not enter into a prototype other transaction unless at least one of four conditions is met.
Condition (A). There is at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent in the prototype project.
Condition (B). All significant participants in the transaction other than the Federal Government are small businesses or nontraditional defense contractors.
Condition (C). 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.
Condition (D). The senior procurement executive for the agency determines in writing that exceptional circumstances justify the use of a transaction providing for innovative business arrangements or structures that would not be feasible or appropriate under a contract.
Read the four together and the shape of the policy is clear. Three of them describe a team the ordinary defense industrial base does not produce on its own. The fourth is an escape hatch that a senior official has to sign personally. There is no dollar floor anywhere in subsection (d). A $600,000 prototype agreement is subject to the same condition as a $600 million one.
Why the prime is usually the party that fails the test
The term is defined 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."
Every word of that turns on one thing: full CAS coverage. Not company size. Not revenue. Not headcount, and not whether the firm has held DoD work before. Under 48 CFR 9903.201-2, full coverage attaches to a business unit that receives a single CAS-covered contract 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, modified coverage applies. And 48 CFR 9903.201-1(b) exempts whole categories from CAS before the thresholds are even reached, including contracts and subcontracts with small businesses, negotiated contracts not in excess of the certified cost or pricing data threshold, and firm-fixed-price awards made on adequate price competition without certified cost or pricing data. FAR 15.403-4(a)(1) sets that data threshold at $2.5 million for prime contracts awarded on or after July 1, 2018.
Now run the same arithmetic on the prime. A company with the balance sheet, facility clearances, and program management depth to carry a nine-figure prototype has almost certainly taken a single CAS-covered award over $50 million, or cleared $50 million in net CAS-covered awards last year, or both. The status is lost by growth, and it is lost at exactly the scale that qualifies a firm to prime. This is the part that surprises people: the prime is not disqualified because of anything it did wrong. It is disqualified because it succeeded.
One nuance worth holding onto. The statutory definition speaks of an entity, while CAS attaches at the level of a business unit, and DFARS 212.102(a)(iv)(B) refers explicitly to "a business unit that is a nontraditional defense contractor." Where the line falls inside a large corporate family is a determination for the agreements officer on the facts, and it is not a question to answer optimistically in a teaming discussion.
The four doors, priced from the prime's side
Each condition is available to any project. They are not equally practical.
| Door | What it takes | What it costs the prime | When it is the right one |
|---|---|---|---|
| (A) Nontraditional or nonprofit research institution participating to a significant extent | One qualifying participant with real, describable scope on the project | Workshare given up, plus the diligence to confirm status and document participation | Almost always. It is the only door that scales with project size without new money or a senior signature |
| (B) All significant non-federal participants are small businesses or nontraditional contractors | Every significant participant qualifies, including the prime | The prime is excluded from its own team once it crosses the CAS line | Small-team prototypes led by a firm that has not scaled past full CAS coverage |
| (C) One third of total project cost from non-federal sources | Company money, at one third of the total, not one third of the government's share | On a $30M project, $10M of non-federal funds. Real capital at risk on a prototype | When the prime wants the resulting position badly enough to co-invest, and can defend the accounting |
| (D) Exceptional circumstances determined in writing by the senior procurement executive | A personal written determination by a named senior official | Schedule. It is a slow, individually justified exception, not a routine filing | Genuinely unusual business structures. Not a fallback for a team that was drawn without checking |
Cost share is a real door, and it is expensive
Condition (C) deserves its own arithmetic because it is the one people reach for when the teaming conversation goes badly. The statute asks for one third of total project cost from sources other than the Federal Government. If the government is putting in $20 million and that is two thirds of the total, the total is $30 million and the non-federal share is $10 million. That is not a rounding item on a prototype, and it has to be paid, tracked, and shown.
Whether a particular pool of company funds counts, and how it is measured and reported, is negotiated into the agreement rather than settled by a general rule, so get that answer from the agreements officer in writing before pricing around it. The comparison is simple: condition (A) costs workshare, condition (C) costs capital, and workshare is almost always cheaper than a third of the project.
Three labels that get confused, and the different work each does
A surprising share of teaming errors trace to treating three separate categories as one. They overlap heavily in practice and not at all in law.
| Label | What defines it | Which condition it opens | Where the prime verifies it |
|---|---|---|---|
| Nontraditional defense contractor | 10 U.S.C. § 3014: no DoD contract or subcontract subject to full CAS coverage, currently or for at least one year preceding the solicitation | Condition (A) on its own; also counts toward (B) | The firm's CAS coverage history, which is a representation the firm makes and the prime should capture in writing |
| Small business | § 4022(e)(4) points to a small business concern as defined under section 3 of the Small Business Act, 15 U.S.C. 632 | Counts toward (B) only. A small business alone does not satisfy (A) | Size status against the applicable NAICS code |
| Nonprofit research institution | Named in the text of condition (A) alongside nontraditional defense contractors | Condition (A), on the same footing as a nontraditional participant | The institution's own status and the scope it is actually performing |
Two consequences follow. Adding a small business subcontractor does not by itself open condition (A); it helps only under (B), and (B) fails the moment the prime is fully CAS-covered. And a university or nonprofit research institution is a first-class alternative to a company under (A), which some teams find easier to seat where the prototype needs instrumentation or independent evaluation.
"Significant extent" has no statutory definition
This is the part of the gate that decides real cases, and the statute does not measure it. Subsection (e) of § 4022 defines six terms: covered official, nontraditional defense contractor (by cross-reference to § 3014), service acquisition executive, small business, prototype project, and follow-on production contract or transaction. "Significant extent" is not among them. The phrase appears in the condition and is left to the people applying it.
For the prime this is the most consequential open question in the whole area, and the answer is not to argue the phrase. The answer is to build a record that makes the argument unnecessary. A participant whose scope can be stated in one sentence, whose share of the effort is visible in the work breakdown and the price, and whose absence would change the technical result is a participant nobody has to characterize. A participant described as "supporting" with an unbounded task and a small fixed fee invites a characterization, and a characterization made months later by someone who was not in the room is the risk.
Two failure patterns show up repeatedly. One is the token seat, where a qualifying firm is added late for status and given work that could be deleted without effect on the prototype. The other is the relabeled sub, where an existing supplier is renamed a participant while the arrangement stays what it was. Both leave a record whose weakest point is the sentence saying the condition is met.
The written determination is where a thin partner shows
Below $100 million, the condition still applies, but no separate senior determination about it is required by subsection (a)(2). Above that, the statute installs review, and the review is specifically about subsection (d).
For a prototype expected to cost DoD more than $100 million but not more than $500 million including all options, § 4022(a)(2)(A) requires a written determination by the head of the contracting activity — or, for DARPA, the Defense Innovation Unit, or the Missile Defense Agency, the director of the agency — that the requirements of subsection (d) will be met and that use of the authority is essential to promoting the success of the prototype project.
Above $500 million including all options, § 4022(a)(2)(B) raises it: the agency's senior procurement executive (or the director, for those same three agencies) determines in writing that subsection (d) will be met and that use of the authority is essential to meet critical national security objectives, and the congressional defense committees are notified in writing at least 30 days before the authority is exercised.
A follow-on production award above $100 million carries its own gate under § 4022(a)(2)(C): a covered official determines in writing that subsection (d) was met on the prototype transaction and that the requirements of subsection (f) will be met, and that the authority is essential to meet critical national security objectives, with written notice to the congressional defense committees at the time the authority is exercised. Subsection (e)(1) lists who a covered official is: a service acquisition executive, the Director of DARPA, the Director of the Defense Innovation Unit, the Director of the Missile Defense Agency, the Under Secretary of Defense for Acquisition and Sustainment, or the Under Secretary of Defense for Research and Engineering.
Read that as a design and it becomes useful. The larger the program, the more senior the person who has to put a name on the statement that the team qualifies. A prime that seated a partner thinly at proposal time is asking a service acquisition executive to sign that characterization later, on a program with congressional visibility.
The condition has no dollar floor; only the paperwork does
The determinations at § 4022(a)(2) begin at $100 million. Subsection (d)(1) begins at the first dollar. A small prototype agreement with no senior review is subject to exactly the same gate as a flagship program, which means a team that was never checked can carry a defect for the life of the agreement and into any follow-on that depends on it.
Software is a prototype under this statute
Primes on the services and digital side sometimes assume the authority is for hardware. The statute says otherwise. Section 4022(e)(5) defines "prototype project" to include a project that addresses a proof of concept, model, or process, including a business process; reverse engineering to address obsolescence; a pilot or novel application of commercial technologies for defense purposes; agile development activity; the creation, design, development, or demonstration of operational utility; or any combination of those.
"Business process" and "agile development activity" are in the text. A data pipeline, a model evaluation harness, a decision-support application, a modernization of a workflow that runs on paper today — all inside the definition as written. The teaming question in this article therefore applies to software programs on the same terms as to a hardware demonstrator.
The benefit that has nothing to do with other transactions
There is a second reason a prime cares about this status, and it sits entirely inside the FAR world. DFARS 212.102(a)(iv) gives contracting officers explicit authority around nontraditional defense contractors.
Under (a)(iv)(A), contracting officers may treat supplies and services provided by nontraditional defense contractors as commercial products or commercial services, in order to enhance innovation and investment, and doing so does not require a commercial product or commercial service determination. Under (a)(iv)(B), contracting officers shall treat services provided by a business unit that is a nontraditional defense contractor as commercial services when those services use the same pool of employees as used for commercial customers and are priced using a methodology similar to the methodology used for commercial pricing. Under (a)(iv)(C), the contracting officer documents the file when treating supplies or services from a nontraditional defense contractor as commercial.
For a prime building a supplier package under a FAR prime contract, that is a documented authority rather than a favor, and one of the few places where a supplier's status affects the prime's own pricing and compliance posture rather than only its eligibility. The status diligence done for an other transaction carries over to the FAR side of the same portfolio.
Follow-on production seats the same roster
Under § 4022(f)(2), a follow-on production contract or transaction provided for in a prototype transaction may be awarded to the participants without the use of competitive procedures if competitive procedures were used for the selection of parties for participation in the transaction, and the participants successfully completed the prototype project. Subsection (e)(6) defines the follow-on as a contract or transaction to produce, sustain, or otherwise implement the results of a successfully completed prototype project for continued or expanded use by DoD.
Read the words "the participants." The roster seated at prototype time is the roster that reaches the non-competitive follow-on. A prime treating the qualifying partner as a compliance formality on a $4 million prototype is drawing the shareholder list for whatever production award the prototype earns. That argues for picking a partner the prime would actually want on the program at scale, and for writing the agreement so the participation, the deliverables, and the follow-on expectations are stated rather than assumed.
It also argues for precision about "successfully completed." An agreement that defines completion against measurable acceptance criteria protects the whole team's path to production. One that leaves completion to someone's later satisfaction rests the non-competitive route on a judgment nobody wrote down.
What to verify before you name the partner
- Get the status in writing, at business-unit level, with the one-year lookback stated. The § 3014 test runs to the period preceding the solicitation of sources, so an undated assurance is not an answer.
- Confirm which condition the project is going through, and confirm it with the agreements officer, not internally. Teams that assume (A) and are actually relying on (B) discover it at the worst point.
- Write the participant's scope so it can be stated in one sentence. If describing it takes a paragraph of qualifiers, the participation is thin.
- Make the share of effort visible in the work breakdown and the price. A characterization argument is won by arithmetic, not adjectives.
- Ask what happens if the partner's status changes mid-performance. The test is tied to the solicitation period, but the agreement should still say what the program expects.
- Settle intellectual property before award, not at delivery. An other transaction supplies no default data rights clauses, so background IP schedules and per-deliverable license grants for every participant are teaming work.
- Say in the agreement whether a follow-on production award is contemplated, and define successful completion in measurable terms. Both are conditions of the § 4022(f) route.
When a prime does not need one
The counterweight matters, because the wrong answer wastes a partner's time and the prime's.
If the work is a well-defined buy of a mature capability, the instrument is wrong before the teaming question arises: an other transaction is for prototype projects, and a firm-fixed-price commercial acquisition under the FAR usually beats it on speed and simplicity for a small, clearly specified purchase. If the prime's own business unit has not crossed into full CAS coverage, it may open condition (A) on its own, and confirming that is cheaper than the teaming conversation. If the effort is already funded at one third or more from non-federal sources for independent reasons, condition (C) is available without changing the team.
And if the only role available is a seat with no scope, the right decision is to not add the partner at all. A participant added for status and given nothing to do is the weakest possible foundation for a determination somebody senior has to sign.
Common objections, answered plainly
Can't we just use the exceptional circumstances condition?
It exists, and it is a written determination by the agency's senior procurement executive that unusual business arrangements or structures justify the transaction. It is an individually justified exception rather than a routine filing, and it takes the time that implies. Teams that reach for it because the roster was drawn without checking the gate generally lose more schedule than the teaming conversation would have cost.
Our sub is a small business. Doesn't that satisfy the requirement?
Only under condition (B), which requires that all significant non-federal participants be small businesses or nontraditional defense contractors. If the prime's own business unit is fully CAS-covered, (B) is closed and the small business does not by itself open (A). The two categories are defined by different tests and do different work.
Does adding a nontraditional participant slow the award down?
The diligence is real but small: status confirmation, a scope statement, a share of the work breakdown, and intellectual property terms. Set against a written determination at $100 million or a one-third cost share, it is the least expensive of the available paths. The schedule risk sits in funding, sponsorship, and security access, not in the teaming step.
Bottom line
The prototype other transaction is not a lighter version of a FAR contract. It is an instrument whose availability is conditioned on the composition of the team, and the condition falls hardest on exactly the companies most able to prime. A prime evaluating this pathway is really answering three questions in order. Does our business unit still hold nontraditional status, or has scale closed that door. If it has closed, which condition is the project going through, and does the person who will sign the determination agree. And is the participant we are naming someone we would want on the program when the prototype becomes production, because § 4022(f) hands the non-competitive follow-on to the same roster.
Get those right and the teaming work is a small front-loaded cost that buys an instrument with negotiated terms and a production pathway. Get them wrong and the defect sits inside the agreement, unexamined, until a determination has to be written about it.
Frequently asked questions
Because the definition of a nontraditional defense contractor at 10 U.S.C. § 3014 turns on full Cost Accounting Standards coverage, and under 48 CFR 9903.201-2 full 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 in its preceding cost accounting period. Companies at prime scale have generally crossed that line, which closes the status to them.
Yes. Section 4022(d)(1) has no dollar floor. The written determinations at § 4022(a)(2) begin above $100 million, but the underlying condition applies to every prototype other transaction regardless of value.
The statute does not define the phrase. Subsection (e) defines six other terms and not this one, so the judgment sits with the officials applying the condition. The practical standard a prime should aim for is a participant whose scope can be stated in one sentence, whose share is visible in the work breakdown and the price, and whose removal would change the technical result.
It does. DFARS 212.102(a)(iv) allows contracting officers to treat supplies and services from nontraditional defense contractors as commercial products or commercial services without a commercial determination, and requires commercial treatment of services from such a business unit when they use the same employee pool as commercial customers and are priced using a similar methodology, with the file documented either way.
Under § 4022(f)(2), a follow-on production contract or transaction may be awarded to the participants without competitive procedures if competitive procedures were used to select the parties for participation and the participants successfully completed the prototype project. The prototype transaction has to have provided for the follow-on, so both the provision and a measurable definition of completion belong in the agreement.