A written emergency response plan only proves its worth in an actual emergency — and by then, it's too late to fix the gaps. Nearly 30% of workplaces still lack a written emergency action plan despite OSHA requirements, and many of the plans that do exist haven't been opened, tested, or updated in years. A plan that sits in a binder isn't a plan; it's a liability. Here are four concrete ways to close the gaps before an incident forces you to find them.
1. Audit Your Plan Against OSHA's Minimum Elements
Before anything else, confirm your plan actually meets the baseline. Under 29 CFR 1910.38 (general industry) or 1926.35 (construction), a compliant emergency action plan needs six elements: procedures for reporting a fire or other emergency, evacuation procedures and exit-route assignments, procedures for employees who stay behind to shut down critical operations, a way to account for everyone after evacuation, procedures for employees with rescue or medical duties, and the name or job title of anyone employees can contact for more information.
Employers with more than 10 employees must keep the plan in writing and accessible on-site — a shared drive folder no one has opened since onboarding doesn't satisfy that. When auditing, check three things specifically: whether the accountability procedure names a real method (a physical muster point and a person responsible for the headcount, not just "employees report to the parking lot"), whether contact information is current, and whether the plan reflects your actual facility layout, not a template that predates a renovation or a new shift schedule. Inaccurate contact information and outdated site details are among the most common pitfalls found in plan reviews, and they're also the easiest to fix.
If you manage plans across multiple sites, this is where a centralized EHS management platform earns its keep — it's much harder for a plan to go stale when updates and approvals are tracked in one system instead of scattered across site-level documents.
2. Replace Paper Reviews with Real Drills
Reading a plan is not the same as running it. A tabletop exercise like walking a team through a simulated scenario step by step surfaces the gaps a document review never will: the manager who's on vacation during the drill and has no backup, the exit route that's blocked by seasonal storage, the radio channel nobody remembers to switch to.
Annual tabletop exercises are the recommended minimum for most organizations, with higher-risk or more heavily regulated facilities running them semi-annually or quarterly. Facilities subject to chemical accident prevention rules have their own mandated cadence, so check whether your industry has a specific requirement layered on top of the general OSHA baseline. Beyond frequency, vary the scenario. A plan that's only ever been tested against a fire evacuation may fall apart during a chemical release, active threat, or severe weather event that calls for shelter-in-place instead of evacuation. Rotate scenarios year to year, and rotate who leads the drill — a plan that only works when one specific person is in the building isn't resilient.
3. Fix the Communication and Accountability Chain
When plans fail in a real emergency, the root cause is rarely the evacuation route — it's communication. As an incident intensifies, fewer people volunteer to step into a leadership role unless one has already been assigned, and information that isn't actively monitored and relayed stops flowing exactly when it matters most.
Two fixes address most of this. First, name leadership roles explicitly in the plan — not just "management" but specific titles with backups, so the chain of command survives someone being out of office. Second, build in two-way accountability, not just one-way alerts. A mass notification system that supports reply-based check-ins ("Reply 1 if safe, 2 if you need assistance") and rolls responses into a live dashboard lets you account for your workforce in minutes instead of manually calling down a roster. If your current system can only push a message out and can't confirm who received and understood it, you have a notification tool, not an accountability tool — and accountability is the part OSHA actually requires.
4. Put the Plan on a Review Cycle Tied to Change, Not the Calendar
An annual review is the floor, not the ceiling. Roughly three-quarters of manufacturing facilities only evaluate their emergency plans once a year, which means a new hire, a relocated production line, or a renovated exit corridor can go unaddressed for months. The fix is to trigger a plan review on specific events, not just a date on the calendar: a change in headcount or shift structure, a facility layout change, a new chemical or process brought on-site, a near-miss or actual incident, or turnover in a named emergency role.
Building this into your incident management or audit workflow means the review gets triggered automatically by the event that necessitates it, rather than depending on someone remembering to circle back. Pair that with a version history — who changed what, and when — so you can demonstrate to auditors and regulators that the plan is a living document, not a static file that happens to have last year's date on the cover.
The Bottom Line
A tight emergency response plan isn't the one with the most pages — it's the one that's accurate, tested, communicated, and current. Audit it against OSHA's six required elements, run realistic drills at least annually, close the communication and accountability gaps, and tie your review cycle to real organizational change instead of the calendar. Do those four things and the plan will actually do its job when it's needed.
Frequently Asked Questions
What are the OSHA-required elements of an emergency action plan?
Under 29 CFR 1910.38, a compliant plan must include procedures for reporting emergencies, evacuation procedures and exit-route assignments, procedures for employees who shut down critical operations before evacuating, a method to account for all employees after evacuation, procedures for employees with rescue or medical duties, and the name or job title of a contact for more information about the plan.
How often should you test or update an emergency response plan?
At minimum, run a tabletop exercise annually and review the plan whenever there's a major change — new hires, a facility layout change, new equipment or chemicals, or turnover in a named emergency role. Higher-risk or more heavily regulated facilities should test quarterly or semi-annually, and some regulated sectors have their own mandated exercise frequency.
What's the difference between an emergency action plan and an emergency response plan?
The terms are often used interchangeably, but "emergency action plan" (EAP) typically refers to the specific OSHA-regulated document covering evacuation and reporting procedures, while "emergency response plan" is sometimes used more broadly to include response and recovery procedures beyond evacuation, such as incident command structure and business continuity steps. Check your regulatory context to confirm which term applies.
Who should be responsible for maintaining an emergency response plan?
The plan should name specific roles — not just "management" — with backups assigned for each, since fewer people step into leadership voluntarily as an incident escalates. In practice, this is usually an EHS or facilities manager who owns the document, supported by named floor wardens or team leads who execute specific duties during an event.
