FEMA Disaster Monitoring for Events

Canonical URL: https://signalguard.live/docs/signals/disasters Meta description: SignalGuard surfaces active FEMA disaster declarations for the venue's state via the OpenFEMA API — Major Disaster (DR), Emergency (EM), and Fire Management (FM) declarations that affect event continuity, ingress, and insurance posture.

What this signal monitors

The Disasters signal pulls all currently-active federal disaster declarations covering the venue's state from FEMA's OpenFEMA Disaster Declarations Summaries dataset. A declaration is "active" if its incidentEndDate is in the future or absent (open-ended). SignalGuard distinguishes three declaration types — Major Disaster (DR), Emergency (EM), and Fire Management Assistance (FM) — and groups multiple county-level rows for the same incident under a single disasterNumber so a single hurricane affecting 30 counties shows up once with countiesCount: 30, not 30 duplicated cards.

Data sources

• Primary: OpenFEMA v2 — https://www.fema.gov/api/open/v2/DisasterDeclarationsSummaries with OData-style filtering on state and ordering by declarationDate desc. Free, no API key, well-documented at https://www.fema.gov/openfema-data-page/disaster-declarations-summaries-v2.
• Geocoding: OpenStreetMap Nominatim for venue → state code (2-letter state field is what FEMA expects).
• Query window: top 100 most-recent declarations per state, filtered client-side to isActive.
• Cache TTL: 30 minutes. FEMA declarations don't churn on minute boundaries.

How SignalGuard scores severity

Per-declaration severity:

• DR (Major Disaster) → critical — the highest federal declaration tier; triggers Stafford Act assistance
• EM (Emergency) → high — pre-event or supplemental emergency aid
• FM (Fire Management Assistance) → medium — wildfire response support
• Anything else → medium by default

Overall threat level is the max severity across active declarations, with one escalation rule: three or more active declarations in the same state pushes the rollup to at least high regardless of individual severities. Multiple concurrent emergencies indicate a stressed regional response capacity, which matters for event continuity planning.

Use cases for event security

1. DR overlapping event date → activate continuity plan. A Major Disaster Declaration covering the venue's state means federal aid is flowing for a specific incident — hurricane, flood, wildfire, severe storm. Even if the venue itself wasn't impacted, regional resources (police, EMS, hospitals) are stretched. SignalGuard surfaces the declaration so operations can pre-stage their own private medical, security, and transport rather than relying on the local mutual-aid pool.
2. Three concurrent declarations → coordinate with state EOC. When the rollup hits high because of declaration count rather than severity, that's the signal to make sure the event has a direct line to the state emergency operations center. Multiple concurrent declarations mean the state is operating in elevated posture and may have already pre-positioned assets that affect your ingress routes or air operations.
3. Active FM declaration upwind of venue → re-check air quality plan. Fire Management declarations are wildfire-specific. Even when the fire itself is hundreds of miles away, smoke transport can degrade air quality at the venue within 24 hours. SignalGuard's disasters card flags active FM declarations so event organizers can have the AQI / N95 / cancellation conversation in advance rather than at gate-open.

Pairs well with

• Weather signal — current and forecast conditions at the venue
• Air quality signal — wildfire smoke transport from active FM declarations
• News signal — local reporting on declared incidents

Premium upgrade path

OpenFEMA is free and fully open. Where premium adds value:

• Everbridge CEM — fuse FEMA declarations with internal asset location data and automate evacuation / shelter-in-place playbooks (link: /integrations)
• PredictHQ Severe Weather — predictive overlays that often precede formal FEMA declarations by 24–72 hours
• NC4 Mission Mode — enterprise crisis-management workflow on top of FEMA + private feeds
• Veraset / Placer.ai — mobility data showing how populations are actually shifting during a declared incident

FAQ

What's the difference between a DR and an EM declaration? A Major Disaster Declaration (DR) is the highest tier under the Stafford Act and unlocks the broadest federal assistance — Individual Assistance, Public Assistance, and Hazard Mitigation. An Emergency Declaration (EM) is faster and broader-purpose but more limited in dollar amount; it's often issued in advance of an expected impact (e.g., before hurricane landfall). FEMA's own program background lives at https://www.fema.gov/disaster/how-declared.

Why does SignalGuard group multiple counties under one disasterNumber? FEMA issues county-level rows for the same incident — Hurricane Helene, for example, produced separate declaration records for each affected county. From an event-security standpoint that's a single incident, so the UI rolls them up with a countiesCount field rather than showing 30 cards for the same storm.

What if the declaration covers a different part of the state than my venue? SignalGuard reports declarations at state granularity because that's what OpenFEMA filters by. The county list per declaration is available in the raw record. For venue-precise impact filtering, integrate OpenFEMA's FEMA Web Disaster Summaries (FemaWebDisasterSummaries) endpoint with the venue's FIPS code — on the roadmap.

How quickly does FEMA publish a new declaration? DR and EM declarations are typically published within hours of the President's signature. The OpenFEMA dataset itself refreshes at least daily. SignalGuard's 30-minute cache means worst-case staleness is half an hour.

Can SignalGuard alert me when a new declaration drops? Push alerts on declaration creation are a paid tier feature — see /integrations for the Everbridge / Dataminr / NC4 workflows that handle this.