How Federal Defense Acquisition Works

“Defense acquisition” is the government’s term for how the Pentagon buys things — from rifles and radios to fighter jets, submarines, and satellites. It is one of the largest and most scrutinized purchasing operations in the world, and it is governed by a dense body of statute, regulation, and policy. But the underlying logic is straightforward: acquisition is the process of turning a validated military need into a capability that is designed, tested, produced, fielded, and then kept running for decades. This explainer walks that process from end to end and then turns to why it has become a central target of reform.

It starts with a requirement

Acquisition does not begin with a product; it begins with a requirement — a formally validated statement of a military need. The armed services identify capability gaps, and a requirements process reviews and validates them so that the department is buying against an agreed need rather than a wish list. At the joint level, the Joint Requirements Oversight Council (JROC) validates the most significant requirements. Getting the requirement right is decisive: a vague, unstable, or overreaching requirement is one of the most reliable predictors of a program that later runs over cost and behind schedule.

Choosing a pathway: the Adaptive Acquisition Framework

There is no longer a single acquisition process. Under the Adaptive Acquisition Framework, established by DoD Instruction 5000.02, a program is directed down one of six pathways chosen to fit what is being bought and how fast it is needed:

• Urgent Capability Acquisition — for urgent operational needs, fielded in months, not years.
• Middle Tier of Acquisition (MTA) — rapid prototyping and rapid fielding, typically within about five years, without the full major-program process.
• Major Capability Acquisition — the traditional, milestone-based path for large, complex systems like ships and aircraft.
• Software Acquisition — a modern path built around continuous, iterative software delivery.
• Defense Business Systems — for the department’s business and IT systems.
• Acquisition of Services — for the enormous volume of contracted services the department buys.

The framework exists because a one-size process badly served both ends of the spectrum: it was too slow for software and urgent needs, and it applied heavy overhead to small buys. Matching the pathway to the product is one of the most consequential early decisions in any program.

Contracting and procurement

Once a program has a requirement and a pathway, it has to be put on contract. Federal contracting runs on the Federal Acquisition Regulation and its defense supplement, and it turns on a few core choices: whether to compete the work (competition is the default, and full and open competition is generally required); what contract type to use (fixed-price contracts put cost risk on the contractor; cost-reimbursement contracts suit work whose scope is uncertain); and how to structure incentives. These choices determine who bears the risk when a program costs more or takes longer than planned.

Testing, production, fielding, and sustainment

A major system then moves through a sequence that, in the traditional pathway, is punctuated by milestone decisions — formal go/no-go reviews by a designated milestone decision authority before a program advances:

• Development and testing — the system is designed and put through developmental and then operational test and evaluation to confirm it works and is suitable and effective before large-scale commitment.
• Production — the department commits to building the system, often starting at low rate before ramping to full-rate production once testing and reliability support it.
• Fielding — the capability is delivered to operational units and declared ready for use.
• Sustainment — the longest and often costliest phase, covering maintenance, spare parts, upgrades, and support across a system’s service life, which for major platforms can run decades.

Congressional oversight

Because acquisition spends public money at enormous scale, Congress oversees it closely, using several standing mechanisms:

Why acquisition reform is a live debate

The reason acquisition is such an active policy fight is that its timelines have grown long enough to matter strategically. In its July 2026 Weapon Systems Annual Assessment (GAO-26-108457), the GAO found that the average time to deliver a new capability had increased to over 12 years — and that programs continue to enter rapid-acquisition pathways with immature technologies, a pattern GAO ties directly to later cost and schedule problems. When capabilities take more than a decade to field, the technology can be dated before it arrives, and adversaries can move faster than the process that is supposed to counter them.

That concern has driven reform from both ends of Pennsylvania Avenue. In April 2025, the executive branch issued Executive Order 14265, directing the Defense Department to modernize acquisition and lean harder on commercial and nontraditional approaches. Congress, meanwhile, made acquisition reform a marquee element of the FY2026 NDAA.

What actually became law — a precise reading

Here it is worth being careful, because the reform debate is easy to describe inaccurately. The House’s FY2026 defense bill was branded the SPEED Act (Streamlining Procurement for Effective Execution and Delivery Act, H.R. 3838), and the Senate advanced its own reform vehicle. But the law that was actually enacted is the National Defense Authorization Act for Fiscal Year 2026 — Public Law 119-60 — and not every proposal from the House SPEED Act survived into it. The SPEED Act is best understood as a set of proposals, some of which became law and some of which did not.

The enacted FY2026 NDAA carried a dedicated acquisition-reform title (Title XVIII), together with streamlining provisions in Title VIII. Among the provisions that did become law: a rewrite of the statutory objectives of the defense acquisition system (Section 1801); the establishment of a portfolio acquisition executive role (Section 1802); adjustments to certain acquisition dollar thresholds (Section 1804); and streamlining and competition measures in Title VIII. Crucially — and this is where secondhand summaries often go wrong — the enacted law modified the Joint Requirements Oversight Council rather than abolishing or replacing it. The JROC continues to exist in law; what changed were its procedures and consultation requirements, not its existence.