The National Defense Authorization Act (NDAA) sets policy, establishes or modifies authorities, and authorizes appropriations for the Department of War. It does not provide the money. Acquisition provisions (most often in Title VIII) travel a defined path from committee mark to law and then to usable authority inside the Department. Understanding that path tells you when a provision is real and when it is still only direction.
The process starts with the President’s budget request, typically submitted in early February, often accompanied by Administration legislative proposals. The House Armed Services Committee (HASC) and Senate Armed Services Committee (SASC) hold posture hearings, then develop and mark their bills. Subcommittee marks focus on their jurisdictions; the full committee chairs’ marks address cross-cutting acquisition, industrial base, and organizational issues. Members offer amendments, and the committees report bills that become the vehicles for floor action.
Floor consideration follows. The House usually operates under a structured rule. The Senate requires unanimous consent or cloture. Hundreds of amendments are often considered. Once both chambers pass versions, a conference committee (drawn primarily from HASC and SASC) resolves differences and produces a conference report accompanied by a Joint Explanatory Statement. That statement is the practical record of what the committees agreed and often clarifies how a provision is intended to operate. Both chambers must approve the conference report. The President then signs the enrolled bill.
Enactment is the start of implementation, not the end. Many high-impact acquisition sections require the Department to issue policy, update the Defense Federal Acquisition Regulation Supplement (DFARS), train the workforce, or restructure organizations. The FY26 NDAA, for example, codified Portfolio Acquisition Executives and directed commercial-first practices; subsequent NDAAs have withheld funding until guidance and DFARS changes appear. Historical pattern is clear: even widely supported provisions often take multiple cycles to move from statute into routine practice. DoW implementation speed varies by Service, by topic, and by whether the provision aligns with existing executive direction.
Defense Tech and Acquisition tracks this path each year from SASC and HASC marks through conference, focusing on the provisions that change authority, incentives, or execution for acquisition professionals and industry. The full year-by-year analysis is available to paid subscribers.
Practical Implications
For PAEs and program managers: Watch the Joint Explanatory Statement as closely as the statutory text. It often signals how committees expect the authority to be used. Build implementation plans that include the policy and DFARS steps, not only the legal citation. Many provisions remain underused until those steps are complete.
For industry: A provision that expands commercial procedures, OT authority, or data rights does not change contracting behavior until the Department issues implementing guidance and contracting officers are trained. Track the lag between enactment and usable policy. Engage early on the marks that matter to your pathway.
For congressional staff: Implementation is the real test of a provision. Reports, briefings, and funding withholds in subsequent NDAAs are the tools that close the gap between statute and practice. The most durable sections are those that change who decides and what they are measured against.
This is the durable path. Current-year marks, conference outcomes, and specific implementation status appear in Defense Tech and Acquisition’s annual NDAA analysis.