A defense tender is the formal competition through which a government turns a stated capability need into a signed contract, and in the American system it moves through six distinct gates: requirement, budget, solicitation, proposal, source selection and award. Each gate can kill the program. The protest numbers alone say how contested the last gates are — contractors filed more than 1,600 bid protests with the Government Accountability Office in fiscal year 2023, per GAO's annual report to Congress, and many of those protests targeted exactly the selection decisions described in the final sections of this piece.
What follows is the full pipeline as it works in the United States, which is the best-documented case in open sources and the template many allies adapt. Other countries run different statutes, but the sequence — a need, money, a published solicitation, competing offers, a documented choice, a signed instrument — shows up almost everywhere, which is why reading a single American tender teaches you most of what a tender is.
Where does the requirement come from?
Before any solicitation exists, the military has to state what it cannot do. In the United States that statement goes through the Joint Capabilities Integration and Development System, run by the Joint Staff, which forces a sponsor to document a capability gap, weigh non-material fixes like doctrine and training, and only then recommend a material solution. The output is an initial capabilities document, and it deliberately says nothing about which company or which product should win.
This is the gate where programs most often die quietly. A gap that cannot be documented compellingly never gets a budget line, and a requirement written too narrowly — naming a solution instead of a capability — invites scrutiny precisely because it steers the competition. The Defense Department's own instruction on the system emphasizes that requirements documents must describe the problem, not the purchase. Enthusiast discussion tends to start at the airframe; the paperwork starts a decade earlier, with a paragraph about what the force could not do on its last major exercise.
How does money enter the picture?
A requirement with no budget line is a wish. Money enters through the Planning, Programming, Budgeting and Execution process, in which the services build program objective memoranda covering five future fiscal years, the Office of the Secretary of Defense reviews and challenges them, and Congress ultimately appropriates funds — frequently changing the request along the way. The key documents for an outside observer are the RDT&E and procurement justification books, published on service budget sites, which state quantities, unit cost estimates and the acquisition strategy in publicly readable detail.
Two consequences of this gate matter for everything downstream. First, the funding profile shapes the contract type: stable multiyear money makes fixed-price or multiyear contracts thinkable, while year-to-year appropriations push programs toward annual competition. Second, the budget documents are the first public record of unit cost expectations, which is why cost analysts read justification books the way radar operators read raw returns — before the program office has packaged the story.
What does the solicitation actually ask for?
The solicitation is the tender proper: the government's published statement of what it wants to buy and on what terms. For major weapons this is a Request for Proposals issued under the Federal Acquisition Regulation and its Defense supplement, and it contains the specification, the evaluation criteria, the contract type the government intends to use, and the instructions and format for proposals. Everything a bidder later complains about traces back to this document, which is why the language is negotiated internally for months.
The acquisition strategy sits behind the RFP and decides the competition's shape: full and open competition, a set-aside, a follow-on to an incumbent, or a Commercial Solutions Opening or Other Transaction Authority vehicle that deliberately steps outside the FAR — a route the department has used heavily for space and software. Section 804 middle-tier acquisition authorities add further fast-track lanes with reduced statutory overhead. A reader who wants to forecast who can realistically bid should find the strategy first; the RFP merely operationalizes it.
Related stories: Why export licenses, not signed contracts, decide when weapons actually ship · What a letter of acceptance actually locks in when a weapons deal is signed.
What goes into a proposal?
On the other side, the bidders assemble proposals that typically run to thousands of pages in three volumes: technical, past performance and price. The technical volume answers the specification; the past performance volume argues that the offeror has delivered comparable work; the price volume quotes not just a total but a cost breakdown — labor categories, rates, materials, escalation assumptions — that the government's cost evaluators will interrogate line by line, including through audited field pricing when the sums are large.
The quiet mechanism here is the cost estimate cross-check. The government builds an independent estimate of what the work should cost, and a bid far below that estimate is treated as a risk, not a gift: evaluators must document why they believe the offeror can execute at the offered price, because an unrealistically low bid that collapses in execution becomes a renegotiation or a loss the contractor must absorb. The result, visible in many post-mortems of troubled programs, is that the cheapest compliant proposal and the winning proposal are often not the same document.
How is the winner actually chosen?
Source selection follows the published criteria, and only those criteria. A team of evaluators scores technical merit and past performance, a cost or price analysis runs in parallel, and a source selection authority — a named official whose rank scales with the program — documents the decision in a source selection statement that, for many programs, is released with redactions after award. Most major defense competitions use a best-value tradeoff, in which the government may pay a documented premium for technical merit, rather than lowest-price technically acceptable, which many agencies moved away from after criticism in the 2010s.
This is also where the protest counts come from. A losing offeror can challenge the award at the Government Accountability Office within days, and GAO must decide within 100 days; further routes run through the Court of Federal Claims or the agency's own protest system. GAO's annual reporting has for years shown sustain rates in the low double digits, but the protest process routinely delays awards for months and frequently forces corrective action — a re-evaluation or amended solicitation — without a formal win or loss. Bid protests are not a flaw in the system so much as its self-check, paid for in schedule.
What happens after the signature?
The signed contract fixes the deal's structure but rarely its endpoint. An award letter specifies the contract type — firm fixed price, fixed-price incentive, cost plus fixed fee — the delivery schedule, and the government's oversight rights: program management reviews, earned value reporting above defined thresholds, testing gates run by an independent office, and audit access for the Defense Contract Audit Agency. Options for follow-on production years are exercised one at a time, which keeps a lever in the government's hand.
Execution is where the tender's assumptions meet the factory. Cost-reimbursable development phases absorb surprises at government expense; fixed-price production phases put them on the contractor's books, with the incentive structure that implies. Defense Department and GAO reporting on major programs have documented for decades that concurrency — testing while producing — is the recurring pattern behind cost growth, and every acquisition reform cycle since the 1990s has tried to push testing ahead of production. The tender, in other words, does not end the negotiation. It sets the rules for the next round of it.
Why does all of this take so long?
The pipeline is slow because every gate is a deliberate friction point designed to make a very expensive commitment survivable. A documented requirement prevents the military from buying enthusiasms; a budget process prevents programs from existing without priority; a published solicitation and a written evaluation record make the choice contestable; a protest window makes the contest real. Strip out any one and the system gets faster and less defensible, which is the trade every acquisition reform debate re-litigates.
For the reader tracking a specific program, the practical takeaway is which documents to watch at each gate: the requirements validation memo, the RDT&E justification book, the SAM.gov posting of the solicitation, the award notice and its source selection statement, and the GAO protest docket. Those five artifacts, all public, reconstruct most of any tender's history without a single leak.