Legacy IT Reduction Act of 2026
- Sponsor
- Rep. Frost, Maxwell [D-FL-10]
- Committees
- Oversight and Government Reform Committee (primary)
- Last action
- Apr 21, 2026
Bottom line
The bill aims to reduce federal government reliance on old, potentially inefficient or insecure IT systems by requiring agencies to plan for their modernization or replacement, without authorizing new funding and with a 6-year sunset clause.
What it actually does
This bill mandates federal agencies to identify and create plans to modernize, retire, or dispose of their outdated "legacy information technology systems." It requires agencies to compile an inventory of these systems, including their costs and update schedules, and then develop a 5-year modernization strategy. The Office of Management and Budget (OMB) is tasked with issuing guidance for these processes, and the Government Accountability Office (GAO) will review the Act's implementation.
Proponents argue
Proponents argue that modernizing federal IT systems is crucial for efficiency, cybersecurity, and delivering better services to the public. They contend that legacy systems are often costly to maintain, vulnerable to cyber threats, and hinder government agility. This bill provides a structured approach to address this long-standing problem by forcing agencies to inventory and plan for the retirement of these outdated systems, ultimately saving taxpayer money and improving government operations.
Opponents contend
Opponents might argue that while IT modernization is desirable, this bill places an unfunded mandate on agencies, potentially diverting resources from critical operational needs to compliance activities. They might also contend that the 6-year sunset clause and the lack of new funding could undermine the long-term effectiveness of the initiative, leading to a temporary effort rather than sustained change. Some might also raise concerns about the practicality of defining "legacy IT" and the administrative burden of detailed inventory and planning requirements.
The bill is relatively short and clearly structured, making it accessible for an informed reader to understand its core provisions within a reasonable timeframe.
Section 3(a)
Agency Inventory of Legacy IT Systems
This provision requires the Chief Information Officer (CIO) of each federal agency to create a comprehensive list of all outdated "legacy information technology systems" used by their agency. This inventory must be compiled within one year of the bill's enactment and updated every five years. The Office of Management and Budget (OMB) will provide guidance on what specific details to include for each system, such as its purpose, last update, annual operating costs, and planned retirement date.
Supporters argue
Supporters argue that a clear, comprehensive inventory is the essential first step to understanding the scope of the legacy IT problem across the federal government. Without knowing what systems exist, their costs, and their age, effective modernization planning is impossible. This provision provides the necessary data foundation.
Critics contend
Critics might argue that compiling such a detailed inventory for every legacy system could be an immense, resource-intensive task for agencies, especially without additional funding. They might contend that agencies already have some understanding of their IT landscape, and this mandate could lead to a bureaucratic exercise rather than meaningful change, diverting resources from actual modernization efforts.
Tradeoffs
The tension lies between the need for comprehensive data to inform strategic decisions and the administrative burden and cost associated with collecting and maintaining that data, especially for complex, decentralized IT environments.
Section 4(a) and (b)
Development of Legacy IT Modernization Plans
This provision requires each agency head to develop a plan for modernizing their legacy IT systems. These plans must be submitted as part of the agency's broader information resource management strategic plan within two years of the bill's enactment, and then every five years. The plans must identify prioritized systems for updates, modernization, retirement, or disposal, and outline the steps the agency intends to take over the subsequent five-year period.
Section 8
Funding Limitation and Sunset Clause
This section explicitly states that no additional funds are authorized to be appropriated to carry out the Act. Furthermore, the entire Act will cease to have force or effect six years after its date of enactment. This means the bill's mandates for inventory and planning are temporary and must be accomplished using existing agency budgets.
The bill defines "legacy information technology system" by referencing section 1076 of the National Defense Authorization Act for Fiscal Year 2018 (40 U.S.C. 11301 note; Public Law 115-91). This external reference is crucial because the entire premise of the bill hinges on this definition.
Section 2(8)
Why it matters:This is standard legislative practice to avoid reprinting lengthy definitions already established in law and to ensure consistency across statutes.
Case for: Referencing existing definitions promotes consistency in federal law and avoids redundant text. It leverages prior legislative work on defining complex terms.
Case against: For a casual reader, this requires extra effort to fully understand the bill's scope, potentially obscuring the exact criteria for what constitutes a "legacy system" that agencies must inventory and modernize.
Estimated impact: The precise scope of the bill's application to federal IT systems is entirely dependent on this external definition.
This subsection explicitly states that nothing in the Act should be construed to authorize the transfer of legacy information technology systems or equipment to the Chinese Communist Party, the People's Republic of China, or any entity controlled by the People's Republic of China.
Section 7(c)
Why it matters:While related to security, its specific focus on China suggests a political sensitivity or a desire to explicitly prevent a specific perceived risk, potentially placed here to avoid drawing undue attention as a standalone provision.
Case for: Proponents would argue this is a critical safeguard to prevent sensitive federal IT assets from falling into the hands of a geopolitical rival, aligning with broader national security concerns regarding China's technological ambitions.
Case against: Critics might argue that while the intent is understandable, such a provision could be seen as redundant if existing laws already prevent such transfers, or that its inclusion here might imply a risk that isn't directly addressed by the bill's primary purpose of IT modernization. Some might also see it as a political statement rather than a necessary functional clause.
Estimated impact: Prevents a specific, potentially high-risk transfer scenario, reinforcing national security policy.