Sponsors (3)
The bill creates a more accountable, government‑wide mechanism to modernize high‑risk federal IT using a revolving Fund, but stricter repayment rules and reduced appropriations oversight may block some needed projects, shift costs to operating budgets, and concentrate decision-making outside normal congressional review.
Federal agencies (and therefore taxpayers and users of federal services) can replace and modernize high‑risk legacy IT to improve cybersecurity and reduce outages for services the public relies on.
Agencies are required to repay transfers, preserving a revolving IT Modernization Fund that stays solvent until sunset and can finance future projects without repeated new appropriations.
Agencies must use milestone‑based, metric‑tied incremental transfers, increasing project accountability and reducing the risk of wasteful large upfront spending.
State and local governments, hospitals, and other public service providers could see needed modernization projects deterred if those projects lack clear mechanisms to reimburse the Fund and therefore become ineligible for transfers.
Agencies (and the state/local entities they contract with) may be forced to shift IT modernization costs onto operating budgets, potentially reducing funding for other programs or services.
Removing the requirement to follow reprogramming law or Appropriations Committee guidelines reduces traditional congressional procedural oversight of Fund transfers, concentrating decision authority outside regular appropriations review.
Based on analysis of 2 sections of legislative text.
Expands allowable uses of the federal IT modernization fund, requires reimbursement to keep the fund operational, authorizes suspension/termination for fraudulent applications, and narrows one reprogramming constraint.
Expands how a federal IT modernization fund may be used and how fund transfers are made: the Administrator may transfer amounts to agency heads to buy, develop, operate, or replace information technology, bolster cybersecurity and privacy, improve IT efficiency and service delivery, and pay for supporting services and Board/Director support. Projects must generally reimburse the Fund so it stays at an operational level until the Fund sunsets, funding may not be used for programs denied or restricted by Congress, and the Administrator (after Board recommendations) must suspend or terminate funding if an agency submitted fraudulent or misleading information in a Fund application. Also removes a previous procedural requirement that certain transfers be consistent with reprogramming law or Appropriations Committee guidelines and makes targeted technical edits to cross‑references and rules about repayment, transfers, and reporting for amounts moved from the Fund to agencies.
Introduced April 24, 2025 by Nancy Mace · Last progress April 24, 2025