The bill strengthens targeting, accountability, and transparency for STC resources, but risks leaving less-prepared communities behind and could create administrative burdens or perverse incentives if metrics are not well designed.
Taxpayers, local and state governments, and congressional oversight bodies will get stronger accountability and transparency because the bill requires performance metrics, monitoring of STC spending/outcomes, and a mandated congressional report on participation and performance within two years.
State and local governments will receive clearer, capability-based criteria for STC designation so assistance can be targeted to jurisdictions that meet demonstrated capability benchmarks.
Less-prepared and vulnerable jurisdictions (and the communities they serve) could be deprioritized for STC resources, leaving them with reduced support and higher risk.
If metrics are poorly designed, hospitals, health systems, and local governments may focus on meeting measurable outputs instead of actual preparedness, reducing program effectiveness.
The new metric-setting and monitoring requirements will impose administrative burdens on the Department of Homeland Security and local partners, which could slow program delivery or divert resources toward reporting instead of frontline preparedness.
Based on analysis of 2 sections of legislative text.
Revises Securing the Cities to select jurisdictions by preparedness and risk, requires DHS to set and monitor performance metrics, and mandates a two-year report to Congress.
Alters the federal Securing the Cities program by changing how jurisdictions are chosen, requiring the Department of Homeland Security to set performance metrics and milestones, monitor spending and outcomes, and report to the congressional homeland security committees within two years with participation and performance details and any planned program changes. The bill does not appropriate new funds but changes program oversight and selection criteria to focus on jurisdictional preparedness and relative threat.
Introduced February 14, 2025 by Troy Carter · Last progress March 11, 2025