PolicyBrief
S. 1956
119th CongressJun 4th 2025
Strengthening Agency Management and Oversight of Software Assets Act
IN COMMITTEE

This Act mandates federal agencies to conduct comprehensive software inventories, develop modernization plans to consolidate licenses and reduce costs, and subjects these practices to GAO review.

Gary Peters
D

Gary Peters

Senator

MI

LEGISLATION

Federal Agencies Must Inventory All Software and Costs Within 18 Months to Cut Waste

If you’ve ever had to manage a spreadsheet of software licenses at your job, you know how quickly things get messy. Now imagine that chaos scaled up to the entire federal government, where every agency, bureau, and department is buying its own specialized tools.

The Strengthening Agency Management and Oversight of Software Assets Act is basically an overdue, mandatory spring cleaning for the government’s digital closets. It requires every federal agency to conduct a full, comprehensive inventory of all the software they use, pay for, or have installed. This isn't just a quick list; agencies have 18 months from the bill’s enactment to detail every piece of software, including all related costs—even the hidden ones like cloud service fees and maintenance—and report it all to the Office of Management and Budget (OMB) and Congress.

The Great Digital Audit: What’s Really Being Spent?

This bill aims to fix a massive, expensive problem: agencies often pay for the same software multiple times, or they keep renewing licenses for tools no one uses anymore. Section 3 mandates that the Chief Information Officer (CIO) of each agency, working with their finance and acquisition teams, must track down the total cost of ownership. This includes identifying software that seems “unnecessary or is causing duplication,” which is a nice way of saying, “find the subscriptions we forgot to cancel five years ago.”

For the taxpayer, this is a clear win. When the government knows exactly what it owns and what it’s spending, it can stop wasting millions on redundant licenses. For the IT staff inside those agencies, however, this means a huge, immediate workload. They have to map out every single software entitlement and contract restriction—like whether a vendor prohibits using their tool in a modern cloud environment—before they can even start planning the fix.

Centralizing Control to Stop Rogue Spending

Once the audit is done, Section 4 requires the CIO to create a detailed Software Modernization Plan. The core of this plan is centralization. Moving forward, no bureau or program within an agency can buy, use, or develop any software without the green light from the agency’s CIO and Acquisition Officer. Think of the CIO as the new gatekeeper, ensuring that every new purchase aligns with agency-wide goals and cost-saving strategies like moving to cheaper enterprise licenses or open-source solutions.

This centralization is designed to give the government better negotiating power. If the Department of Transportation and the Department of Energy both need the same database software, the plan is for them to buy one massive license instead of two smaller, more expensive ones. This is a smart move that could save serious cash, but it also creates a potential bottleneck: if the CIO’s office isn't staffed up and efficient, this new approval process could slow down necessary upgrades and development across the agency.

Training and Transparency: The Fine Print that Matters

The bill also requires mandatory training for staff involved in software buying and development. This training focuses on negotiating contracts to avoid vendor lock-in—specifically, clauses that restrict where software can be deployed (like forcing them to use specific hardware or prohibiting cloud use) or restrict data ownership. This is crucial because those hidden contract restrictions are often what prevent agencies from modernizing their systems efficiently.

Finally, the bill has a very important caveat in Section 6: No additional funds are authorized. This means that all the massive work required—the 18-month inventory, the comprehensive assessment, the modernization planning, and the staff training—must be paid for using existing agency budgets. While the goal is to save money, the initial push to comply will strain existing resources, potentially forcing agencies to delay other IT projects just to fund this mandatory cleanup. The Government Accountability Office (GAO) will then check up on all of this three years down the line to see if agencies actually followed through and if the new rules are working.