The Office of Management and Budget issued Memorandum M-26-10, "Reinforcing Transparency, Accountability, and Oversight of Federal Technology," on March 31, 2026, effective immediately for all solicitations and contracts issued after that date. The memo forces a structural change in how information technology vendors do business with the federal government: pricing and utilization data that vendors once shared only with individual agency customers must now be disclosed in machine-readable formats suitable for government-wide compilation and sharing. For IT vendors — whether selling commercial software, cloud services, or custom development — M-26-10 introduces disclosure obligations and agency oversight mechanisms that will affect everything from how task orders are structured to how pricing strategies are built and defended under government scrutiny. Vendors who do not adapt their contracting approach and internal pricing practices face elevated enforcement exposure as this data becomes visible across the interagency community.
Core Disclosure and Oversight Requirements
M-26-10 establishes two interlocking requirements that together create a federal IT pricing transparency architecture unlike anything previously in place. On the vendor side, IT contractors must disclose utilization and pricing information without contractual terms that would limit cross-agency sharing. Historically, many enterprise software agreements included most-favored-nation clauses, confidentiality provisions, or other language that prevented one agency from learning what another agency paid for the same product. Under M-26-10, such restrictions are incompatible with the new policy framework. Pricing data must be structured in machine-readable formats — a requirement that applies not just to future agreements but to the terms under which agencies enter new task orders and modifications on existing vehicles.
On the agency oversight side, M-26-10 dramatically expands the role of Chief Information Officers. CIOs at CFO Act agencies must review and approve IT purchases before spending occurs — a shift from the advisory role CIOs have historically played in many agencies to a gating function with real authority to block procurements outright. CIOs must also advise agency heads on whether to continue, modify, or terminate IT programs, giving the CIO function direct influence over the lifecycle management of contracts already in place. Beginning in May 2026, CIOs at CFO Act agencies must submit monthly reports to OMB detailing all approved IT contracts, with that reporting obligation running through October 2026, accumulating a detailed government-wide dataset of IT contract activity in near real time.
The memo's two sections work in concert to build a comprehensive IT transparency architecture. Section 1 empowers CIOs through statutory FITARA authority, requiring personal CIO review and approval of IT contracts. Section 2 eliminates information silos by directing agencies to actively request and share IT pricing and utilization data government-wide. Together, CIO pre-approval gates and the mandatory OMB monthly reporting cycle create multiple checkpoints that will increase government-side visibility into IT spending patterns across the executive branch.
Perhaps the most consequential long-run provision is the explicit authorization to share disclosed pricing and utilization data with government enforcement stakeholders. The memo states that shared data may trigger audits or investigations. For vendors whose pricing strategies have relied on information asymmetry — different agencies paying materially different prices for equivalent products — the creation of a government-wide pricing dataset represents an existential threat to those strategies. Contracting officers who previously lacked visibility into what other agencies paid for the same solution will gain access to a consolidated pricing picture that could support price reasonableness determinations, defective pricing claims, and False Claims Act referrals from inspectors general or the Department of Justice.
What It Means for Contractors
The immediate action item for IT vendors is a contract portfolio review. Any existing agreement that contains language restricting the agency's ability to share pricing or utilization data with other government entities is now in tension with M-26-10. Vendors should identify those provisions and assess whether they must be renegotiated as a condition of renewal, modification, or option exercise. Agencies may begin requesting contractual modifications to remove restrictive clauses even on existing contracts as they work to comply with the memo's requirements, and vendors who resist those modifications risk being viewed as non-compliant with government-wide policy.
Vendors should also prepare for a more rigorous pre-award process at every agency. The requirement that CIOs review and approve IT purchases before spending occurs means that a contracting officer's award decision is no longer the final internal hurdle in the procurement process. Vendors whose deals stall in the CIO review layer — for reasons related to enterprise architecture alignment, cybersecurity posture, or competing agency priorities — may face unpredictable delays not present under prior practice. Building CIO review timelines into program schedules and proposal development assumptions is now a practical operational necessity for any IT contractor competing for federal business.
The monthly reporting obligation that CFO Act agency CIOs must fulfill through October 2026 creates a secondary visibility effect that extends beyond individual agency relationships. OMB will accumulate detailed, current data on the IT contract landscape across the government throughout the second half of 2026. Vendors with large federal footprints across multiple agencies should model what a consolidated view of their pricing data reveals and prepare to defend price differentials on a principled, documented basis before that dataset is complete and in the hands of agency reviewers and enforcement stakeholders who have explicit authority to act on it.
The enforcement referral provision is the highest-stakes element of M-26-10 for established IT vendors. The full memo, available at whitehouse.gov, makes clear that pricing data shared across the government may be used not just for acquisition planning but for enforcement purposes. Vendors should review their existing pricing practices against the risk that historical differentials — once invisible due to agency-level silos — become visible to inspectors general, DOJ False Claims Act reviewers, or congressional oversight bodies. Proactive price normalization, accompanied by documented business rationale for any remaining differentials, is a defensible posture. Continued reliance on information asymmetry as a pricing strategy is not sustainable under the transparency framework M-26-10 puts in place.
