What readiness means when the rulebook is absent
Readiness for a Federal Acquisition Regulation contract means being able to comply with terms someone else already wrote. Readiness for an other transaction means being able to answer questions no one has answered for you, inside the two to eight weeks between a selection notice and a signature, while a program office watches how long each answer takes. The FAR governs procurement contracts. An other transaction is not one, so the clause set that would have supplied definitions, data rights, payment financing, audit rights, and a disputes procedure is simply not in the document. Everything it would have given you is now something you bring or something you lose.
The volume behind this is no longer marginal. The Department's annual report to Congress recorded 7,409 other transaction actions and $18.03 billion obligated in fiscal 2024, against 1,702 actions and $7.38 billion in fiscal 2019. Executive Order 14265, Modernizing Defense Acquisitions and Spurring Innovation in the Defense Industrial Base, signed April 9, 2025, directs the department toward "a first preference for commercial solutions and a general preference for Other Transactions Authority." More first agreements are being negotiated every quarter, and most of the companies negotiating them have never done it before.
The list below is ordered by what actually delays a first agreement, not by what is most interesting to read about. Almost none of it is difficult. All of it takes calendar time, and all of it gets checked at the worst possible moment.
Gate zero: confirm that you open the door
A prototype other transaction is available to the department only when one of four conditions in 10 U.S.C. § 4022(d)(1) is satisfied. At least one nontraditional defense contractor or nonprofit research institution participates to a significant extent. Or all significant non-federal participants are small businesses or nontraditional defense contractors. Or at least one third of the total project cost is paid from non-federal sources. Or the agency's senior procurement executive determines in writing that exceptional circumstances justify the instrument.
For a first-time company the realistic answer is one of the first two, and both turn on the same definition. Under 10 U.S.C. § 3014, a nontraditional defense contractor is an entity not currently performing, and not having 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. That is the whole test. No size element, no revenue band, no application, no certificate.
Work the accounting rules backward and the answer usually arrives quickly. Small businesses are exempt from the Cost Accounting Standards outright under the exemptions at 48 CFR 9903.201-1(b), so a firm that is small under the applicable size standard cannot be under full coverage and is nontraditional as a matter of arithmetic. Above that, full coverage under 48 CFR 9903.201-2 attaches at a single covered award of $50 million or more, or $50 million or more in net covered awards during the preceding cost accounting period. The direction of travel is toward easier qualification: section 1806 of the FY2026 National Defense Authorization Act, Public Law 119-60, signed December 18, 2025, raises the full-coverage threshold to $100 million, and the Cost Accounting Standards Board published a proposed rule to implement the change on March 20, 2026.
The third condition, cost share, is a door rather than a toll, and it is the one most often misread. It requires one third of the total project cost from non-federal sources, which works out to half of the government's number rather than a third of it. Satisfy any of the other three conditions and it never comes up.
The readiness action is a single page. Write the eligibility position before anyone asks for it: entity name, CAGE code, a plain statement that the business unit is not performing and has not performed within the preceding year any Department of Defense contract or subcontract subject to full Cost Accounting Standards coverage, and the basis for that statement. An agreements officer needs it in the file. A company that produces it in an hour reads differently from one that takes nine days.
The registrations that stop awards
This is the least interesting section on the page and the one that costs the most weeks. Every item is administrative, every item has a lead time, and every item is verified at award rather than at selection.
- An active SAM.gov registration set to All Awards — not Financial Assistance Awards Only — renewed before it lapses and kept active through the whole period of performance.
- A Unique Entity Identifier and a live CAGE code that match the legal entity name on every other document you will sign.
- Representations and certifications current in SAM, because they are read at the moment of award and not a month earlier.
- Payment enrollment settled before the first milestone — the Defense Innovation Unit directs invoicing through the iRAPT module of Wide Area Workflow, while a consortium project agreement often invoices through the management organization instead. Ask which one applies.
- A signed consortium membership agreement where the path runs through a consortium, plus the militarily critical technical data agreement on Form DD-2345 that many consortia require at joining.
- An employer identification number, a bank account that can receive electronic funds transfer, and current certificates of insurance in the names the agreement will use.
- One named person with authority to bind the company, and the operating agreement or corporate resolution that says so.
Consortium membership deserves one clarification, because it is the most common misunderstanding in this whole area. A membership is a commercial agreement between your company and a private organization. It is not an award, not a contract vehicle, and not a relationship with a contracting officer. It makes you eligible to be evaluated when the sponsoring command releases a call. The paperwork looks federal because the consortium collects the same identifiers the government will later verify.
Money: can the company survive its own payment schedule
Other transaction agreements are commonly written as fixed-price with payable milestones, as expenditure-based, or as a hybrid of the two. The choice decides what kind of company you have to be.
Under fixed payable milestones the government pays on a demonstrated technical event rather than on incurred cost. That is the arrangement most first-time firms want, and it is the one that quietly transfers the financing burden. There are no progress payments unless the agreement creates them, because the FAR clauses that would have supplied contract financing are not present. You pay salaries every two weeks. The government pays when a milestone is accepted and the invoice clears.
Run the arithmetic before the negotiation, not during it. Take the draft milestone schedule, lay your fully burdened monthly cost against it, add a realistic lag between milestone acceptance and cash in the account, and look at the worst month. If that month breaks payroll, the milestone schedule is wrong. It is negotiable now and much harder to move once it is an attachment to a signed agreement.
An expenditure-based agreement moves the conversation to your accounting system. The Cost Accounting Standards do not apply, and certified cost or pricing data is not required, because that requirement attaches to contracts under FAR 15.403-4 and its threshold is a contract rule. What the agreements officer will still want is evidence that costs can be accumulated by project, that labor is recorded as it is worked, and that indirect rates have a defensible basis. Records access is a negotiated term rather than an automatic one, which means the draft agreement contains a sentence describing exactly what you are letting the government examine and for how long. Read that sentence.
Two smaller items belong in the same model. A consortium management organization takes a fee, so the number you price is not the number you keep. And if the agency is relying on the cost-share condition, the required non-federal contribution is half the government's contribution, sustained through performance rather than measured once at award.
The intellectual property schedule you write before you need it
Every serious other transaction has an attachment listing what each party brought to the project. Anything not on that list is exposed to the argument that it was developed under the agreement, and that argument is far harder to win a year later than it is to prevent in week one. This is the only item on the checklist that takes engineering judgment rather than paperwork, and it is the one that cannot be produced in a hurry.
Inventory before anyone drafts anything. Every model, library, dataset, pipeline, and internal tool that predates the project, with the date it existed and the evidence that fixes the date. Repository history is better evidence than a memo written during negotiation.
Make the separation real in the build. A schedule that describes a boundary the delivered container does not have is a paper boundary. If the background model and the project-funded integration layer share a repository, share a build, and ship as one artifact, the separation exists only in the attachment.
Generate the component bill of materials from the build, not from memory. Third-party and open-source dependencies and their licenses, enumerated by the toolchain. A copyleft dependency discovered inside a delivered image after acceptance is a bad quarter for everyone in the room.
Verify that employees and contractors actually assigned their work. A background schedule listing a component your former contractor still owns is worse than no schedule, because it is a representation.
Enumerate the artifacts by name. Training corpora, labeling guidance, held-out evaluation sets, trained weights, fine-tuning adapters, prompt libraries, retrieval indexes, and production telemetry are different assets with different value. A license grant written across "software and technical data" leaves every one of them to be argued later by whoever happens to be holding the agreement.
Data handling, security, and export control
Controlled unclassified information travels with the work regardless of instrument. The government-wide program rule sits at 32 CFR Part 2002, issued under Executive Order 13556. What does not travel is the contract clause that would ordinarily impose safeguarding requirements, because that clause attaches to procurement contracts. Program offices handle the gap by writing NIST SP 800-171 style requirements straight into the agreement text.
The readiness question is therefore concrete rather than philosophical. Know where the work will run before the question arrives: which cloud, which region, which accounts, who holds access, how access is revoked when someone leaves, and whether you could produce an access log this week if asked. Price that environment into the milestone schedule if you do not already operate it. Do not describe an environment you have not stood up.
Export control follows the same logic. An agreement can sit inside International Traffic in Arms Regulations or Export Administration Regulations scope no matter what the instrument is called. If the work touches controlled technical data, the registration, the marking discipline, and the access controls are yours to have already, not yours to build during performance.
People, teammates, and signature authority
Key personnel named in a submission should be real, identified, and available on the schedule you proposed. An agreements officer reading a first agreement is calibrating how much of what the company says can be relied on, and the personnel section is the cheapest place to lose that.
Teaming carries a specific trap under this instrument. Nothing flows down automatically. On a FAR contract, mandatory clauses reach subcontractors by regulation. Under an other transaction, your teammate is bound by whatever your subaward says and nothing else, so the subaward has to be drafted alongside the head agreement rather than after it. Data rights are the usual casualty: a company grants the government rights in a delivered system, then discovers its own subcontract does not obtain those rights from the party who wrote part of it.
Eligibility can also depend on the team. If the award rests on the condition that all significant non-federal participants are small businesses or nontraditional defense contractors, then every significant teammate has to hold that status. Confirm it before you name them, not after the government builds the file around them.
The two sentences about production
The provision that makes prototype other transactions strategically interesting is 10 U.S.C. § 4022(f). A follow-on production contract or transaction may be awarded to the participants without competitive procedures where competitive procedures were used to select the parties and the participants successfully completed the prototype project. Section 817 of the FY2025 National Defense Authorization Act, Public Law 118-159, rewrote the provision, and it now permits that follow-on "even if explicit notification was not listed within the request for proposal for the transaction." Under § 4022(d)(3), the conditions that governed the prototype do not apply to the follow-on.
The condition that fails is successful completion. Oracle America, Inc., B-416061 (May 31, 2018) is the decision everyone in this area eventually reads: GAO sustained a protest of a follow-on production award in part because the prototype agreement contained no provision for one. The statute has moved since. The lesson about acceptance language has not.
So the readiness item is small and specific. Before signature, find the sentence that defines successful completion and make it measurable — a detection rate at a stated false-alarm rate, a latency budget under a stated load, an integration completed against a named system. Satisfaction language leaves the determination to whoever occupies the chair at the end of the period of performance. The department reported that 61 percent of fiscal 2024 prototype projects included an option for follow-on production, up from 56 percent the year before, which means this sentence is now in most agreements and is worth more than most of the pages around it.
What the regulation would have supplied, and who supplies it now
| Element | Under a FAR contract | Under an other transaction | What readiness looks like |
|---|---|---|---|
| Technical data and software rights | DFARS 252.227-7013 and -7014 set defaults according to who funded development | No clause attaches; the agreement is the entire allocation | A background schedule and a per-artifact license table drafted before the first draft arrives |
| Patent rights | Bayh-Dole operates through funding agreements: contracts, grants, cooperative agreements | An other transaction is none of the three, so nothing attaches by itself | A patent article you have read, granting a government license and leaving title where you expect it |
| Cost principles and audit | FAR Part 31 cost principles, CAS above the thresholds, DCAA on cost-type work | None by default; records access is a negotiated term | Books that accumulate cost by project, and a clear read of the access you agreed to give |
| Payment financing | Progress payments and other financing available by regulation | Whatever the agreement says, commonly fixed payable milestones | A cash model run against the actual milestone dates rather than the period of performance |
| Safeguarding controlled information | Imposed by clause, with a defined standard | Written in by hand where the program office wants it | A named environment, named accounts, and an access story you can produce on request |
| Disputes | Contract Disputes Act, a final decision, then a board or the court | Whatever procedure the agreement creates | Reading the disputes article before signature rather than during a disagreement |
| Flow-down to teammates | Mandatory clauses reach subcontractors by regulation | Nothing flows down on its own | Subawards drafted alongside the head agreement, carrying the terms you accepted |
Where first agreements actually stall
The weights below are our reading of how often each item is the thing standing between a selection and a signature. They come from the statute, the department's published guidance, and the shape of the negotiation itself, and they express relative emphasis rather than measurement. Read them as an order of work: fix the top rows first, because the bottom rows can be settled in an afternoon once someone is assigned to them.
Weight we place on each readiness item
Editorial weighting from public statute, department guidance, and practitioner reading. Relative emphasis, not measurement.
A thirty-day readiness sprint
None of this needs a program to be in hand. A company that works the list cold arrives at its first competition able to move at the speed the instrument was designed for, which is the only speed advantage that is genuinely available to a new entrant.
Working the list before a competition exists
Being ready does not make anyone want the prototype
A complete package shortens the distance between a selection and a signature and keeps an administrative problem from killing a technical win. It does not create demand. A sponsor with money, a requirement someone owns, and a technical case that answers it still decide the outcome, and no amount of paperwork discipline substitutes for any of the three. What readiness buys is that nothing on this page is the reason you lose.
Common objections, answered plainly
Isn't the whole point of an OTA that there is less paperwork?
There is less standard paperwork and more original paperwork. The FAR clause set is gone, which removes hundreds of pages of terms nobody negotiates. What replaces it is a shorter document in which every operative sentence was written for this deal and can be argued about. Less volume, higher stakes per page.
Can a company with no federal history receive one?
Yes, and the authority was built partly for that case. The Defense Innovation Unit states that any individual or commercial entity is eligible to respond to its solicitations regardless of prior government contracting experience. The department reported that 93 percent of fiscal 2024 obligations went to awards with significant participation by a nontraditional defense contractor.
Should we hire a consultant to negotiate the agreement?
Outside help is worth most where the terms are technical rather than legal: which artifacts exist, which predate the project, what the delivered system actually contains. A firm that arrives with a defensible inventory needs far less help than one that arrives with a blank schedule and a deadline.
Does readiness expire?
Parts of it do. SAM registration lapses annually. Representations go stale. The background schedule drifts every time the codebase changes, which is why the useful version is generated from the build rather than maintained by hand. Treat it as a standing artifact with an owner, not a one-time exercise.
Bottom line
The instrument is fast because the government skipped the regulation, not because it skipped the diligence. Everything the FAR would have decided in advance now gets decided in a compressed window, and the company that has already answered those questions negotiates from a different position than the one answering them for the first time under schedule pressure.
Three items carry most of the weight: an eligibility position you can state in a paragraph, a background intellectual property schedule that matches what the build actually contains, and a milestone schedule your bank account can survive. The rest is administration with a lead time. Work the administration cold, before a competition exists, and the only thing left to win on is the technical case, which is where it should have been all along.
Frequently asked questions
No. The statutory conditions at 10 U.S.C. § 4022(d)(1) name nontraditional defense contractors, and small business status is one route to that label rather than the label itself. Small businesses are exempt from the Cost Accounting Standards outright, so they cannot be under full coverage and therefore qualify as nontraditional. Larger firms qualify too, as long as they are not performing Department of Defense work under full Cost Accounting Standards coverage.
Only when the agency relies on that specific condition. It is one of four alternatives, and satisfying any other one removes it entirely. Where it does apply, the requirement is one third of total project cost from non-federal sources, which is half the government's contribution rather than a third of it, and the department expects the ratio to hold through performance rather than only at award.
Not by rule. A fixed-milestone agreement can run on ordinary commercial books, since the Cost Accounting Standards and the certified cost or pricing data requirement both attach to contracts rather than to other transactions. An expenditure-based agreement puts the accounting system into the negotiation, and any follow-on FAR work puts it permanently in scope. Firms that skip the build discover the gap at the least convenient moment.
The Defense Innovation Unit describes awarding prototype agreements in as few as 60 to 90 days from solicitation, with the negotiation portion commonly running 30 to 60 days. Consortium project agreements vary more widely. Which end of the range you land on depends mostly on how quickly the company answers questions about intellectual property, cost basis, and data handling.
The background intellectual property schedule. Registrations can be repaired in days and a milestone schedule can be renegotiated, but an inventory of what your company already owns, dated and evidenced and matching what the build actually ships, takes engineering time nobody has during a negotiation. It is also the document that decides what you still own at the end.