Emergency Communications Interoperability — 6 U.S.C. §§ 571-579

6 U.S.C. Subchapter XIII (§§ 571-579) establishes the federal framework for ensuring that police, fire, emergency medical services, and other first responders can communicate with each other across jurisdictional and technological boundaries during emergencies. The core problem the statute addresses is a long-standing failure of public safety communications: during major incidents — from the September 11 attacks to Hurricane Katrina — first responders from different agencies and jurisdictions often could not communicate because their radio systems used incompatible frequencies, protocols, or encryption standards. Congress responded by creating a dedicated Emergency Communications Division inside what is now the Cybersecurity and Infrastructure Security Agency (CISA), mandating a National Emergency Communications Plan (NECP), establishing Regional Emergency Communications Coordination (RECC) Working Groups in each of FEMA's ten regions, and funding the Interoperable Emergency Communications Grant Program to help states and localities upgrade their systems. The grant program is the primary federal mechanism for pushing interoperability improvements to the state, local, tribal, and territorial (SLTT) level.

Current Law (2026)

Emergency Communications Division — § 571

Section 571 creates the Emergency Communications Division within CISA (previously within the Office of Emergency Communications before CISA's 2018 reorganization). The Division is the organizational home for all of the federal government's emergency communications interoperability programs.

The Division's responsibilities include:

• Developing and implementing the National Emergency Communications Plan
• Coordinating federal grant programs for interoperable emergency communications (§ 574)
• Supporting Regional Emergency Communications Coordination Working Groups
• Developing voluntary technical standards for interoperable communications equipment
• Assisting SLTT entities with planning, training, and exercises for interoperable communications
• Coordinating with the FCC on spectrum allocation issues affecting public safety communications

National Emergency Communications Plan — § 572

Section 572 directs the Secretary of Homeland Security to develop and maintain a National Emergency Communications Plan (NECP). The NECP is the overarching strategic document for the nation's emergency communications posture. It must:

• Establish a national vision for interoperable and resilient emergency communications
• Set goals and milestones for achieving interoperability at the local, regional, and national levels
• Identify roles and responsibilities of federal, state, local, tribal, and territorial entities
• Provide recommendations for training and exercise programs
• Address communications in catastrophic events (major disasters, terrorist attacks, pandemic response)
• Be updated at least every five years

The NECP development process is collaborative — CISA convenes federal agencies (FCC, FEMA, DoD, DHS components), state and local public safety associations, and tribal governments.

Regional Emergency Communications Coordination — § 575

Section 575 creates Regional Emergency Communications Coordination (RECC) Working Groups aligned with FEMA's ten regional offices. Each RECC Working Group consists of representatives from:

• State emergency management agencies and state public safety agencies
• Local governments and first responder agencies in the region
• Federal agencies with emergency communications roles in the region
• Tribal nations and territorial governments as applicable

RECC Working Groups coordinate regional emergency communications planning and provide a regional forum for interoperability planning between the national NECP and individual state plans. They conduct regional assessments, support grant-funded projects, and serve as the coordination mechanism when major incidents cross state lines within a region.

Assessments and Reports — § 573

Every five years, the Secretary must assess:

• The status of nationwide emergency communications capabilities
• Progress toward achieving the goals and milestones set in the NECP
• Remaining gaps and barriers to interoperability at the SLTT level
• Federal program effectiveness

Reports go to the relevant congressional oversight committees.

Emergency Communications Preparedness Center — § 576

Section 576 creates the Emergency Communications Preparedness Center, operated jointly by DHS, the Department of Defense, the Department of Justice, and other participating federal agencies. The Center:

• Coordinates federal investment in emergency communications research, development, and testing
• Manages federal participation in RECC Working Groups
• Supports development of voluntary interoperability standards
• Coordinates federal spectrum policy affecting public safety bands

High-Risk Urban Areas — § 577

Section 577 directs the Secretary to work specifically with the FCC Chairman, the Secretary of Defense, and state and local officials to assess and improve emergency communications capabilities in high-risk urban areas — cities and regions identified as significant terrorist targets or with particularly complex communications environments (multiple jurisdictions, transit systems, major events). This provision responds to lessons from 9/11, where New York City's communications complexity contributed to coordination failures.

Interoperable Emergency Communications Grant Program — § 579

Section 579 authorizes federal grants to states for projects that improve interoperable emergency communications for first responders. Grants flow through states to local jurisdictions, with matching requirements. Eligible uses include:

• Equipment upgrades (radios, dispatch systems, mobile data terminals)
• Shared channel agreements and frequency coordination
• Technical standards implementation
• Training and exercises for interoperable communications
• Planning and governance support

Grant conditions require that projects align with the state's Statewide Communication Interoperability Plan (SCIP) — state plans developed under CISA guidance that translate the NECP into state-specific strategies.

Coordination of Grant Programs — § 574

Section 574 requires CISA to coordinate the interoperable emergency communications grant programs with other DHS grant programs — particularly Homeland Security Grant Program (HSGP) funds that states may also use for communications. The goal is to prevent duplication and ensure that all DHS grant conditions on communications equipment are consistent.

How It Affects You

If you work in public safety (police, fire, EMS): Federal interoperability grants — funded through CISA under 6 U.S.C. § 579 — are the primary source of federal dollars for radio system upgrades, Next Generation 911 implementation, and FirstNet adoption. Your agency's path to those dollars runs through your state's Statewide Communication Interoperability Plan (SCIP) and your region's Regional Emergency Communications Coordination (RECC) Working Group. If your agency has been waiting years for a radio system upgrade, the SCIP and RECC processes are where decisions about prioritization and funding allocation actually happen — and the agencies that show up and participate in those planning processes are the ones that get funded. FirstNet — the national LTE broadband network built on AT&T's infrastructure specifically for public safety — is now operational in all 50 states and provides a data layer on top of narrowband radio. If your department has been slow to adopt FirstNet devices, check with your state's FirstNet point of contact (typically at the state public safety agency) about available equipment subsidies and transition timelines. Contact CISA's Emergency Communications Division at cisa.gov/emergency-communications for technical assistance requests; they can send assessors to help your agency benchmark against the NECP milestones.

If you are a state emergency management director or SWIC: Your state's Statewide Interoperability Coordinator (SWIC) role is the linchpin of federal-local emergency communications coordination — and CISA conducts regular state capability assessments against the National Emergency Communications Plan (NECP) milestones that your SCIP commitments drive. Demonstrated SCIP progress directly affects DHS grant eligibility; states that can show measurable advancement toward NECP benchmarks are better positioned in competitive grant cycles. CISA's Emergency Communications Preparedness Center (ECPC) at cisa.gov/resources-tools/groups/ecpc coordinates across 19 federal departments and agencies on emergency communications preparedness — if you're trying to build federal interoperability into your state exercises, ECPC is the right entry point. The SWIC community also shares best practices through the National Council of Statewide Interoperability Coordinators (NCSWIC) at cisa.gov/groups/ncswic.

If you are a communications equipment vendor or systems integrator: The federal public safety communications market is driven by two standards with different enforcement mechanisms. P25 (Project 25) — the interoperability standard for digital land mobile radio — is effectively mandatory for grant-funded equipment purchases; CISA's Compliance Assessment Program (CAP) at cisa.gov/safecomm tests and certifies P25 equipment, and agencies buying CAP-uncertified equipment risk losing grant eligibility. Next Generation 911 (NG911) standards — developed by NENA, APCO, and others — govern the shift from analog PSAP infrastructure to IP-based emergency call handling; NG911 is an active migration market with federal funding flowing through CISA and NHTSA. Vendors who understand the SCIP-driven procurement cycle — including how states allocate grant funds across their regions — are better positioned to win public safety contracts. The Association of Public-Safety Communications Officials (APCO) at apcointl.org and the National Emergency Number Association (NENA) at nena.org are the primary industry bodies shaping standards and procurement guidance in this space.

If you represent a tribal nation: Tribal governments are specifically included in the NECP's interoperability framework as SLTT (State, Local, Tribal, Territorial) stakeholders. You can participate in RECC Working Groups either directly or through your state's SWIC — and tribal emergency communications needs are addressed in both the NECP and CISA's tribal consultation processes. On the funding side, tribal governments may apply for interoperability grant funds through their state's HSGP allocation or, in some cases, directly through tribal-specific set-asides. Tribal lands often have coverage gaps in both commercial LTE and FirstNet infrastructure; FirstNet has active tribal outreach programs, and FirstNet Authority (firstnet.gov) coordinates with the tribal government consultation process separately from state deployments. CISA's Tribal Nations Communications Guide — available at cisa.gov/topics/tribal-resources — outlines tribal-specific resources and how to engage with CISA directly. The National Congress of American Indians (NCAI) also tracks federal emergency communications policy affecting Indian Country.

Implementing Regulations

• 47 CFR Part 400 — 911 Grant Program: the FCC rules establishing the federal grant program for 911 infrastructure authorized by the ENHANCE 911 Act of 2004 and Next Generation 911 Advancement Act, administered by the FCC's Integrated Communications Office (ICO):

  • § 400.3 — Who may apply: grants are available to States and Tribal Organizations (not directly to PSAPs or local governments); states and tribes apply on behalf of their 911 systems; each state applicant must designate a 911 Coordinator — a single officer or body responsible for statewide 911 coordination
  • § 400.4 — Application requirements: a state application must include a State 911 Plan describing proposed projects and activities for implementing 911, E-911, and Next Generation 911 services; documenting how NG911 will be deployed and migrated from legacy systems; certifying that the state is not diverting 911 fees to non-911 purposes (the "fee diversion" problem, where states redirect 911 surcharges from consumers to general fund purposes); and certifying compliance with 911 transition and accessibility requirements
  • § 400.6 — Grant distribution formula: 50% of available grant funds are allocated proportionally to state population; 50% are allocated based on the number of counties or equivalent units in each state; this formula directs resources toward both high-population states and states with many distinct local jurisdictions that must coordinate their 911 systems; tribal organizations receive a separate set-aside
  • § 400.7 — Eligible uses: grant funds may be used for implementation and operation of 911 services, E-911 services, and Next Generation 911; migration to IP-enabled emergency networks; adoption and operation of NG911 services and applications; training public safety personnel in NG911 operations; and public education about 911 services; funds may not be used for general state or local operating expenses, non-911 communications equipment, or any purpose unrelated to 911 service delivery
  • § 400.8 — Continuing compliance certification: grant recipients must submit annual certifications confirming they are not diverting 911 surcharge revenues to non-911 purposes; fee diversion — collecting 911 surcharges from telephone subscribers but using the money for general government purposes — is a persistent problem that the grant program targets; states that cannot certify non-diversion lose access to grant funds
  • § 400.9 — Financial and administrative requirements: grants are subject to 2 CFR Part 200 (Uniform Administrative Requirements) — the standard federal grant management framework covering procurement, cost principles, audit requirements, and closeout

  The FCC 911 grant program is one of several federal funding streams for 911 infrastructure alongside NHTSA's 911 grants and CISA's interoperability grants. The program's fee diversion certification requirement addresses a long-standing problem identified by the FCC in its annual 911 fee diversion reports: states have at times redirected hundreds of millions of dollars in 911 surcharges (charged on consumers' phone bills) to cover general budget gaps, leaving 911 systems underfunded. The annual certification creates a transparency mechanism and grant-funding incentive for states to properly earmark 911 revenue. Recent rulemaking: 83 FR 38059 (August 2018) — updated program requirements and fee diversion certification procedures.

State Variations

Emergency communications interoperability is primarily a state and local function, with federal grants and standards playing a supporting role:

• Every state has a designated Statewide Interoperability Coordinator (SWIC) — typically housed in the state emergency management agency or state police — responsible for the SCIP and for coordinating with CISA
• State radio systems vary significantly: some states have built statewide shared systems (e.g., Minnesota ARMER, North Carolina VIPER); others rely on county-by-county systems with interoperability patches
• FirstNet (the national public safety broadband network built on AT&T's network) now overlays the narrowband radio interoperability framework; CISA coordinates with FirstNet Authority on integration

Recent Developments

The emergency communications interoperability framework has evolved through several iterations of the NECP (published in 2008, 2014, and 2019, with the 2024 update in development). Key recent trends:

• FirstNet adoption — the nationwide public safety LTE network has shifted federal investment toward broadband alongside narrowband P25, requiring updates to interoperability frameworks
• NG911 transition — migration from legacy 911 systems to Next Generation 911 (IP-based) intersects with interoperability grant programs; CISA now coordinates NG911 policy with FCC and NHTSA
• Cyber-physical convergence — as public safety communications migrate to IP networks, cybersecurity becomes an interoperability concern; CISA's role managing both cyber and communications security has increased this coordination
• COVID-19 exposed gaps in interoperability between public health agencies and traditional first responders during large-scale public health emergencies; the 2024 NECP update addresses public health communications integration