- Targeted stakeholdersFaster notification to Congress (30-day requirement) and public posting of cost reports likely increase transparency an…
- Targeted stakeholdersRequiring designation of end items costing >$500M as major subprograms and including operations-and-support (O&S) life‑…
- TaxpayersProhibiting certification after a second critical breach and requiring relatively prompt termination decisions may redu…
To amend title 10 to shorten breach reporting timelines, increase program transparency, and improve congressional oversight of Department of Defense cost overruns with respect to the cost growth for…
Referred to the House Committee on Armed Services.
This bill amends several sections of title 10, U.S. Code, to accelerate and increase congressional visibility into cost-breach reporting for major defense acquisition programs.
It requires unit-cost breach notifications to be submitted within 30 days, designates expensive end items (each > $500 million) as major subprograms for reporting, and requires inclusion of operations-and-support costs for a program’s life cycle in acquisition reporting.
The bill tightens rules around critical cost-growth certifications by requiring public posting of certification reports, preventing certification after a second critical breach and mandating termination within 90 days for programs with a second reassessment-triggering breach, prohibits delegation of certain certification submissions, and directs the Secretary to consider termination options that maximize value from obligated funds.
Content‑wise, the bill is a plausible candidate for inclusion in DoD authorization or appropriations work because it addresses common bipartisan concerns about cost growth and transparency. However, provisions that mandate program termination on repeat breaches and change lifecycle cost treatment are likely to generate pushback from the Pentagon and defense contractors, and would probably be subject to negotiation, amendment, or dilution before becoming law. Passage is possible but not assured solely on the bill’s current terms.
Relative to its intended legislative type, this bill is a clearly drafted substantive statutory amendment that specifies concrete legal changes to acquisition reporting, timelines, and termination authorities. It integrates cleanly into title 10 with precise statutory text and deadlines and introduces several accountability measures (public posting, non‑delegation, termination timelines).
Transparency vs. operational security: liberals and centrists favor public posting and transparency; conservatives worry about sensitive disclosures.
Who stands to gain, and who may push back.
- Targeted stakeholdersShorter reporting timelines, stricter breach consequences, and non‑delegable certification could increase administrativ…
- Targeted stakeholdersPrograms terminated following a second breach—or curtailed earlier because lifecycle costs or designated subprogram cos…
- CitiesTermination or restructuring of large programs can cause disruptions across the defense industrial base and supply chai…
Why the argument around this bill splits.
Transparency vs. operational security: liberals and centrists favor public posting and transparency; conservatives worry about sensitive disclosures.
A mainstream liberal is likely to view this bill favorably as strengthening accountability, reducing waste, and increasing transparency in defense procurement.
They will see faster reporting and public posting of certification reports as tools to expose cost overruns and limit runaway spending on troubled programs.
They may be concerned about potential job losses or readiness impacts from forced terminations but will tend to support provisions that prevent repeated cost-growth failures and recover value for taxpayers.
A mainstream centrist will generally welcome greater transparency and tighter congressional oversight but will worry about rigid timelines and inflexible termination rules undermining long-term acquisition programs and readiness.
They will appreciate the fuller life-cycle cost accounting and subprogram reporting for better cost visibility, yet they will flag operational and administrative burdens and urge measured implementation.
Centrists will look for exemptions, clear definitions, and safeguards to avoid destabilizing capabilities or creating perverse incentives to hide costs or politicize program cancellations.
A mainstream conservative will be skeptical of this bill, viewing its tighter reporting, public posting, and forced-termination rules as added bureaucracy that can jeopardize operational secrecy, program stability, and military readiness.
They will object to constraints on the Secretary’s discretion (including non-delegable certification) and to automatic termination after repeated breaches, arguing these undermine the ability to complete long-term modernization programs and damage the defense industrial base.
They may also see public posting of reports and inclusion of life-cycle O&S costs as opportunities for opponents of robust defense spending to cut programs.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
Content‑wise, the bill is a plausible candidate for inclusion in DoD authorization or appropriations work because it addresses common bipartisan concerns about cost growth and transparency. However, provisions that mandate program termination on repeat breaches and change lifecycle cost treatment are likely to generate pushback from the Pentagon and defense contractors, and would probably be subject to negotiation, amendment, or dilution before becoming law. Passage is possible but not assured solely on the bill’s current terms.
- No cost estimate or formal legislative fiscal analysis is attached; the net budgetary effect (savings from cancellations vs. transition costs) is unknown and could influence legislative support.
- Reactions from the Department of Defense, service leadership, and major defense contractors — including lobbying intensity — are unknown and could materially affect committee and floor outcomes.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Transparency vs. operational security: liberals and centrists favor public posting and transparency; conservatives worry about sensitive di…
Content‑wise, the bill is a plausible candidate for inclusion in DoD authorization or appropriations work because it addresses common bipar…
Relative to its intended legislative type, this bill is a clearly drafted substantive statutory amendment that specifies concrete legal changes to acquisition reporting, timelines, and termination authorities. It integr…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.