119-HR-5457 Investigative Journalist Impact Analysis

Summary

The bill compels every covered civilian agency to complete a comprehensive software assessment within 18 months of enactment, submit a CIO-led consolidation and modernization plan one year after the assessment, directs OMB to deliver a government‑wide recommendations report within two years, and tasks GAO to evaluate outcomes after three years. It authorizes no new funds. These deadlines create near‑term compliance costs but could surface duplication, tighten license governance, and improve leverage in renewals. [1]Congress.gov — H.R.5457 – Text (119th Congress)

Key metrics and timelines

Deadlines and the no‑appropriations clause derive from bill Sections 3–6; the data‑centre projection is the IEA’s 2030 base case. [1]Congress.gov — H.R.5457 – Text (119th Congress)[4]International Energy Agency — Energy and AI—Executive Summary

Economic Effects

Likely fiscal and market impacts based on prior GAO/OMB experience with software license management and category management.

• Savings potential from inventory‑driven consolidation: GAO has repeatedly found agencies lack complete, product‑level usage data, leading to overbuying and weak negotiations; improved inventories and analytics tend to unlock savings when contracts renew. [3]U.S. GAO — GAO-24-105717: Federal Software Licenses—Agencies Need to Take Action
• Policy continuity with MEGABYTE Act and OMB M‑16‑12: H.R. 5457 largely deepens existing requirements (enterprise oversight, inventories, training), which GSA and agencies have operationalized; this reduces implementation novelty but not the resourcing burden. [5]Congress.gov — MEGABYTE Act of 2016—Public Law 114‑210 (Text)[6]GSA Cloud Information Center — OMB M‑16‑12 (summary listing)—GSA Cloud Informat…[7]GSA — GSA Directive 2108.2 CIO—Software License Management
• Category‑management experience suggests material savings but mixed small‑business dynamics: OMB reported multiyear savings from category management, yet GAO observed a decline in the number of small‑business vendors participating in common‑goods/services markets, indicating consolidation can narrow entry points if not mitigated. [2]U.S. GAO — GAO-21-40: Federal Buying Power—OMB Can Further Advance Category Man…
• Administrative and transition costs: Standing up discovery tooling, normalizing contract/usage data, and training program staff impose costs that the bill does not separately fund; expect agencies to reprogram within existing IT portfolios in the first 1–2 years. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• Negotiating leverage vs. hyperscale/cloud lock‑in: Enhanced inventories and CIO approval can strengthen bargaining positions, but switching costs persist where software licensing terms and data‑egress fees (even when partially waived) inhibit multi‑cloud strategies; net pricing pressure may therefore be uneven across vendors. [8]Federal Trade Commission — FTC Cloud Computing RFI—What we heard and learned[9]U.S. GAO — GAO-23-106247: DOD Cloud—Tracking Data Egress Fees[10]TechCrunch — Microsoft to remove Azure egress fees (with caveats)[11]Washington Technology — Google Cloud eliminates exit fees for departing custome…
• Market signal to large vendors: Required disclosure of restriction clauses (e.g., deployment limits, data‑access terms) and emphasis on interoperability may push vendors to temper restrictive terms at federal scale, though analogous probes abroad show such practices can persist without explicit remedy. [1]Congress.gov — H.R.5457 – Text (119th Congress)[12]UK Competition and Markets Authority — CMA Cloud Services Market Investigation—…

Social Effects

Implications for the federal workforce, vendors (including small businesses), and transparency.

• Workforce skilling and governance: The bill requires training for acquisition and program staff on license options, deployment restrictions, and cost modeling, which should professionalize purchasing and reduce compliance errors over time. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• Small‑business participation: Greater use of enterprise licenses and centralized approval can shrink the number of discrete award opportunities; GAO has documented declining small‑business vendor counts in category‑managed spend, underscoring the need for OSDBU engagement during plan design. [2]U.S. GAO — GAO-21-40: Federal Buying Power—OMB Can Further Advance Category Man…
• Transparency and oversight: Standardized inventories and CIO plans, plus an OMB government‑wide report and a GAO audit, improve visibility for Congress and watchdogs; however, intelligence‑community submissions are limited to summaries, constraining public insight. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• Operational equity: Central CIO approval can reduce inconsistent bureau‑level buying but may slow urgent, specialized procurements unless accompanied by clear exception pathways—an implementation risk seen in other FITARA‑era reforms. [13]Web search · turn 7 #0

Environmental Effects

The bill is not an environmental measure, but software asset management can influence IT resource use.

• License rationalization can reduce wasteful compute: Eliminating unused seats and duplicative applications typically lowers background processing and storage, especially in SaaS and VDI contexts, though the magnitude depends on actual deprovisioning and contract terms. Evidence on federal baselines is limited due to current data gaps. [3]U.S. GAO — GAO-24-105717: Federal Software Licenses—Agencies Need to Take Action
• Cloud‑usage externalities: Even with efficiency gains, data‑centre electricity demand is set to more than double by 2030 in IEA’s base case, with the United States a major driver; without explicit efficiency and workload‑placement guardrails, consolidation could shift loads to hyperscalers and raise localized grid demand. [4]International Energy Agency — Energy and AI—Executive Summary
• Long‑run lever: Better meter‑level usage analytics required for license governance can also support demand management (e.g., right‑sizing compute/storage tiers), marginally moderating energy and emissions trajectories relative to unmanaged growth. [3]U.S. GAO — GAO-24-105717: Federal Software Licenses—Agencies Need to Take Action

Temporal Analysis

• 0–18 months (stand‑up period): Agencies inventory entitlements, map restriction clauses, and deploy discovery tools—high staff workload with limited immediate savings; Oversight Committee held a markup on December 2, 2025, indicating momentum but Congress.gov status updates may lag. [1]Congress.gov — H.R.5457 – Text (119th Congress)[14]Congress.gov — H.R.5457 – Overview (status/committee meeting)
• 18–36 months (renewal window): As major agreements renew, CIOs execute consolidation strategies and enterprise licenses; measurable savings and performance gains generally appear during this phase in prior category‑management efforts. [2]U.S. GAO — GAO-21-40: Federal Buying Power—OMB Can Further Advance Category Man…
• 24 months: OMB delivers a cross‑government recommendations report that can harmonize definitions, standard clauses on interoperability, and anti‑lock‑in practices. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• 36+ months: GAO’s report benchmarks agency compliance, conflict‑of‑interest controls on assessment contractors, and the effectiveness of training/automation—providing the first rigorous picture of realized savings vs. plan targets. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• External market timing: Cloud providers’ partial rollbacks of egress fees in 2024 help exits but still condition relief on full migration—limiting multi‑cloud elasticity; agencies should not assume frictionless switching in near‑term renegotiations. [10]TechCrunch — Microsoft to remove Azure egress fees (with caveats)[11]Washington Technology — Google Cloud eliminates exit fees for departing custome…

Unintended Consequences and Risks

• Unfunded mandate risk: Section 6 authorizes no new funds; absent reprogramming, agencies may defer other modernization to meet inventory/plan deadlines, diluting net savings. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• Data‑quality and tooling gaps: GAO finds agencies frequently lack product‑level usage data (bundled licenses, weak metering), which can blunt consolidation benefits unless corrected early. [3]U.S. GAO — GAO-24-105717: Federal Software Licenses—Agencies Need to Take Action
• CIO bottlenecks: Central approvals improve coherence but can introduce delays if staffing and delegation are not calibrated—consistent with GAO’s findings that governance and procurement delays hampered other FITARA implementations. [13]Web search · turn 7 #0
• Residual vendor lock‑in: Even with better inventories, restrictive license terms and egress economics can still deter workload mobility; U.S. regulators have flagged these patterns, and foreign competition authorities have documented similar harms. [8]Federal Trade Commission — FTC Cloud Computing RFI—What we heard and learned[9]U.S. GAO — GAO-23-106247: DOD Cloud—Tracking Data Egress Fees[12]UK Competition and Markets Authority — CMA Cloud Services Market Investigation—…
• Contractor conflicts: The bill bars organizational conflicts of interest for assessment support, but robust screening and firewalls will be needed in practice given integrators’ parallel reseller roles. [1]Congress.gov — H.R.5457 – Text (119th Congress)

Assessment (Analytical, not advocacy)

Neutral. The legislation is likely to produce net positive fiscal effects over a 2–4 year horizon if agencies can execute high‑fidelity inventories and leverage renewals, but those gains are contingent on addressing known data gaps, CIO capacity constraints, and cloud switching frictions. Without explicit funding or anti‑lock‑in procurement standards, outcomes will vary by agency maturity and vendor posture. [3]U.S. GAO — GAO-24-105717: Federal Software Licenses—Agencies Need to Take Action[2]U.S. GAO — GAO-21-40: Federal Buying Power—OMB Can Further Advance Category Man…[10]TechCrunch — Microsoft to remove Azure egress fees (with caveats)

Sourcing notes

• Bill text, deadlines, scope, and no‑funding clause. [1]Congress.gov — H.R.5457 – Text (119th Congress)
• Status/committee activity as of December 4, 2025. [14]Congress.gov — H.R.5457 – Overview (status/committee meeting)[15]House Oversight Committee — Oversight Committee—Markup Wrap Up (Dec. 2, 2025)
• Precedents and policy context: MEGABYTE Act and OMB M‑16‑12; GSA implementation directive. [5]Congress.gov — MEGABYTE Act of 2016—Public Law 114‑210 (Text)[6]GSA Cloud Information Center — OMB M‑16‑12 (summary listing)—GSA Cloud Informat…[7]GSA — GSA Directive 2108.2 CIO—Software License Management
• Evidence on license‑management gaps and savings potential: GAO 2014 and 2024. [16]U.S. GAO — GAO-14-413: Federal Software Licenses—Better Management Needed[3]U.S. GAO — GAO-24-105717: Federal Software Licenses—Agencies Need to Take Action
• Category‑management savings vs. small‑business participation. [2]U.S. GAO — GAO-21-40: Federal Buying Power—OMB Can Further Advance Category Man…
• Cloud switching frictions (egress/licensing) and market evidence. [8]Federal Trade Commission — FTC Cloud Computing RFI—What we heard and learned[9]U.S. GAO — GAO-23-106247: DOD Cloud—Tracking Data Egress Fees[10]TechCrunch — Microsoft to remove Azure egress fees (with caveats)[11]Washington Technology — Google Cloud eliminates exit fees for departing custome…
• Environmental baselines and projections for data‑centre demand. [4]International Energy Agency — Energy and AI—Executive Summary