S. 1956 (119th)Bill Overview

Strengthening Agency Management and Oversight of Software Assets Act

Government Operations and Politics|Accounting and auditingBudget process
Cosponsors
Support
Lean Republican
Introduced
Jun 4, 2025
Discussions
Bill Text
Current stageCommittee

Read twice and referred to the Committee on Homeland Security and Governmental Affairs.

Introduced
Committee
Floor
President
Law
Congressional Activities
01 · The brief
Plain-English summaryWhat this bill actually does

This bill requires federal agencies to complete a comprehensive assessment of software inventories and entitlements within 18 months, then develop agency plans to consolidate, manage, and modernize software asset management. Agencies must report assessments and plans to OMB, GSA, GAO, and congressional oversight committees; OMB and GSA will coordinate government-wide guidance and submit recommendations.

Why people may split

Centralization vs bureau-level procurement flexibility

Watch point

Relative to its intended legislative type, this bill is a well-structured administrative/operational measure that prescribes detailed assessments, planning, roles, timelines, and reporting to improve agency software asset management, while also producing government-wide reporting through OMB/GSA and GAO.

This bill requires federal agencies to complete a comprehensive assessment of software inventories and entitlements within 18 months, then develop agency plans to consolidate, manage, and modernize software asset management.

Agencies must report assessments and plans to OMB, GSA, GAO, and congressional oversight committees; OMB and GSA will coordinate government-wide guidance and submit recommendations.

The bill mandates training, automation, discovery tools, and restrictions on internal software acquisitions without CIO approval, and directs a GAO report within three years.

Passage40/100

Low-controversy, administrative reform increases prospects, but unfunded mandates, industry pushback, and legislative calendar constrain chances.

CredibilityPartially aligned

Relative to its intended legislative type, this bill is a well-structured administrative/operational measure that prescribes detailed assessments, planning, roles, timelines, and reporting to improve agency software asset management, while also producing government-wide reporting through OMB/GSA and GAO.

Contention58/100

Centralization vs bureau-level procurement flexibility

02 · What it does

Who stands to gain, and who may push back.

Likely benefits vs burdens50% / 50%
Likely helpedLikely burdened

These are examples from the analysis, not a ranked list of the most-affected groups.

Likely helped
  • Potential benefitMay reduce duplicate software purchases and licensing waste across agencies.
  • Potential benefitCould lower long‑term software spending through enterprise licensing and consolidated procurement.
  • Potential benefitImproved inventory visibility may strengthen cybersecurity and asset tracking.
Likely burdened
  • Potential burdenImposes additional administrative and compliance burdens without authorizing new funding.
  • Potential burdenCentralized approval requirements may slow procurement and reduce bureaus' operational flexibility.
  • Potential burdenShort-term costs for remediation, discovery tools, and migration could rise before savings accrue.
03 · Why people split

Why the argument around this bill splits.

Centralization vs bureau-level procurement flexibility
Progressive85%

Likely supportive overall because the bill prioritizes transparency, cost reduction, interoperability, and open licensing.

Values the emphasis on reducing duplicative spending, training public servants, and exploring open-source or enterprise licensing.

Concerned about the lack of new funding and potential gaps in protecting data access or privacy during inventory disclosures.

Leans supportive
Centrist70%

Generally favorable, viewing the bill as pragmatic housekeeping to reduce waste and improve governance.

Appreciates timelines, reporting, and GAO oversight but worries about unfunded mandates and execution burden.

Wants clear metrics, phased implementation, and accountability to ensure costs do not exceed savings.

Leans supportive
Conservative35%

Skeptical about increased centralization of procurement and added reporting requirements.

Concerned that CIO approval restrictions and harmonized definitions will expand bureaucracy and limit flexibility.

Worries agencies will face unfunded mandates and that vendors could be unfairly disadvantaged by prescriptive guidance.

Likely resistant
04 · Can it pass?

The path through Congress.

Introduced

Reached or meaningfully advanced

Committee

Reached or meaningfully advanced

Floor

Still ahead

President

Still ahead

Law

Still ahead

Passage likelihood40/100

Low-controversy, administrative reform increases prospects, but unfunded mandates, industry pushback, and legislative calendar constrain chances.

Scope and complexity
52%
Scopemoderate
52%
Complexitymedium
Why this could stall
  • No cost estimate or budgetary scoring provided
  • Agency capacity to implement without new funding
05 · Recent votes

Recent votes on the bill.

No vote history yet

The bill has not accumulated any surfaced votes yet.

06 · Go deeper

Go deeper than the headline read.

Included on this page

Centralization vs bureau-level procurement flexibility

Low-controversy, administrative reform increases prospects, but unfunded mandates, industry pushback, and legislative calendar constrain ch…

Unlocked analysis

Relative to its intended legislative type, this bill is a well-structured administrative/operational measure that prescribes detailed assessments, planning, roles, timelines, and reporting to improve agency software ass…

Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.

Perspective breakdownsPassage barriersLegislative design reviewStakeholder impact map
Open full analysis