SB1956, the Strengthening Agency Management and Oversight of Software Assets Act, would require each federal agency to conduct a comprehensive assessment of software paid for, in use at, or deployed within the agency. The assessment would inventory software entitlements, contracts, and costs, identify large entitlements by provider and category, and evaluate interoperability across the agency’s software ecosystem.
The bill then requires agencies to develop a modernization plan that consolidates entitlements, adopts cost-effective procurement strategies (including enterprise licensing), and imposes governance to restrict purchases or deployments without CIO approval. It also establishes reporting and oversight provisions and directs routine collaboration among CIOs, CFOs, Acquisition Officers, and data and legal offices.
No new funds are authorized to carry out these requirements, placing the implementation burden on current agency budgets.
At a Glance
What It Does
Requires a comprehensive software assessment, consolidation of entitlements, and a modernization plan that emphasizes cost-effective procurement and governance over software purchases and deployment.
Who It Affects
Federal agencies’ CIOs, CFOs, Acquisition Officers, data officers, general counsels, and program offices; cloud service providers and software vendors tied to agency contracts.
Why It Matters
Sets a government-wide approach to software governance, aiming to reduce duplication and cost, improve interoperability, and establish accountability for software investments across the federal portfolio.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill starts by laying out definitions for the key players and terms it uses, including what counts as software entitlements, inventories, and cloud arrangements. It then requires each agency’s top IT leaders to conduct a comprehensive review of all software assets within 18 months of enactment.
That review must map the current software inventory, list entitlements and the contracts behind them, quantify costs (including cloud-related fees and upgrade costs), and assess how well the different software pieces work together across the agency. The assessment also checks for restrictions embedded in entitlements that could limit deployment, access, or data ownership.
Importantly, the review must consider whether software is interoperable with other agency systems and what is being done to improve that interoperability. The plan for modernization, due within a year after the assessment, must outline how entitlements will be consolidated, how the agency will pursue cost-effective licenses (like enterprise licensing), and how to prevent unilateral acquisitions that bypass CIO oversight.
It requires training for staff on the new policies, automation of license management where feasible, and governance measures to maximize software value while limiting waste. The act directs ongoing consultation with the Director and Administrator, and it instructs agencies to share best practices to support standardization and interoperability across the government.
Finally, Congress and GAO oversight are preserved through mandated reporting, while no additional funding is authorized for this program, meaning agencies must absorb the costs within existing budgets.
The Five Things You Need to Know
The bill requires an 18-month comprehensive software assessment by each agency’s CIO and designated officers.
The assessment must catalog software entitlements, contracts, and total lifecycle costs, including cloud-related fees.
Plans must consolidate entitlements, promote cost-effective licenses (e.g.
enterprise licensing), and require CIO approval for certain acquisitions.
The plan must include training, automation, governance, and interoperability enhancements to maximize software efficiency.
No new funds are authorized; implementation must occur within existing agency budgets.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions and Key Terms
Section 2 defines terms used throughout the bill, including Administrator (GSA), Agency (per 44 U.S.C. 3502), Cloud Computing (per NIST SP 800-145 or successor), Cloud Service Provider, Comprehensive Assessment, Director (the Director of OMB), Plan (the agency CIO’s plan under section 4), Software Entitlement, and Software Inventory. The definitions create a standardized vocabulary to support cross-agency comparability and accountability in software asset management.
Software Inventory Update and Expansion
Section 3 requires the CIO, in consultation with CFO, CIO, CAO, Chief Data Officer, and General Counsel, to complete a comprehensive assessment of software paid for, in use, or deployed across the agency within 18 months of enactment. The assessment must inventory software, entitlements, contracts, and large entitlements by provider, and assess interoperability and related costs (including ancillary cloud charges). It also mandates evaluation of contract terms that may restrict deployment or data ownership, and requires a check of the accuracy and completeness of the assessment and the agency’s compliance with software license management policies.
Software Modernization Planning at Agencies
This section obligates the agency’s CIO to develop a plan (with CFO, CAO, Data Officer, and General Counsel) to consolidate entitlements, pursue cost-effective acquisition strategies (including enterprise licensing), and restrict internal entities from acquiring or deploying software without CIO (and depending on approval, CAO) consent. The plan must include remediation of management deficiencies, ongoing maintenance, automation of license management, training, and governance to support interoperability and data ownership considerations. It also requires cost estimates for moving toward open or enterprise licensing and set-out timelines for implementing changes.
GAO Reporting
Section 5 directs the Comptroller General to prepare a government-wide evaluation within three years of enactment. The GAO report will compare agency practices, summarize cross-agency processes, and assess compliance with procurement and licensing restrictions, while highlighting efficiency, interoperability, and modernization outcomes.
Funding
Section 6 states that no additional funds are authorized to carry out this Act; agencies must fund the required assessments, plans, and related activities from existing budgets.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government 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
- CIOs and their offices, who gain a structured framework for software governance and clearer authority over licensing decisions.
- CFOs and CAOs, who achieve better cost visibility, budgeting, and procurement efficiency.
- Program offices and software asset managers, who receive standardized reporting, improved interoperability, and clearer licensing terms.
- The GAO and Congress, which obtain standardized data and reporting to assess cross-agency trends and policy impact.
Who Bears the Cost
- Agency IT and program staff time dedicated to conducting the comprehensive assessment and implementing the plan.
- Contractors hired to support the comprehensive assessment and modernization planning (subject to independence requirements in the bill).
- Agencies may need to adjust procurement practices and training programs, potentially reconfiguring budgets to accommodate new processes and governance.
Key Issues
The Core Tension
The central dilemma is whether agencies can overhaul software asset management—consolidating licenses, improving interoperability, and reducing costs—without dedicated funding and while preserving the flexibility to support diverse missions and vendor relationships.
The act creates a sweeping set of requirements that touch nearly every element of how agencies buy, manage, and deploy software. While the goal is clearer oversight and lower costs, the execution hinges on accurate data, timely reporting, and the ability to shift licensing models and practices across dozens of separate agencies.
A core risk is the tension between aggressive modernizing timelines and the lack of new funding — agencies must absorb these activities within existing resources, which could strain operations during the transition. A second tension concerns standardization across agencies versus the autonomy to adopt agency- or vendor-specific arrangements that may better fit unique mission needs.
The bill anticipates these tensions by emphasizing plans, governance, and cross-agency coordination, but it leaves unresolved questions about how exactly agencies will fund and institutionalize these changes over time.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.