Emergency Response Plan: Build & Test

Emergency Response Planning: How to Build and Test Your ERP

An emergency response plan (ERP) is the difference between a controlled evacuation and a fatal stampede, between a contained chemical spill and an environmental disaster, between a near-miss and a headline. OSHA requires emergency action plans under 29 CFR 1910.38 for workplaces covered by specific standards and the General Duty Clause creates a broader obligation for any employer facing foreseeable emergency scenarios. In Canada, every province mandates emergency preparedness under its occupational health and safety legislation - Ontario's O. Reg. 213/91 (Section 17), WorkSafeBC's OHS Regulation Part 4.13-4.18, and Alberta's OHS Code Part 7 all require documented emergency response procedures. Internationally, ISO 45001 Clause 8.2 mandates emergency preparedness and response planning as a core element of any OHS management system. Here is how to build an ERP that actually works.

What Must an Emergency Response Plan Cover?

The scope of your ERP depends on the hazards present at your workplace, but every plan must address a set of core emergency scenarios. At minimum, regulators expect you to plan for:

• Fire and explosion
• Medical emergencies (cardiac events, severe injuries, allergic reactions)
• Natural disasters (earthquakes, tornadoes, floods, severe weather) applicable to your region
• Hazardous material releases (chemical spills, gas leaks, biological exposure)
• Structural failure or collapse
• Active threat / workplace violence
• Utility failure (power outage, water main break, ventilation failure)
• Bomb threat or suspicious package

Not every scenario applies to every workplace. A three-person accounting office and a refinery will have very different ERPs. The key is that you have assessed the foreseeable emergencies and addressed each relevant one in writing.

OSHA Emergency Action Plan Requirements (29 CFR 1910.38)

OSHA's Emergency Action Plan standard requires the following elements:

1. Procedures for reporting a fire or other emergency.
2. Procedures for emergency evacuation, including type of evacuation and exit route assignments.
3. Procedures for workers who remain to operate critical plant operations before evacuating.
4. Procedures to account for all employees after evacuation has been completed.
5. Procedures for employees performing rescue or medical duties.
6. Names or job titles of contacts for further information about the plan.

The plan must be in writing if the employer has 11 or more employees. Employers with 10 or fewer may communicate the plan orally. Regardless of size, every employee must be trained on the plan when it is first developed, when their responsibilities change and when the plan itself changes.

Canadian Requirements

Canadian provinces require emergency response plans with variations in specificity:

• British Columbia (WorkSafeBC Part 4.13-4.18): Written emergency procedures must cover rescue, evacuation, first aid and fire response. Employers must designate wardens, post evacuation routes and conduct regular drills.
• Ontario (O. Reg. 213/91, OHSA): Construction projects require written emergency procedures including procedures for rescue from heights, excavation emergencies and confined space emergencies. General workplaces must have fire safety plans under the Ontario Fire Code.
• Alberta (OHS Code Part 7): Employers must establish emergency response plans proportional to the hazards. Plans must include procedures for rescue, first aid, fire suppression and hazardous material response.
• Federal (Canada Labour Code, Part II): Federally regulated employers must develop emergency procedures that are reviewed at least annually.

Step-by-Step: Building Your Emergency Response Plan

Step 1: Conduct a Hazard and Vulnerability Assessment

Before you can plan for emergencies, you need to know which emergencies are realistically possible at your workplace. A hazard and vulnerability assessment (HVA) evaluates:

• Probability: How likely is this event? (Consider geographic location, industry, building type and operational processes.)
• Severity: What is the worst-case impact on people, property and operations?
• Preparedness: What existing controls, equipment and training are already in place?

Score each scenario and prioritize your planning effort accordingly. A chemical manufacturing plant will rank hazardous material releases high; a high-rise office will prioritize fire and earthquake. Document your assessment - regulators want to see the rationale behind your plan's scope.

Step 2: Establish the Chain of Command

Emergencies create chaos. A clear chain of command reduces it. Define:

• Incident Commander (IC): The person with overall authority during an emergency. Typically the site manager or highest-ranking person present.
• Emergency Coordinator: Manages the tactical response (evacuation, communication with emergency services, headcount).
• Floor/Area Wardens: Responsible for sweeping their assigned zones, ensuring all personnel evacuate and reporting to the assembly point.
• First Aid Responders: Designated employees trained in first aid, CPR and AED use.
• Communication Lead: Handles calls to 911/emergency services, manages internal communication and contacts families if needed.

Identify backups for every role. The Incident Commander may be on vacation when the emergency occurs. If your plan depends on one person, your plan has a single point of failure.

Step 3: Map Evacuation Routes and Assembly Points

Evacuation maps should be posted at every exit, stairwell and common area. Each map must show:

• Primary and secondary evacuation routes
• Location of exits, fire extinguishers, first aid kits, AEDs, fire alarm pull stations and spill kits
• Assembly point locations (at least 150 feet from the building, away from fire department access routes)
• Shelter-in-place locations for weather emergencies or external hazardous material releases

For multi-story buildings, stairwell assignments prevent congestion. For large industrial sites, evacuation may require designated vehicle routes to transport workers from remote areas.

Step 4: Develop Scenario-Specific Procedures

Write clear, step-by-step procedures for each emergency type identified in your HVA. Each procedure should answer five questions:

1. What triggers this procedure? (Alarm sounds, verbal alert, specific conditions observed.)
2. Who does what? (Specific actions by the IC, wardens, first aid team and general employees.)
3. Where do people go? (Evacuate, shelter in place, or relocate to a specific area.)
4. How is accountability confirmed? (Headcount procedures at the assembly point.)
5. When is the "all clear" given? (Who has the authority to allow re-entry and what conditions must be met.)

Store these procedures where everyone can access them. A centralized document management platform ensures workers can pull up procedures on their phones during an actual emergency - not just during a planned drill.

Step 5: Equip Your Workplace

Your plan is only as good as the equipment supporting it. Ensure you have:

• Functional fire alarm and notification systems (tested per NFPA 72)
• Fire extinguishers inspected monthly and serviced annually (OSHA 29 CFR 1910.157)
• First aid kits stocked per ANSI Z308.1 or your provincial standard
• AEDs in accessible locations (if required or recommended for your workforce size)
• Spill containment kits for hazardous materials
• Emergency lighting and exit signage compliant with NFPA 101 Life Safety Code
• Communication systems - bullhorns, two-way radios, PA systems - that work when power is out

Step 6: Train Everyone - Not Just the Emergency Team

Every employee must know the basics: how to report an emergency, where to go during an evacuation and where the assembly point is. Beyond that, role-specific training is essential:

• Floor wardens: Sweep procedures, headcount methods, working with mobility-impaired employees.
• First aid responders: Current first aid and CPR certification, AED operation and bleeding control.
• Hazmat responders: Awareness, operations, or technician level per OSHA 29 CFR 1910.120 (HAZWOPER).
• Incident Commanders: Decision-making under pressure, communication with emergency services, Incident Command System (ICS) basics.

Use toolbox talks to reinforce emergency procedures between formal training sessions. A five-minute refresher on assembly point locations or fire extinguisher operation keeps the knowledge fresh without pulling workers off the job for hours.

Testing Your ERP: The Drill Program

A plan that has never been tested is a plan that will fail. Period. Build a drill program with escalating complexity:

Tabletop Exercises (Quarterly)

Gather the emergency response team around a table and walk through a scenario verbally. "It's 2:00 PM on a Tuesday. A forklift punctures a drum of solvent in Warehouse B. What happens next?" Tabletop exercises expose gaps in communication, decision-making and procedural clarity without disrupting operations.

Functional Drills (Semi-Annually)

Test specific components of the plan in real conditions. An evacuation drill tests whether workers can clear the building within the target time. A first aid drill tests response time and equipment readiness. A communication drill tests whether the notification chain works. Time everything. Measure everything.

Full-Scale Exercises (Annually)

Simulate a realistic emergency involving all elements: activation, evacuation, communication, first aid and interaction with simulated emergency services. Full-scale exercises are resource-intensive but reveal the integration failures that simpler drills miss.

Post-Drill Evaluation

Every drill must end with a debrief - a structured review of what worked, what did not and what must change. Document the findings and assign corrective actions with deadlines. Track them through your incident reporting system just as you would a real event. The debrief is where the drill's value is captured; without it, you have just disrupted a workday for no lasting benefit.

Common ERP Failures

After reviewing hundreds of emergency response plans, certain weaknesses appear repeatedly:

• No headcount procedure. If you cannot confirm that every person has been accounted for within minutes of an evacuation, firefighters may enter a burning building to search for someone who is already safely at the assembly point - or, worse, they may not search for someone who is still inside.
• Outdated contact lists. Phone numbers change. People leave the company. Review your emergency contact list monthly.
• No plan for after-hours emergencies. If the emergency happens at 3:00 AM with a skeleton crew, does your plan still work?
• Ignoring contractors and visitors. Your headcount procedure must account for everyone on site, not just full-time employees.
• Shelter-in-place gaps. Most plans focus exclusively on evacuation. But for tornadoes, active threats, or external chemical releases, evacuation can be the wrong move.

Centralize Your Emergency Preparedness With Make Safety Easy

Managing an ERP across multiple sites, shifts and teams demands more than a binder on a shelf. Make Safety Easy provides cloud-based document management so every worker can access emergency procedures from any device, toolbox talk templates for emergency preparedness topics, and incident reporting tools that double as post-drill evaluation forms. Your emergency plan stays current, accessible and continuously tested.

The best time to build your emergency response plan was before the last emergency. The second-best time is now. Book a demo to see how Make Safety Easy keeps your team prepared, or explore pricing to start building your program today.