What OMB M-26-10 Means for Federal Agencies and Software Oversight 

Federal agencies are facing renewed pressure to show that technology spending is transparent, accountable, and aligned to mission needs. OMB Memorandum M-26-10 reinforces this expectation more directly by strengthening oversight responsibilities for agency leaders and requiring stronger visibility into IT contracts, pricing, and utilization data. 

For many agencies, this creates a practical challenge. It is not just about understanding the memo; it is about having the data, governance, and software oversight needed to respond with confidence.  The good news is that agencies do not need to wait for mandates to take full effect before making progress. Early steps toward better visibility and control can reduce risk now and make future reporting much easier. 

With growing attention on waste, fraud, and abuse in federal spending, agencies need to demonstrate a clearer view of what they have purchased, what they are using, and where risk may be building. OMB M-26-10, along with broader efforts such as the Strengthening Agency Management and Oversight of Software Assets Act (SAMOSA), signals a clear direction: stronger accountability for software and IT spending is becoming a higher priority across government. 

 What OMB M-26-10 Requires from Federal Agencies 

OMB M-26-10 places strong emphasis on transparency, accountability, and oversight of federal technology. It strengthens the role of CIOs in technology decisions while pushing agencies to break down information silos around IT acquisitions and vendor data. 

For covered CFO Act agencies, the memo requires CIOs to report approved IT contracts and certain delegated approvals to OMB every month, beginning in May 2026.  

The memo also calls on agencies to request utilization and pricing data from current IT vendors, include contract language that supports future disclosure, compile the information in a machine-readable format, and share it with OMB and GSA when requested. 

In other words, agencies need more than commitment to deliver effective outcomes. They need usable data, repeatable processes, and confidence that their technology environment can support executive scrutiny. 

Why OMB M-26-10 Matters Now 

For many agencies, growth in software spending has outpaced corresponding visibility and control. Licensing terms have become more complex, and vendor ecosystems continue to expand. At the same time, procurement, deployment, and usage data often sit in different systems with limited connection between them. 

As a result, agencies may end up paying for more software than is necessary, face challenges in demonstrating compliance with publisher licensing terms, or struggle to respond quickly to leadership requests for a clear and comprehensive view of technology spending and value. 

OMB M-26-10 underscores the urgency of this issue, but it is not an isolated directive. It reflects a broader federal emphasis on accountability in software and IT spending. Related initiatives, such as SAMOSA, reinforce this same direction. Agencies are increasingly expected to improve visibility into software usage, strengthen license management practices, and reduce inefficiencies across their technology environments.  

 Taken together, these efforts underscore a clear imperative: strong software asset management is no longer optional. It is now a core component of how agencies manage risk, control costs, and demonstrate responsible stewardship of public funds. 

This is about control, not just compliance 

OMB M-26-10 has been interpreted as an additional reporting requirement; however, such a view overlooks its broader intent. The memorandum is fundamentally concerned with whether agencies possess sufficient control over their technology environments to enable informed decision-making, respond effectively to oversight inquiries, and demonstrate responsible stewardship of taxpayer resources. 

This level of control requires more than periodic reporting. It depends on a comprehensive and accurate understanding of what has been procured, what is owned, what is actively in use, and where risks may be emerging. With this visibility in place, agencies are better positioned to take proactive action, reduce unnecessary expenditure, and strengthen decision-making across procurement, finance, and IT functions.  

Why Agencies Struggle with Software Oversight and Reporting 

Most agencies are not starting from a clean slate. Software and hardware data often live in different systems. Contract terms may sit with one team, while deployment data sits with another. Usage information is often incomplete, inconsistent, or difficult to validate. As a result, even agencies with strong personnel and well-defined processes may face challenges in consolidating information quickly and effectively. 

That is where the challenge becomes practical rather than theoretical. When leaders seek to understand where inefficiencies exist, which publishers present the greatest exposure, or whether the agency can confidently support OMB reporting requirements, the answers are not always readily available. The issue is rarely a lack of effort. More often, it is a lack of connected, reliable data. Anglepoint helps fill that gap by working collaboratively with agencies to validate usage and entitlement data, provide an independent view of software utilization, and turn disconnected information into practical insight that supports reporting, optimization, and cost reduction goals.  

How Anglepoint Helps Federal Agencies Meet OMB M-26-10 Requirements 

OMB M-26-10 introduces new reporting expectations; however, its broader significance lies in organizational readiness. Agencies that act proactively can do more than satisfy compliance requirements—they can strengthen oversight, reduce waste, improve visibility into software licensing, and make more informed technology decisions based on trusted data. 

That is where Anglepoint helps. We work collaboratively with agencies to make sense of reporting data, software entitlements, usage, and compliance risk, and turn those insights into practical action that supports mission outcomes. For agencies seeking to get ahead of these requirements, this work establishes a stronger foundation not only for reporting but also for long-term stewardship of taxpayer resources. 

Agencies need not wait for formal deadlines or commit to a large, long-term engagement to begin building this foundation. Through a one-time Software Licensing Entitlement Assessment (SLEA) and targeted workshops, often structured below common simplified procurement thresholds, Anglepoint helps identify immediate risks, inefficiencies, and accountability gaps, enabling agencies to prioritize remediation efforts and strengthen oversight over time.