Safeguard Signal

How to Create an Emergency Response Team

An emergency response team is a small set of named roles, not a title on an org chart. Design it so that on any day, at any hour, a trained person answers the phone.

Published: July 19, 2026Last reviewed: July 19, 2026~11 min read

Different organizations use different labels - Emergency Response Team (ERT), Incident Response Team, Crisis Management Team - but the underlying design problem is the same. You need a group that can be called, that has the authority to act, and that has thought through what "act" means before the event. This guide describes the roles, the coverage model, and the documentation that make an ERT actually work. It does not prescribe a single structure; industry, size, geography, and regulatory context all change the right answer.

The Command Structure

Most modern emergency response draws on the Incident Command System (ICS) framework maintained by FEMA under the National Incident Management System (NIMS). Even organizations that never file a FEMA form benefit from ICS's core idea: separate the person running the incident from the people running the functions, and keep spans of control small enough that a single person can direct the roles reporting to them.

A common starting structure

Incident Commander at the top. Directly reporting: Communications, Operations, Employee Accountability, Facilities, IT, HR, and External Liaison. Executive Sponsor supports from the side rather than from the top of the response chart.

Roles That Make the Team

The list below is a starting palette. Combine or split roles based on your size, and always assign a primary and a documented backup for each.

Incident Commander

Owns the response. Sets objectives, approves major actions, and decides when to escalate or stand down. Trained in ICS 100/200 at minimum. Not necessarily the most senior executive in the building - usually the person best equipped to run a fast-moving operation.

Communications Lead

Owns internal and external messaging. Activates the notification system, chooses the right template, coordinates with executive communications, and manages message cadence. Holds the pen on all-clear and status messages.

Employee Accountability Lead

Confirms the status of every person on site or expected on site. Owns the muster process, contractor and visitor accountability, and the missing-person escalation path. Reports headcount to the Incident Commander at defined intervals.

Facilities Lead

Manages the physical environment: utilities, doors, HVAC, elevators, fire systems, and building access. Coordinates with landlords, security vendors, and mutual-aid partners as needed.

IT Lead

Keeps critical technology available (or safely down). Manages cyber-incident response, coordinates with the security operations function, and supports the Communications Lead when notification systems depend on IT infrastructure.

HR Lead

Handles injury reporting, employee support, family notification, and coordination with employee assistance programs. Works closely with legal on any events involving injuries, fatalities, or workplace violence.

Executive Sponsor

Provides authority, unblocks resources, and briefs the board or ownership. Rarely runs the response, but is on-call throughout it. Approves reputational and financial messaging.

External Liaison

Single point of contact for fire, law enforcement, EMS, public health, emergency management, and (where relevant) environmental regulators. Maintains standing relationships before an event, so introductions are not happening at 3 a.m.

Coverage and Succession

A role that is only staffed during business hours is not staffed. Coverage means an on-call rotation for each role, published somewhere the activator can find it in under a minute, and confirmed at shift change and holidays. Succession means every primary has a documented backup who has been trained on the role, not just told they hold it.

The turnover test

If one person left the organization tomorrow, would any ERT role be uncovered? If the answer is yes for any role, the succession plan is incomplete regardless of how good the primary is.

Decision Authority

Document, in advance and in writing, which decisions each role can make alone, which require the Incident Commander, and which require the Executive Sponsor. Life-safety decisions belong to the on-scene commander. Reputational, financial, and legal decisions belong further up. Ambiguity here is what causes ten-minute pauses during real events.

Contact Rosters

The roster is a living document. A workable pattern:

  • One roster per role, showing primary and backup with 24×7 numbers.
  • Updated whenever a person joins, leaves, or changes numbers - with a maximum staleness of one calendar quarter.
  • Distributed both electronically and on paper. Paper matters when the network is what failed.
  • Included in every activation exercise, so gaps surface in a drill rather than a real event.

Training and Exercises

FEMA's independent-study courses (IS-100, IS-200, IS-700, IS-800) are free and well-suited to onboarding new ERT members. Beyond ICS fundamentals, ERT members benefit from tabletop exercises against scenarios drawn from their own hazard assessment, plus a periodic no-notice activation to test on-call responsiveness.

ERT Documentation Checklist

  • Named Incident Commander with primary and backup, 24×7
  • Every functional role staffed with primary and documented backup
  • Decision-authority matrix reviewed and signed by executive sponsor
  • Current on-call roster distributed electronically and on paper
  • Training records for each ERT member with course and date
  • Standing relationships with local fire, law enforcement, EMS, and emergency management
  • Annual tabletop exercise scheduled and completed
  • Turnover review at least quarterly with backups actually trained on the role

How Safeguard Signal Fits

Once the ERT is designed, the notification system becomes the mechanism they use to reach the rest of the workforce. Safeguard Signal's targeted groups map naturally to ERT structure - you can activate the ERT itself as a group, page a specific site's floor wardens, or send an organization-wide notice from a mobile device when the commander is not at a desk. Delivery analytics and per-recipient acknowledgement give the Employee Accountability Lead a real-time picture of who is safe, without having to build it manually.

Related Guides

Authoritative Sources

  1. FEMA - National Incident Management System (NIMS) and Incident Command System (ICS) Resource Center (fema.gov/nims)
  2. FEMA Emergency Management Institute - Independent Study courses IS-100, IS-200, IS-700, IS-800 (training.fema.gov/is)
  3. OSHA - Evacuation Plans and Procedures eTool (osha.gov)
  4. U.S. Department of Homeland Security / CISA - Active Shooter Preparedness resources (cisa.gov)
  5. Ready.gov - Crisis Communications Plan guidance (ready.gov/business)

Frequently Asked Questions

How large should an emergency response team be?

Small enough to make decisions quickly and large enough to cover every essential function around the clock. Many organizations start with six to twelve named roles, each with a primary and a backup.

Should the incident commander always be an executive?

No. The incident commander is the person best trained and positioned to run the response - often an operations, safety, or security leader. Executives typically support and approve, not command.

Do small organizations need a formal team?

Yes, though the structure is proportionally smaller. Even three or four named roles with documented backups outperform an ad-hoc response.

How do we handle 24×7 coverage?

Rotate on-call for each role, publish a current on-call roster, and confirm the roster during shift changes and holidays.

What is succession planning for the ERT?

Documented backups for every role, cross-training between adjacent roles, and a periodic review that removes people who have left and adds replacements before there is a gap.

How does the ERT coordinate with external agencies?

Through a designated liaison role that maintains standing relationships with fire, law enforcement, EMS, emergency management, and, where relevant, environmental regulators.

These resources provide general planning information and are not a substitute for guidance from emergency management professionals, legal counsel, regulatory authorities, law enforcement, fire services, medical professionals, hazardous-material specialists, or other appropriate public-safety agencies. Organizations should adapt their plans to their facilities, workforce, risks, applicable laws, and local emergency procedures.