When Hurricane Helene made landfall in late September 2024 and Milton followed two weeks later, FEMA activated what it would later describe as its largest-ever disaster workforce. Thousands of individual assistance inspectors, public assistance coordinators, disaster survivor assistance teams, and logistics personnel deployed simultaneously across Florida, Georgia, North Carolina, South Carolina, and Tennessee.
The scale was unprecedented. The data infrastructure supporting that scale was not.
What followed — across both storm responses and into 2025’s recovery operations — exposed a fundamental problem that emergency management professionals have known about for years but rarely have the political will to fix: the systems used to manage disaster survivors, track assistance delivery, and coordinate intergovernmental response were not built for the complexity of back-to-back catastrophic events affecting overlapping geographic areas.
The Specific Failures
The most visible data problem was duplication and verification lag in individual assistance processing. When survivors register for FEMA assistance, that registration feeds into the National Emergency Management Information System (NEMIS). NEMIS was not designed with real-time interoperability in mind. State systems, county systems, voluntary agency case management platforms, and FEMA’s own inspector scheduling tools operated on update cycles that created multi-day lags in case status visibility.
In practice, this meant disaster survivor assistance teams in the field were often operating on stale data. A survivor who had already received an inspection might get a second visit. A household that needed an expedited review for life-safety reasons might not be prioritized because the urgency flag hadn’t propagated across systems.
For public assistance — the program that pays local governments and nonprofits for disaster-related costs — the problem was different but equally disruptive. Project documentation, damage assessments, and obligated funding records sat in multiple systems with inconsistent identifiers. Program delivery staff spent significant time reconciling records rather than moving applications forward.
Why This Keeps Happening
The honest answer is that emergency management data infrastructure is chronically underfunded relative to the scale of modern disaster operations. FEMA’s core operational systems are decades old. Modernization efforts have been slow, politically difficult, and chronically under-resourced.
But the problem goes beyond FEMA. The data landscape in a major disaster involves dozens of actors: state emergency management agencies, county offices of emergency services, voluntary organizations active in disasters (VOADs), the Small Business Administration, HUD, state housing finance agencies, utility companies, and the private sector. None of these operate on compatible systems. Most don’t have real-time data sharing agreements even when the technology to enable it exists.
When a Category 4 hurricane hits a region still recovering from a previous storm, you don’t get a clean dataset. You get overlapping registrations, conflicting damage assessments, applicants whose addresses no longer exist, and a manual reconciliation burden that scales with every complicating factor.
What a Data Overhaul Actually Requires
There is no shortage of technology that could address these problems. The barriers are mostly policy, procurement, and institutional inertia.
Unified survivor identity resolution: Across multiple disaster registrations, FEMA needs a reliable way to link individuals and households across events without requiring survivors to re-prove their identity repeatedly. This is a solvable identity management problem. The technology exists. The implementation requires sustained commitment to a platform that spans disaster cycles rather than being rebuilt event-by-event.
Real-time interoperability between state and federal systems: Several states have made genuine progress on modernizing their emergency management platforms. The gap is in the federal-state data exchange layer. FEMA needs API-based integration standards — not file transfers on 24-hour cycles — for case status, eligibility determinations, and benefit delivery confirmation.
Field data capture that doesn’t depend on connectivity: Disaster areas frequently have degraded telecommunications infrastructure in the immediate aftermath of an event. Field teams need offline-capable data collection tools that sync when connectivity is restored, rather than paper-and-manual-entry workflows that create transcription errors and delays.
Damage assessment data standardization: Individual inspections, remote sensing data, and community-reported damage information currently live in different formats with different schema. A common damage data standard — something analogous to what the open data community has been pushing for years — would allow faster aggregation and more accurate prioritization of assistance.
Predictive resource positioning: The technology exists to use pre-event data — housing stock, population demographics, historical damage patterns, infrastructure vulnerability — to pre-position disaster response resources more effectively. FEMA and state agencies have been slow to operationalize this capability at scale.
The Policy Window
The 119th Congress has several pending bills related to FEMA modernization and disaster data. The political dynamics of disaster response — bipartisan, constituent-visible, and regularly in the news cycle — create at least some opportunity for meaningful legislative action.
More immediately actionable is the IA and PA program data work that can happen within existing FEMA authority. The agency doesn’t need new legislation to standardize its internal data formats, improve its inspector scheduling algorithm, or publish API specifications for state integration.
What it needs is sustained executive attention and budget — neither of which has been consistently available during the political turbulence of the past few years.
The Stakes
The 2024-2025 storm season will not be the last time the United States faces back-to-back catastrophic events with overlapping recovery timelines. Climate trends and population patterns in high-risk coastal and inland flood zones suggest this complexity will be the norm, not the exception.
The organizations that work in this space — state agencies, federal contractors, voluntary organizations, and technology providers — have a genuine opportunity to push for the infrastructure investments that would make future responses more effective. That push requires specificity about what needs to change, not just general calls for “modernization.”
Helene and Milton showed us the cost of data gaps at scale. The question is whether the emergency management community has the institutional will to do something about it before the next event forces the issue again.