- Potential benefitCould create demand for additional compliance, auditing, and data‑analysis work within both industry and government (e.…
- Potential benefitIncreases transparency and oversight of price escalations on noncompetitive defense contracts, giving acquisition offic…
- Potential benefitMay deter excessive or opportunistic price increases by creating a reporting requirement and public record in FAPIIS, p…
Defense Industry Pricing Transparency Act
Referred to the House Committee on Armed Services.
This bill (Defense Industry Pricing Transparency Act) adds a new reporting requirement to title 10 of the U.S. Code for certain Department of Defense contracts awarded without full competition (other-than-competitive awards or awards justified under FAR 6.302). An offeror must report within 30 days after it becomes aware that the price of a product or service under a covered contract has met or exceeded one of three thresholds: 25% above the contract bid, 25% above what the Government paid in the prior calendar year, or 50% above what the Government paid more than five years earlier.
Scope vs. adequacy: liberals seek broader coverage and stronger enforcement; conservatives see the bill as overbroad or intrusive despite shared interest in reducing waste.
Relative to its intended legislative type, this bill creates a new statutory obligation requiring offerors to report specified price increases for certain noncompetitive contracts and prescribes a limited administrative consequence for failure to report (FAPIIS entry).
This bill (Defense Industry Pricing Transparency Act) adds a new reporting requirement to title 10 of the U.S. Code for certain Department of Defense contracts awarded without full competition (other-than-competitive awards or awards justified under FAR 6.302).
An offeror must report within 30 days after it becomes aware that the price of a product or service under a covered contract has met or exceeded one of three thresholds: 25% above the contract bid, 25% above what the Government paid in the prior calendar year, or 50% above what the Government paid more than five years earlier.
If an offeror fails to submit the required report, the Director of the Defense Contract Audit Agency or the relevant service acquisition executive must enter specified identifying and transaction information about the offeror and the product/service into the Federal Awardee Performance and Integrity Information System (or successor).
On content alone, the bill is a modest, administratively focused transparency measure with limited fiscal impact and a narrowly targeted scope, which makes it broadly acceptable in principle. Its main barriers are industry resistance and the legislative process (it will be most viable if folded into the annual defense authorization or a larger procurement reform package). Lack of punitive measures and clear thresholds improve political palatability, but absence of a cost estimate and potential pushback from contractors leave uncertainty.
Relative to its intended legislative type, this bill creates a new statutory obligation requiring offerors to report specified price increases for certain noncompetitive contracts and prescribes a limited administrative consequence for failure to report (FAPIIS entry). It provides explicit thresholds and basic assignment of responsibilities but leaves multiple implementation details unspecified.
Scope vs. adequacy: liberals seek broader coverage and stronger enforcement; conservatives see the bill as overbroad or intrusive despite shared interest in reducing waste.
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- Potential burdenAdds administrative and compliance burdens on contractors and on contracting officers/DCAA to track, report, and valida…
- Potential burdenMay discourage some firms—particularly small or single‑source suppliers—from participating in sole‑source procurements…
- Potential burdenCould slow procurement speed or reduce flexibility in emergency or contingency situations where noncompetitive contract…
Why the argument around this bill splits.
Scope vs. adequacy: liberals seek broader coverage and stronger enforcement; conservatives see the bill as overbroad or intrusive despite shared interest in reducing waste.
A mainstream liberal would likely view this bill positively as a narrow, practical step toward greater transparency and accountability in defense procurement, especially for sole-source awards where price-gouging risk is higher.
They would welcome public-sector oversight that could deter unjustified price increases and protect taxpayer dollars, but they would also note the law's limitations — it mandates reporting but does not create new fines or direct remedies.
Progressives would probably press for broader scope, stronger enforcement, public disclosure, and resources for audits and enforcement.
A centrist/moderate would likely see this as a modest, commonsense transparency measure aimed at limiting abuse in sole-source defense purchases without imposing heavy-handed price controls.
They would appreciate that it targets a specific procurement problem and is administratively light in concept, but would have pragmatic questions about implementation costs, definitional clarity (e.g., what constitutes becoming "aware" and how "price" is defined), and whether agencies have the capacity to act on the reports.
They would probably be cautiously supportive if implementation details and funding are clarified.
A mainstream conservative would view the bill with mixed feelings: they may welcome measures that increase accountability and reduce waste in defense spending, but would be concerned about additional federal micromanagement, administrative costs, and potential harm to the defense industrial base.
The requirement to report price increases (and the consequence of FPPIIS listing) may be seen as intrusive and risk exposing proprietary information, and could reduce supplier willingness to accept sole-source awards.
Overall, many conservatives would be skeptical and prefer market-driven or targeted enforcement approaches rather than broad reporting mandates.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
On content alone, the bill is a modest, administratively focused transparency measure with limited fiscal impact and a narrowly targeted scope, which makes it broadly acceptable in principle. Its main barriers are industry resistance and the legislative process (it will be most viable if folded into the annual defense authorization or a larger procurement reform package). Lack of punitive measures and clear thresholds improve political palatability, but absence of a cost estimate and potential pushback from contractors leave uncertainty.
- No Congressional Budget Office or cost estimate in the text; administrative costs to offerors and agencies (DCAA, service acquisition executives) are unknown.
- The bill uses 'becomes aware' as a trigger for reporting; that phrase could invite disputes about timing and scope of required reports unless clarified in regulation.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Scope vs. adequacy: liberals seek broader coverage and stronger enforcement; conservatives see the bill as overbroad or intrusive despite s…
On content alone, the bill is a modest, administratively focused transparency measure with limited fiscal impact and a narrowly targeted sc…
Relative to its intended legislative type, this bill creates a new statutory obligation requiring offerors to report specified price increases for certain noncompetitive contracts and prescribes a limited administrative…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.