This bill amends Title 10 to tighten how the Department of Defense reports and responds to cost growth on major acquisition programs. It shortens the timeline for Nunn‑McCurdy breach notifications, requires public posting of cost‑growth certification reports, expands what counts in life‑cycle cost estimates, and creates a strict prohibition on certifying programs that suffer a second critical cost breach, triggering mandatory termination timelines.
For program managers, contractors, and congressional staff, the changes mean earlier reporting windows, more granular reporting obligations where programs deliver multiple high‑cost end items, and a materially higher risk that persistent cost growth will lead to program termination rather than further waivers. The practical effects will touch budgeting, pricing, program schedules, and procurement risk strategies across major systems acquisition portfolios.
At a Glance
What It Does
The bill shortens statutory notification deadlines for Nunn‑McCurdy breaches to 30 days and requires DoD to publish written cost‑growth certification reports online. It designates end items that each exceed $500 million as major subprograms and explicitly includes operations and support (O&S) costs in life‑cycle cost calculations. It also prevents the Secretary from certifying a program that has experienced a second reassessment for cost growth and requires termination within a set period.
Who It Affects
Affected parties include DoD acquisition program offices, prime contractors and suppliers on programs with multiple high‑cost end items, congressional defense committees, and agency budget offices that must account for expanded lifecycle costs. Program financial analysts and compliance teams will also see increased reporting and disclosure obligations.
Why It Matters
By accelerating reporting and broadening what counts as program cost, the bill raises the visibility and near‑term consequences of cost growth. That changes tradeoffs between absorbing overruns, restructuring programs, or terminating them — with downstream impacts on industrial base planning, contract strategy, and Congressional oversight practices.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
Section 1 tightens the timing for Nunn‑McCurdy breach actions. Where current statute begins with the phrase “When a unit cost report,” the bill replaces that open‑ended trigger with clear deadlines: program offices and the Secretary must act within 30 days of a unit cost report or a determination based on required quarterly reports.
Practically, this compresses the time between identification of a critical breach and formal notification to Congress and other statutorily required steps.
Section 2 introduces a new way to break down big programs: if a major defense acquisition program will deliver two or more distinct end items and each end item is projected to require more than $500 million in research, development, test, evaluation, operation and support over its life, the Secretary must treat each end item as a separate “major subprogram” for acquisition reporting. That creates additional reporting lines and thresholds inside a single program of record where multiple expensive end items exist.Section 3 amends the statutory cost baseline by making explicit that operations and support costs are part of the life‑cycle cost for both major defense acquisition programs and any newly designated major subprograms.
In short, the denominator used to judge cost growth must include long‑term O&S estimates, not just procurement and development costs.Section 4 tightens the consequences for repeated critical cost growth. The bill (a) requires the Secretary to post each written certification required by statute on a DoD website; (b) prevents the Secretary from submitting the statutory certification for any program that has already undergone more than one reassessment due to unit or procurement cost growth (i.e., a “second critical breach”); (c) requires mandatory termination of such a program within 90 days after the reassessment that triggered the second breach; (d) bars delegation of the statutory certification to subordinates; and (e) mandates that termination planning explicitly consider options that maximize value to the government (immediate termination, finishing already funded end items, resale‑value economics, or other value‑maximizing actions).
These changes move the regime from one of repeated waivers toward hard stop options where persistent cost growth occurs.
The Five Things You Need to Know
The bill replaces the open‑ended "When a unit cost report" trigger in 10 U.S.C. §4374 with explicit 30‑day deadlines for reporting and congressional notification following unit cost reports or determinations based on quarterly reporting.
It requires the Secretary to designate as separate "major subprograms" any end items within a major defense acquisition program when two or more end items each have projected life‑cycle expenditures exceeding $500 million.
The statutory life‑cycle cost baseline is expanded to require inclusion of operations and support (O&S) costs for both major defense acquisition programs and designated major subprograms.
The bill bars the Secretary from certifying a program that has experienced more than one unit or procurement cost increase resulting in reassessment (a second critical breach), requires termination of such programs within 90 days of the reassessment, and prohibits delegating the certification submission.
DoD must make each written cost‑growth certification publicly available on a Department website and, for terminated programs, prepare termination plans that explicitly evaluate options to maximize value (immediate termination, completion of funded end items, resale value, or other value‑maximizing alternatives).
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Shortened Nunn‑McCurdy notification deadlines
This amendment replaces the statute’s prior timing language with firm 30‑day deadlines for the actions triggered by unit cost reports and related determinations. Two distinct subsections are changed—one governing the initial breach handling and another governing subsequent determinations—so both program offices and the Secretary face the same compressed window. For program offices, that means faster internal decision cycles and accelerated coordination with legal, budget, and Congressional Affairs teams; for Congress it means earlier visibility into cost problems.
Major subprogram designation for high‑cost end items
The Secretary must label each end item as a major subprogram when a program will deliver multiple end items and each end item’s eventual life‑cycle cost (RDT&E, test, evaluation, operation, and support) is estimated above $500 million. That shifts reporting and oversight from a single program‑level view to a more granular structure, increasing the number of reportable acquisition units inside a program of record and changing how thresholds and breaches are calculated.
Explicit inclusion of O&S in life‑cycle cost
The change clarifies that the life‑cycle cost metric used across acquisition reporting must include operations and support for the entire life of a program or designated subprogram. This raises the nominal cost baseline against which growth is measured and can push programs closer to statutory breach thresholds even if procurement and development costs remain stable. Budget analysts and cost estimators will need to incorporate longer‑term O&S models into acquisition baseline reporting.
Public posting, no second‑breach certification, mandatory termination, and non‑delegable certification
This section makes several interlocking changes: it requires DoD to post written cost‑growth certification reports online; it prevents the Secretary from issuing a statutory certification for any program that has had more than one cost increase leading to reassessment; it compels termination of such programs within 90 days after the reassessment; and it disallows delegation of the certification. The provision also expands what termination planning must consider, listing immediate termination, finishing already funded end items, resale economics, and other value‑maximizing approaches. Together, these mechanics tighten central control (by reserving certification to the Secretary) while forcing timely public disclosure and concrete termination planning.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Congressional oversight committees — get faster notifications, public certification documents, and clearer decision points when programs exceed cost thresholds, improving their ability to hold DoD accountable.
- Taxpayers and the public — gain transparency through mandated online publication of certification reports and clearer statutory gates that can prevent repeated cost escalation without consequence.
- Program cost analysts and auditors — receive a clearer lifecycle accounting rule (including O&S) and more granular subprogram delineation that can improve traceability of where costs accrue within multi‑end‑item programs.
Who Bears the Cost
- DoD acquisition program offices and Service acquisition executives — face compressed 30‑day timelines for internal analysis and external notification, plus stricter preservation of the Secretary’s signature authority.
- Prime contractors and suppliers on multi‑end‑item programs — encounter increased reporting scrutiny, the risk of program termination after a second breach, and elevated commercial sensitivity from public disclosures.
- Budget and finance offices — must integrate longer‑range O&S cost estimates into acquisition baselines, which can complicate budget scoring and obligational planning and may shift how programs are funded or structured.
Key Issues
The Core Tension
The bill forces a choice between faster, more transparent oversight and the risk of premature program disruption: accelerate reporting and widen the cost base to catch overruns earlier — at the price of heavier administrative burdens, potential manipulation of cost models, and a harsher termination regime that may interrupt programs with strategic or industrial‑base implications.
The bill tightens procedural deadlines and broadens cost bases, but it leaves several implementation choices unresolved. For example, including O&S in life‑cycle costs is conceptually straightforward, but practice requires agreement on cost‑modeling standards, escalation assumptions, and how to treat classified or contingency‑driven sustainment costs.
Without detailed guidance, Services could produce inconsistent O&S estimates, moving breach determinations from being a technical exercise to a dispute over modeling assumptions. Similarly, designating high‑cost end items as major subprograms will increase reporting lines—useful for granularity but administratively heavier—and the statute does not specify whether existing baselines must be recalculated at the time of designation.
The forced‑termination mechanics pose tradeoffs. Requiring termination after a second critical breach can prevent endless waivers, but it also creates incentives to avoid or manipulate reassessment triggers, reclassify costs off the program, or delay reporting to stay beneath statutory gates.
The bar on delegating certification centralizes accountability at the Secretary level, improving political visibility but risking politicization of technical certification decisions. Public posting of certification reports advances transparency but may disclose competitive or sensitive program details unless the Department pairs the requirement with classification or redaction standards.
Finally, the statute references a 60‑day period in existing law for certain terminations and inserts a 90‑day timeline for second‑breach terminations; reconciling these windows across program types and for programs carrying over obligated funds will require careful rulemaking and interagency coordination.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.