The Office of Management and Budget’s March 31 memo requires CIOs at large federal civilian agencies to report all IT contracts monthly from May through October. The goal is to give the federal government a clear, top-down view of what agencies are buying, what they are paying, and where spending is duplicated. Here, we explain what’s driving that mandate, why it reflects a broader visibility problem that exists at every level of government, and what agencies can do to build the operational structure needed to meet it.
What Is the OMB IT Contract Reporting Mandate?
On March 31, OMB Director Russ Vought and Federal CIO Greg Barbaccia directed CIOs at large federal civilian agencies to submit monthly IT contract reports to OMB from May through October.
The stated goal is straightforward: identify duplicated software licenses, inconsistent contract pricing across agency offices, and technology investments that no single person in the agency has full visibility into. The GAO has flagged these issues repeatedly. The memo is OMB’s attempt to force accountability.
Agencies have until May to begin reporting — limited time to build visibility they may not already have.
Why Is IT Spending Visibility a Problem in Government Agencies?
The visibility problem is not located in procurement. It is located in operations.
Government agencies run on two kinds of technology work:
| Type | What It Looks Like | Where It Lives |
|---|---|---|
| Visible systems | Databases, applications, platforms | Formal IT infrastructure |
| Invisible coordination | Approvals, decisions, status tracking | Email threads, spreadsheets, meetings |
The contracts exist. The approvals happened. The problem is that the process connecting those decisions to the people responsible for them lived outside any system designed to track it — in a delegate approval that never surfaced to the CIO, or a program-level decision that was never formally recorded.
This is not unique to federal agencies. It is the default operating state for most government at every level.
Does This Mandate Apply Beyond Federal Agencies?
The memo applies to large federal civilian agencies, but the pressure it reflects exists at every level of government.
- State legislatures are asking the same questions about IT spending
- County executives want to know why technology projects run over budget
- Municipal CIOs are being asked to prove their systems are actually in use
The federal government tends to formalize these pressures first. The underlying dynamic is already present in agencies that have not yet received a formal mandate.
What Is the Operational Visibility Gap — and How Does It Create a Reporting Crisis?
The Operational Visibility Gap is the pattern that emerges when government agencies respond to reporting mandates without structured operational infrastructure in place.
The Four-Stage Pattern:
- Mandate arrives: A new reporting requirement is issued
- Teams are asked to produce a report: Leaders request information from staff
- Reconstruction begins: Teams discover the required data lives across multiple systems, informal approvals, and undocumented decisions
- Report is produced through staff effort: Compliance is achieved, but only through significant manual work
The result: the next mandate triggers the same cycle. This is not a compliance failure. It is a structural one.
What Does Operational Visibility Look Like in Practice?
Agencies that break the reporting-crisis cycle share a common operational structure:
| Without Operational Visibility | With Operational Visibility |
|---|---|
| Approvals run through email threads | Approvals run through defined, tracked processes |
| Decisions reconstructed after the fact | Decisions recorded where they happen |
| CIO learns about purchases after they occur | Purchases are visible to CIOs in real time |
| Reporting requires staff scramble | Reporting is a query, not a project |
The agencies that meet accountability requirements most effectively are not necessarily the ones with the most sophisticated technology. They are the ones where how decisions get made, how approvals move, and how programs run is visible and structured rather than informal and fragmented.
What Should Agency Leaders Do Now?
The OMB memo is one data point in a broader shift: agencies are increasingly expected to demonstrate not just that a program exists, but that it is running well, resources are being used appropriately, and decisions are being made accountably.
Three questions every agency leader should be asking today — regardless of jurisdiction or whether this specific mandate applies:
- Can your CIO see every active IT contract without chasing down approvals? If not, that information lives outside your structured systems.
- Do approvals run through defined processes or through email? Informal approvals are invisible approvals.
- When a new reporting requirement arrives, is your response a query or a scramble? The answer tells you whether your operational structure is working.
The question the OMB memo is really asking is not which contracts did your CIO approve. It is whether your agency has the operational visibility to answer that question without a crisis.
SimpliGov is the platform where government program teams design, run, and improve how their programs operate. Learn how agencies are building operational visibility by meeting with a SimpliGov expert.
