Modernizing Government Technology Reform Act
Sponsored By: Senator Moran, Jerry [R-KS]
Introduced
Summary
Tightened oversight and repayment for the Technology Modernization Fund (TMF). This bill would realign TMF dollars to prioritize defensible IT modernization, enforce repayment rules, and add CIO-led risk lists to focus federal IT and cybersecurity work.
Show full summary
- Agencies could get TMF transfers to modernize, retire, or replace legacy IT, improve cybersecurity, or pay for supporting services. Funds transferred would need to be reimbursed to the TMF and could be released only with milestone-based development and reporting; funding can be suspended or terminated if an agency made fraudulent or misleading statements in its application.
- Agency chief information officers (CIOs) would have to give the Federal Chief Information Officer a list of high-risk legacy systems within 180 days of guidance and update it yearly. The Federal CIO would compile the top 10 highest-risk systems within 90 days of each agency list and report those lists to Congress within 14 days.
- The board and Director would face tighter repayment, reporting, and governance rules, including a 10-day congressional copy requirement for written agreements. The updated governance and oversight would remain in place until the TMF sunsets after December 31, 2032.
Your PRIA Score
Personalized for You
How does this bill affect your finances?
Sign up for a PRIA Policy Scan to see your personalized alignment score for this bill and every other piece of legislation we track. We analyze your financial profile against policy provisions to show you exactly what matters to your wallet.
Bill Overview
Analyzed Economic Effects
7 provisions identified: 5 benefits, 0 costs, 2 mixed.
New TMF transfers with repayment
If enacted, the Administrator would be able to transfer Technology Modernization Fund money to agency heads for IT work when more efficient. Transfers would remain available until expended and could pay for development, operations, or cybersecurity. Except in documented compelling cases, transfers would be incremental and tied to metric-based milestones. Agencies would have to sign written agreements to reimburse the Fund so the Fund stays able to operate until its sunset.
Fixed end date for TMF
If enacted, the Fund's statutory sunset would be a fixed calendar date: after December 31, 2032. This would replace the earlier GAO-report trigger and give agencies and administrators a clearer end date for planning projects. The change would not itself appropriate new funds or change eligibility rules.
Agency CIO lists and top-10 risks
If enacted, each agency CIO would give the Federal CIO a list of high‑risk legacy IT systems within 180 days after Director guidance, and update it annually. The Federal CIO would pick the 10 systems that pose the biggest risks within 90 days of receiving lists. The Director would issue guidance within 180 days after enactment. The Director would send lists and updates to Congress and the Comptroller General within 14 days.
Stricter Board checks and fraud rules
If enacted, the Board would have to weigh an agency's ability to repay Fund transfers when recommending support. The Board would prioritize projects that retire or replace high‑risk legacy IT systems. The Board could flag fraudulent or misleading application statements, and the Administrator would have to suspend or end funding for projects tied to such fraud.
Congress gets TMF agreement copies
If enacted, the Director would have to give either the Senate Homeland Security and Governmental Affairs Committee or the House Oversight and Government Reform Committee a copy of any written TMF agreement covered by the rule within 10 days of a request. The rule aims to increase congressional oversight and transparency.
More reporting on repayments and savings
If enacted, the Board would send reports every two years until it ends. Reports would list amounts agencies repaid to the Fund under written agreements. Reports would also state total cost savings from projects rather than focusing only on projected savings.
Standard solvency language for TMF
If enacted, statutory text and reports would use one solvency rule: total Fund amounts must be no less than needed to keep the Fund operational until it sunsets. Certain cross-references would be broadened for consistency. These edits aim to clarify oversight and reporting but do not change who is eligible for funds.
Sponsors & CoSponsors
Sponsor
Moran, Jerry [R-KS]
KS • R
Cosponsors
Gary Peters
MI • D
Sponsored 12/2/2025
Roll Call Votes
No roll call votes available for this bill.
View on Congress.gov