DoDD 5000.01: Defense Acquisition System Policy and Pathways

DoD Directive 5000.01 is the Department of Defense’s top-level policy on how the military acquires weapons, equipment, software, and services. It was issued under Section 113 of Title 10 of the U.S. Code, took effect on September 9, 2020, and was updated by a change incorporated on July 28, 2022.¹ The directive binds every organizational entity within DoD, including the military branches, the Office of the Secretary of Defense, the Joint Staff, Combatant Commands, Defense Agencies, and DoD Field Activities. It sets the overarching policies and assigns responsibilities. The procedural detail lives in a family of subordinate instructions, the DoDI 5000-series.

Core Policy Principles Every Program Must Follow

The directive frames acquisition around a few principles that apply to every program, regardless of size or type.

The first is delivering performance “at the speed of relevance.” The acquisition system exists to put capable, tested equipment into warfighters’ hands with measurable and timely improvements to mission capability.¹ Speed is a policy objective, not a preference.

Affordability is treated as a design constraint. Programs must achieve their performance goals at an affordable life-cycle cost, meaning officials weigh expenses from early design through sustainment and disposal.¹

Security has to be built in from the start. The directive treats cybersecurity as a fundamental element of system design rather than something added on later, and the obligation carries through the whole life cycle.¹

Innovation and competition round out the core principles. The directive encourages adopting commercial technology when it offers an advantage, and full and open competition is required in most procurement actions.²

Who Decides What: The Acquisition Authority Chain

DoDD 5000.01 assigns responsibilities at three main levels.

At the top is the Under Secretary of Defense for Acquisition and Sustainment (USD(A&S)), the principal advisor to the Secretary of Defense on acquisition matters. This office sets department-wide policy, oversees research and development, manages the acquisition workforce, and coordinates international acquisition cooperation.¹

Each program has a designated Milestone Decision Authority (MDA). The MDA approves a program’s progression from one development phase to the next: from technology maturation into engineering, from engineering into production, and so on. The directive’s policy favors delegating authority to the lowest competent level, so an MDA for a smaller program may be a service acquisition executive or a program executive officer within a military branch.

The Program Manager (PM) runs day-to-day execution, owning cost, schedule, and performance for a specific system. Because authority is pushed downward, PMs have real decision-making power, and they also own the results.

Independent Cost Estimates

Federal law forces an independent check on program cost. The Director of Cost Assessment and Program Evaluation must conduct or approve an independent cost estimate before several key events: any milestone approval, any decision to enter low-rate initial production or full-rate production, certain statutory certifications, and any military construction contract exceeding $500 million.³

Nunn-McCurdy Cost Growth Reporting

When a program’s unit cost grows past defined thresholds, the Nunn-McCurdy provisions apply. The service acquisition executive compares current cost estimates against the program’s baseline, and if costs have breached the significant or critical growth threshold, the Secretary of the relevant military department must notify Congress in writing.⁴

A critical breach triggers a more demanding process. The program must be certified as essential to national security, the cost estimates must be independently validated as reasonable, and there must be a finding that no less expensive alternative can provide acceptable capability.⁵ Without that certification, the program faces termination.

The Adaptive Acquisition Framework and Its Six Pathways

One of the directive’s most consequential moves was replacing a one-size-fits-all acquisition model with the Adaptive Acquisition Framework (AAF). The AAF gives decision authorities and program managers latitude to plan and manage programs by selecting from six pathways, each designed for a different type of acquisition.⁶

Urgent Capability Acquisition

This pathway applies when warfighters need a capability fielded in less than two years, typically in response to a validated urgent operational need or a critical warfighter issue. Programs face dollar caps: as originally set, no more than $525 million in development funding or roughly $3 billion in procurement funding (in fiscal year 2020 constant dollars). Solutions acquired this way must later transition to a longer-term program or be divested.⁷

Middle Tier of Acquisition

The Middle Tier targets capabilities that need to move faster than traditional acquisition allows but do not qualify as urgent. It offers two tracks. Rapid prototyping aims to field a prototype meeting defined requirements and providing residual operational capability within five years of the program start date. Rapid fielding requires production to begin within six months and complete fielding within five years.⁸ Neither track may be planned to exceed the five-year limit, and going beyond it in execution requires a waiver from the Defense Acquisition Executive.

Major Capability Acquisition

This is the structured, milestone-driven pathway for large, complex weapons systems: aircraft carriers, fighter aircraft, missile defense networks. Programs move through technology maturation, engineering and manufacturing development, production and deployment, and operations and sustainment, with formal milestone reviews gating each transition. Milestone B, which authorizes entry into engineering and manufacturing development, requires certifications covering technology readiness, affordability, schedule realism, and sustainment planning.⁹

Software Acquisition

The Software pathway recognizes that software runs on different timelines and methods than hardware. Programs must use modern iterative development approaches such as Agile or Lean, employ DevSecOps pipelines, and use automated tools for development, integration, testing, and certification to iteratively deploy software to operational environments.¹⁰ The goal is continuous delivery rather than a single monolithic release.

Defense Business Systems

This pathway covers internal business systems that keep the department running: financial management, human resources, logistics, contracting, and similar functions. It follows the Business Capability Acquisition Cycle, which divides work into five phases from capability need identification through capability support.¹¹ The pathway can also cover non-developmental, software-intensive programs that fall outside the business systems category.

Acquisition of Services

The sixth pathway applies to contracted services with a total estimated value at or above the simplified acquisition threshold. It follows a seven-step process organized into planning, development, and execution phases, running from team formation and market research through requirements definition, strategy execution, and performance management.¹²

Operational Testing Before Full Production

Federal law bars major defense acquisition programs from moving beyond low-rate initial production until initial operational test and evaluation is complete. The Director of Operational Test and Evaluation, the principal advisor to the Secretary of Defense on testing matters, must approve the adequacy of the test plans in writing before operational testing begins.¹³ After testing, the Director issues a report stating whether the testing was adequate and whether the items are effective and suitable for combat. No final decision to proceed to full-rate production may be made until Congress receives that report.

Life Cycle Sustainment Planning

Sustainment planning starts at the beginning of a program, not after production is underway. Every covered system must be supported by a Life Cycle Sustainment Plan approved by the Service Acquisition Executive. The plan covers product support strategy, life-cycle cost estimates, intellectual property management, training, spare parts, facilities, and the transition from production to initial fielding. The Product Support Manager develops, updates, and implements the plan across the program’s life.

Performance-based strategies are mandatory. Rather than dictating how a contractor should maintain a system, these strategies define the results to be achieved (readiness rates, response times, reliability metrics) and let the contractor determine the approach. DoDD 5000.01 requires performance-based strategies for all new procurements, upgrades, and re-procurements beyond the initial production contract.¹

Cybersecurity Through the Risk Management Framework

The directive’s build-in-security requirement is implemented through the Risk Management Framework (RMF), a seven-step process integrated into the acquisition life cycle. The steps are Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor.¹⁴ Every system has its security posture categorized based on the sensitivity of the information it processes, selects appropriate controls tailored to its risk environment, implements and tests those controls, receives an authorization to operate, and is then continuously monitored for new threats. The obligation extends to the supply chain: contractors must demonstrate their manufacturing and development processes are secure from foreign interference.

Intellectual Property and Data Rights

Rights to technical data and software are one of the more consequential and frequently misunderstood areas. The government generally owns the physical deliverables, such as documents and disks, but does not automatically own the underlying intellectual property. What rights the government receives depends primarily on who funded the development.

When the government funds development entirely, it typically receives unlimited rights to use, reproduce, modify, and distribute the data. When a contractor funds development exclusively with private money, the government receives only limited rights (for technical data) or restricted rights (for software), which constrain use to internal government purposes. A middle category, government purpose rights, applies when development is jointly funded, allowing broader government use but prohibiting commercial release for a set period.¹⁵

The directive and its implementing guidance require programs to develop an intellectual property strategy early and to connect data requirements to specific use cases.

Small Business and Domestic Content Requirements

DoD is the federal government’s largest buyer, and its acquisition policies incorporate statutory requirements to direct a share of spending to small businesses. The department sets annual prime contracting goals across several categories, including overall small business participation, HUBZone businesses, service-disabled veteran-owned small businesses, small disadvantaged businesses, and women-owned small businesses.¹⁶ For fiscal year 2025, the overall small business goal stood at approximately 23 percent of prime contracting dollars.

Domestic content requirements add another layer. Under the Buy American Act as implemented through the Federal Acquisition Regulation, manufactured end products delivered in 2026 must contain domestic components exceeding 65 percent of the total component cost. Products made wholly or predominantly of iron or steel face a stricter standard: foreign iron and steel must constitute less than 5 percent of component cost.¹⁷ The domestic content threshold is scheduled to increase further after 2028.

Ethics and Post-Government Employment

DoD personnel involved in acquisition are held to strict ethical standards and must avoid situations that could call into question their impartiality or the integrity of their programs.¹⁸ Violations can lead to criminal prosecution, civil action, or administrative discipline. Military personnel who violate punitive ethics provisions face action under the Uniform Code of Military Justice. Post-government-employment restrictions prevent former acquisition officials from immediately working for contractors they oversaw.

How DoDD 5000.01 Fits With the DoDI 5000-Series

DoDD 5000.01 is the policy roof. The procedural detail a program office needs comes from subordinate instructions:

DoDI 5000.02 covers the overall operation of the Adaptive Acquisition Framework.
DoDI 5000.80 governs the Middle Tier of Acquisition pathway.
DoDI 5000.81 covers urgent capability acquisition.
DoDI 5000.85 addresses major capability acquisition.
DoDI 5000.75 handles defense business systems.
DoDI 8510.01 implements the cybersecurity Risk Management Framework.¹⁹

Read the directive for what the department values and requires. Read the instructions for how to execute a specific program on a specific pathway.

1
Department of Defense. DoDD 5000.01 – The Defense Acquisition System
2
Acquisition.GOV. Federal Acquisition Regulation Part 6 – Competition Requirements
3
Office of the Law Revision Counsel. 10 USC 3221 – Director of Cost Assessment and Program Evaluation
4
Office of the Law Revision Counsel. 10 USC 4374 – Unit Cost Reports – Determinations by Service Acquisition Executive and Secretary Concerned of Breach of Significant and Critical Cost Growth Thresholds
5
Office of the Law Revision Counsel. 10 USC 4376 – Breach of Critical Cost Growth Threshold
6
Defense Acquisition University. Adaptive Acquisition Framework Pathways
7
Department of Defense. DoDI 5000.81 – Urgent Capability Acquisition
8
Department of Defense. DoDI 5000.80 – Operation of the Middle Tier of Acquisition
9
Office of the Law Revision Counsel. 10 USC 4252 – Major Defense Acquisition Programs – Certification Required Before Milestone B Approval
10
Defense Acquisition University. Software Acquisition
11
Defense Acquisition University. Defense Business Systems
12
Defense Acquisition University. Acquisition of Services
13
Office of the Law Revision Counsel. 10 USC 139 – Director of Operational Test and Evaluation
14
Washington Headquarters Services. DoDI 8510.01 – Risk Management Framework for DoD Systems
15
Office of the Under Secretary of Defense for Acquisition and Sustainment. Intellectual Property Guidebook for DoD Acquisition
16
Department of Defense Office of Small Business Programs. Small Business Program Goals and Performance
17
Acquisition.GOV. Subpart 25.1 – Buy American – Supplies
18
Department of Defense. DoDD 5500.07 – Ethics and Standards of Conduct
19
Defense Acquisition University. Acquisition Policies