The 2025 Emergency Notification
Readiness Report
Primary research across 412 jurisdictions. Latency benchmarks, compliance gap analysis, and channel-reach data your budget presentation actually needs.
Jurisdictions Surveyed
412
Data Collection Window
Q2–Q4 2024
Agency Types
5 categories
Report Pages
84 pp.
Section 01
Key Findings
Alert Latency Benchmark
Median dispatch-to-delivery across legacy systems
Legacy CAD-integrated systems average 47 seconds from dispatch authorization to first device receipt. AlertDispatch-class platforms benchmark at 9–13 seconds. The 34-second gap is the difference between shelter-in-place compliance and open-door exposure.
IPAWS Compliance Gap
Of surveyed agencies have at least one critical compliance gap
Of 412 surveyed agencies, 61% had at least one critical IPAWS compliance deficiency — most commonly in monthly CAP message validation (38%), WEA geo-targeting accuracy (29%), and EAS encoder firmware currency (24%). Only 14% passed all three audit categories.
Channel Reach Statistics
Average active channels per jurisdiction during major incidents
Jurisdictions using integrated platforms activated an average of 7.8 channels simultaneously (WEA, EAS, email, SMS, outdoor sirens, digital signage, PA integration). Single-vendor legacy systems averaged 3.2. Each additional channel adds an estimated 11% population reach.
How to read these numbers: The latency benchmark reflects time from authorized dispatch to confirmed first-device receipt across all registered channels. Compliance gap percentages are self-reported and third-party-validated via FEMA IPAWS audit records where available (n=214). Channel reach is calculated on population census blocks with confirmed device registration or outdoor siren coverage zones.
Section 02
Methodology
Expand each subsection for full detail. Peer-reviewed; limitations disclosed in 2.3.
The survey sample was drawn from FEMA's National Emergency Management Association (NEMA) member directory, supplemented by IPAWS-registered agency lists current as of Q1 2024. Stratification ensured proportional representation across five population tiers:
Tier 1
< 25K
n=82
Tier 2
25K–100K
n=118
Tier 3
100K–500K
n=124
Tier 4
500K–1M
n=58
Tier 5
> 1M
n=30
Agency types covered: county emergency management (34%), municipal public safety (28%), higher education (18%), K-12 school districts (12%), and federal facility managers (8%). Response rate: 71% (412 of 580 contacted). Non-response bias analysis showed no statistically significant skew toward larger jurisdictions.
Data was collected through three independent channels to enable triangulation and reduce self-report bias — a known limitation in compliance-adjacent research:
- 01
Structured Agency Survey
84-item questionnaire covering system architecture, channel configuration, staff training hours, last drill date, and self-assessed compliance status. Administered online with a 30-day completion window (August–October 2024).
- 02
FEMA IPAWS Audit Records
Third-party-validated audit outcomes obtained under FOIA for 214 of 412 agencies. Used to cross-validate self-reported compliance status. Discordance rate: 23% (agencies reported compliant but audit-flagged).
- 03
Live Latency Probes
With agency consent (n=187), AlertDispatch Research conducted live test broadcasts using synthetic emergency messages across all registered channels. Delivery timestamps captured at device level via registered test receivers in each jurisdiction.
Findings were reviewed by Dr. Pamela Ortega-Ruiz (University of Colorado Emergency Management Program) and James Whitfield (former FEMA Region IV Administrator). Neither reviewer has a financial relationship with AlertDispatch.
Acknowledged Limitations
- —Self-selection bias: agencies that declined participation may systematically differ in compliance posture.
- —Latency probes used synthetic messages; real-incident latency may differ due to concurrent system load.
- —FOIA audit records were unavailable for 198 agencies; compliance analysis uses self-report for those jurisdictions.
- —Channel-reach calculation assumes uniform device distribution within census blocks.
IPAWS
Integrated Public Alert & Warning System — FEMA-administered infrastructure for WEA and EAS message routing.
WEA
Wireless Emergency Alerts — cell-broadcast messages delivered to mobile devices in a geographic area without opt-in.
EAS
Emergency Alert System — broadcast-based system covering radio, TV, and cable. Encoder/decoder firmware must be current per FCC §11.
CAP 1.2
Common Alerting Protocol — OASIS standard XML message format required by IPAWS. Non-compliant messages are rejected at the aggregator.
Dispatch-to-delivery
Time elapsed from authorized send action in origination platform to confirmed receipt timestamp on first registered device.
CPG 101 v3
FEMA Comprehensive Preparedness Guide — the planning framework used to define exercise frequency benchmarks in Section 3.
Section 04
Comparative Capability Framework
17 capabilities across 4 system archetypes. Filter by category.
| Capability | Legacy CAD | Basic Standalone | Integrated Platform | AlertDispatch |
|---|---|---|---|---|
WEA (Wireless Emergency Alerts) Channel | Partial | Yes | Yes | Yes |
EAS Broadcast Integration Channel | Yes | Partial | Yes | Yes |
Outdoor Siren Activation Channel | Yes | No | Partial | Yes |
Indoor PA / Mass Notification Channel | No | No | Partial | Yes |
Digital Signage Integration Channel | No | No | Partial | Yes |
Dispatch-to-Delivery < 15 sec Performance | No | Partial | Partial | Yes |
Simultaneous Multi-Jurisdiction Performance | No | No | Partial | Yes |
Geo-Targeted WEA (< 0.1 mi²) Performance | No | Partial | Yes | Yes |
IPAWS CAP 1.2 Compliance Compliance | Partial | Yes | Yes | Yes |
Automated Monthly CAP Validation Compliance | No | No | Partial | Yes |
EAS Encoder Firmware Monitoring Compliance | No | No | No | Yes |
Documented Failover Paths Resilience | No | Partial | Yes | Yes |
Cellular Fallback for PA Resilience | No | No | No | Yes |
Offline Dispatch Queue Resilience | No | No | Partial | Yes |
Single-Action Multi-Campus Dispatch Workflow | No | No | Partial | Yes |
Role-Based Dispatch Authorization Workflow | Partial | Yes | Yes | Yes |
Plain-Language Drill Mode Workflow | No | No | Partial | Yes |
"Partial" indicates capability exists but requires manual configuration, third-party add-on, or does not meet IPAWS compliance thresholds. Full methodology in Section 02.