OSHA Emergency Action Plan Requirements: Where Detection Fits and Where It Does Not
An emergency action plan audit should begin with duties, not devices. A camera alert can help a trained person learn that something may be happening, but it cannot write evacuation procedures, assign authority, account for employees, provide medical care, or make an employee alarm compliant. Those responsibilities remain with the employer and the people named in the plan.
The useful purchasing question is therefore narrower than “Can cameras improve emergency response?” It is: which documented handoff could receive better event information, who evaluates that information, and what required procedure follows? That framing prevents a detection project from becoming an unsupported compliance claim.
What does OSHA require in an emergency action plan?
When another OSHA standard requires an emergency action plan, 29 CFR 1910.38 generally requires a written workplace plan with six minimum elements, an employee alarm system, trained evacuation assistants, and employee review at specified moments. Employers with 10 or fewer employees may communicate the plan orally. The rule’s application clause matters: section 1910.38 governs an EAP required by another Part 1910 standard, while OSHA separately recommends emergency planning for all employers.
Scope and as-of date
Regulatory status was checked September 11, 2026 against eCFR Title 29 content current through September 9, 2026. No new 2026 compliance deadline is claimed. This article concerns no grant program, so there is no funding window or expired-grant status to report. Confirm site-specific obligations with qualified safety and legal advisers.
A document can name every required topic and still leave an operational gap. Audit each section for an initiating event, a reporting route, an authorized decision-maker, an action, and a fallback when the normal channel is unavailable. Detection may strengthen the first two links in selected camera-covered scenes. It does not complete the chain.
Where can detection support the six required elements?
Detection can support parts of reporting and situational awareness, but it does not satisfy any of the six elements by itself. The OSHA minimum-elements page provides the regulatory starting point; the crosswalk below turns those headings into an ownership audit.
Swipe or scroll horizontally to view all table columns.
| Required element | Question the plan must answer | Possible detection support | What detection cannot replace |
|---|---|---|---|
| Report a fire or other emergency | How does an employee or system report the event, and who receives that report? | A configured visual alert may bring a camera-covered event to a named recipient for evaluation. | The employer’s reporting procedure, manual reporting options, emergency call, or required alarm activation. |
| Evacuation procedures and route assignments | Who orders each response, what type applies, and which routes should employees use? | A reviewed event image may add location context for an authorized decision-maker. | Evacuation authority, route design, employee instructions, or judgment about whether to evacuate or shelter. |
| Critical plant operations | Who may remain, what may they operate, and when must they leave? | An alert can be routed to the role already responsible for the affected operation. | The shutdown procedure, role qualification, exposure limits, or the decision that continued operation is safe. |
| Account for employees after evacuation | Who conducts the count, where, and how are discrepancies escalated? | Camera review may provide supplemental context about a covered doorway or area. | A roster, assembly process, human accountability, or proof that an unobserved person is safe. |
| Rescue or medical duties | Which trained people perform these duties, and what procedure do they follow? | A person-on-ground alert may notify a designated responder about a visible event. | Assessment, first aid, rescue, emergency medical services, or training required for assigned personnel. |
| Plan contacts | Which name or job title can explain the plan and an employee’s duties? | Alert routing can mirror the plan’s role-based contact and after-hours escalation list. | The required contact designation, current contact data, or responsibility for explaining the plan. |
The boundary is clearest in the accountability row. A camera may show that someone crossed a covered doorway, but the absence of a detection does not prove a person left, reached the assembly point, or avoided another route. Keep the plan’s accountability method authoritative and treat video as limited corroborating context.
Is camera-based detection an OSHA employee alarm?
Camera-based detection should be treated as an upstream information source, not presumed to be the required employee alarm. Under 29 CFR 1910.165, an employee alarm must warn people for the action called for in the plan or provide escape time, be perceptible in affected areas, and use a distinctive, recognizable signal. Section 1910.38 also requires the employer to have and maintain the alarm system.
These functions should remain explicit: detection observes a configured visual condition; verification evaluates available context; escalation reaches a responsible role; the employee alarm warns affected workers; and the EAP tells them what to do. A site may integrate some functions, but integration does not erase the requirements attached to each one.
Compliance boundary
Do not describe a camera alert as OSHA compliance or as a replacement for required alarms, evacuation procedures, employee instruction, inspections, or training. For fire scenarios, IntelliSee itself describes visual smoke and flame detection as a supplemental layer.
How should you build the plan-to-trigger handoff?
Build the handoff by assigning a person, decision, communication route, action, and fallback to every detection scenario. The result should be a short operating specification that sits beneath the EAP rather than replacing it.
- Start with the plan. Record the hazards addressed, the applicable response for each one, and the role authorized to initiate that response. Do not let a vendor’s detection menu define workplace policy.
- Define the observable event. State what must be visible in a particular camera view, such as visible smoke, a drawn weapon, or a person in a configured restricted zone. A person box describes a detected person, not proof that the person is unauthorized.
- Name the first recipient. Identify the staffed role, device, and after-hours route that receive the alert. Add a fallback for unavailable personnel, failed communications, or an offline camera.
- Write the decision rule. Specify what the recipient reviews, whom they contact, and which existing procedure they may initiate. Separate automatic alert delivery from human authority over evacuation, sheltering, emergency calls, or a building-wide message.
- Test the whole handoff. Evaluate the actual scene and stream, alert delivery, recipient availability, decision record, employee alarm, and planned action. Record failures by link so a fast model does not conceal a slow or ownerless response.
This workflow also clarifies the relationship to a mass-notification system. Detection may supply an earlier input to a decision-maker, while notification distributes an authorized message. The EAP still defines who acts and what employees are expected to do.
What should buyers test before adding analytics?
Buyers should test operational fit on the real site before treating analytics as part of an emergency workflow. A product presentation cannot establish camera coverage, stream access, alert ownership, or the suitability of a particular view.
- A scene list connecting each proposed detection to a documented hazard and response role.
- A camera-by-camera assessment conducted under the lighting and operating conditions that matter.
- Proof that the system can access a usable stream without assuming all installed cameras are compatible.
- A routing test for each shift, weekend coverage, unavailable recipients, and communication failure.
- A clear statement of what a detection label means and what it does not establish.
- A written boundary preserving required alarms, procedures, inspections, training, and human decision authority.
- Acceptance results measured from event presentation through receipt and action, not model output alone.
An existing-camera approach does not automatically mean every camera is suitable. IntelliSee’s existing-camera guide identifies four practical dependencies: a usable image, access to the stream, somewhere to run the model, and a person who receives the result. Field of view, credentials, network access, and alert ownership should therefore be validated before the EAP references the workflow.
How do fire and workplace-violence scenarios differ?
Fire and workplace-violence events may share an alert path, but they should not inherit the same decision rule. The plan must define the response for the actual hazard, and the people interpreting an alert must understand that a visual label is evidence to review rather than a complete emergency determination.
Visible smoke or flame
A configured camera may add another view of visible smoke or flame in its field of view. That observation can be routed to a safety role, but required fire detection, employee alarms, inspections, and emergency procedures remain in place. The operating specification should state what the recipient does if the visual alert and another fire-safety system disagree.
Weapon or restricted-area event
A weapon or person detection may supply visual context to a security or safety decision-maker. It does not determine a person’s intent, authorization, or identity, and it should not autonomously select an evacuation or shelter instruction. The plan should establish who evaluates the scene, who contacts emergency services, and who has authority over employee warnings.
Person on the ground
A person-on-ground alert may help notify a designated recipient about a camera-covered event. It cannot diagnose the situation, establish whether medical care is needed, or perform rescue. The EAP’s assigned medical or rescue duties and the organization’s emergency-call procedure continue to control the response.
What should the finished audit produce?
The finished audit should produce an EAP that stands on its own and a separate, testable detection handoff for selected risks. Each scenario should identify the camera-covered condition, first recipient, verification step, authorized decision, employee-warning method, required action, backup route, and owner responsible for keeping the workflow current.
If those fields cannot be completed, the procurement is premature. If they can, camera-based detection may become a useful supplemental input without being oversold as a plan, an alarm, or compliance. To examine which existing views and alert routes could support your documented procedures, contact IntelliSee.
Frequently asked questions
Does every employer need an OSHA emergency action plan?
No. Section 1910.38 applies when another OSHA standard in Part 1910 requires an EAP. OSHA nevertheless recommends emergency planning for all employers. Determine which standards apply to the worksite before describing a plan as legally required.
What are the six minimum elements of an EAP?
They are procedures for reporting emergencies; evacuation and exit-route assignments; employees who remain for critical operations; post-evacuation accountability; assigned rescue or medical duties; and the name or job title of contacts who can explain the plan or an employee’s duties.
Can an employer use an oral emergency action plan?
Under 29 CFR 1910.38, an employer with 10 or fewer employees may communicate the plan orally. Other applicable requirements and site circumstances still need review, so the head-count exception should not be treated as a reason to leave responsibilities undefined.
Can AI video analytics replace a fire alarm or employee alarm?
No. Camera-based detection should be treated as supplemental unless the complete system has independently been shown to satisfy every applicable alarm requirement. IntelliSee directs users to keep required fire alarms, procedures, and inspections in place.
Can cameras account for everyone after an evacuation?
Cameras may provide limited context for covered areas, but they cannot prove every employee reached the assembly point or is safe. The plan needs a defined accountability process, current information, responsible people, and an escalation method for discrepancies.
Sources
- 29 CFR 1910.38, Emergency action plans
- 1910.38, Emergency action plans
- Emergency Action Plan: Minimum Requirements
- Emergency Preparedness and Response: Getting Started
- 1910.165, Employee alarm systems
- AI Video Analytics on Existing Cameras: What Actually Has to Be True
- AI Smoke and Fire Detection
- Mass Notification Systems: The Trigger Gap Between Detection and Alert
Your people. Your spaces.
See it on the cameras you already have.
Bring one priority event and one camera view. We will walk through how IntelliSee turns it into an alert your team can act on.