What Is the Emergency Action Plan Builder?
CC-EAP-PLAN-BUILDER-001 v1.0 is a structured documentation framework built on the Compliance Crucible platform. It walks an employer through the elements of a written emergency action plan under 29 CFR 1926.35 and assembles them into a single, versioned, lockable record — site identity and written-plan basis, escape procedures and route assignments, procedures for employees who remain to operate critical operations before evacuating, post-evacuation accountability, rescue and medical duties, the preferred means of reporting emergencies, the persons or job titles to contact for further plan information, the employee alarm system and its distinctive signals, the types of evacuation established, muster and assembly areas, emergency resources near the site, scenario response documentation, designated evacuation assistants, and the plan review and drill record.
The tool is guided rather than open-ended: fill-in-the-blank fields, checkboxes, and structured selections walk the user through each plan element. The six plan elements required by 1926.35(b) form the completeness spine, and each element supports an explicit not applicable declaration distinct from a blank field — the assistant raises an open item whenever a required input is neither documented nor declared. The oral-plan allowance at 1926.35(e)(3) for employers with 10 or fewer employees is surfaced rather than assumed. When a record is locked, the platform preserves an immutable server-side snapshot with a content hash — a fixed, dated version of what the plan said at that moment. The tool records what the employer provides; it does not decide whether the plan complies or whether work may proceed.
What the Tool Produces
A completed record can produce the following outputs. See them rendered on a full sample record on the Sample Output page.
Written Emergency Action Plan
The plan-of-record: every documented element rendered in order with its authority anchor, the open-items register, the emergency resource roster with its verification state, live verified authority references, and the employer attestation.
Open-Item Roll-ups
Plan-level registers surfacing every unresolved element and undeclared field with its section, so nothing is forced to look finished when it is not.
Authority Reference Panel
Verified federal authority citations for emergency action plans, retrieved live from the platform’s reviewed authority library and attached to the record — pointers to the standard, never a judgment about the plan.
Machine Audit JSON
Structured machine-readable export of the record, including identity and lock fields, all plan elements, open items, site-media content hashes, and authority anchor provenance.
What the Tool Does Not Do
CC-EAP-PLAN-BUILDER-001 does not perform or substitute for any of the following:
- Determining regulatory compliance or stating that a plan is compliant, approved, certified, or safe
- Verifying emergency-service capability, trauma designation, operating hours, response areas, or response times
- Evaluating site hazards, or determining which emergency scenarios apply to a site
- Determining the adequacy of escape routes, assembly areas, shelter locations, or alarm audibility
- Replacing emergency-management, fire-protection, or engineering judgment
- Making state-plan determinations
Authority Boundary
| Tool ID | CC-EAP-PLAN-BUILDER-001 |
|---|---|
| Version | v1.0 |
| Class | B-1 Program Assistant — Authority-Bounded Documentation Framework |
| Authority Packet | SAP-EAP-1926.35-v1 |
| Primary Authority | 29 CFR 1926.35 — Employee emergency action plans. |
| Supporting Authority | 29 CFR 1926.34 (means of egress) · 29 CFR 1926.150 (fire protection; employee alarm systems at 1926.150(e)). |
| Live Authority References | Verified federal anchors are retrieved live from the platform’s reviewed authority library (Concordance Direct Adapter) and displayed with the record. Federal OSHA baseline; pointers to the standard, not a judgment. |
| State-Plan Awareness | State-plan requirements may differ from or exceed the federal baseline; independent verification is required. |
| Jurisdiction | Federal OSHA baseline; state verification required. |
| Strongest Statement | “Documentation fields are complete for this element” — never that the employer complies, that a route or assembly area is adequate, or that work may proceed. |
A Documented Anomaly in the Printed Standard
29 CFR 1926.35(c)(1) requires an employee alarm system conforming to a cross-referenced section — §1926.159 — that no longer exists. That section was removed from the Code of Federal Regulations at 61 FR 31427 (June 20, 1996); the cross-reference in 1926.35 was never corrected and still prints today.
This tool neither parrots the dead reference as a live requirement nor silently deletes it. It anchors the employee-alarm element on 29 CFR 1926.150(e) and presents the dangling cross-reference with its Federal Register history, so the employer can see exactly what the printed rule says, what happened to it, and what the plan is actually documented against. The anomaly is carried in the platform’s authority library as a verified, cited edge — not as an editorial assumption.
Why this matters
An employer reading the printed rule can spend real time chasing a standard that has not existed since 1996. Documenting the anomaly, with its citation trail, is more useful to a reviewer than either repeating it or quietly ignoring it. The tool takes no position on how a compliance officer will read the requirement; it records the basis the employer documented and shows its work.
Proper Use Case
Example — Written Emergency Action Plan Documentation
A general contractor is mobilizing on a multi-employer industrial site. The safety lead needs one reviewable written emergency action plan: how employees escape and who is assigned to which route, who stays to shut down critical operations and by what procedure, how everyone is accounted for at the muster point, who performs rescue and medical duties, how an emergency is reported, who to contact for plan information, what the alarm is and what its signals mean — plus the hospitals, clinics, and responding agencies near the site, with each one confirmed rather than assumed.
The tool helps the employer structure, complete, and preserve that documentation as a versioned, lockable record with live verified authority references attached. It does not decide whether the plan is compliant, whether an assembly point is adequate, whether a listed hospital can receive a given casualty, or whether work may proceed. Those decisions remain with the employer and its qualified professionals.
Improper Use Cases
CC-EAP-PLAN-BUILDER-001 should not be used as any of the following:
- A statement that an employer or plan is compliant, or that a record satisfies requirements
- A verification that a listed hospital, clinic, or responding agency is open, capable, in-network, or able to respond
- A determination that escape routes, assembly areas, shelter locations, or alarm coverage are adequate
- A substitute for site-specific emergency planning, drills, or coordination with responding agencies
- A statement that conditions are safe or that work may proceed
- A professional legal, emergency-management, or engineering service
Platform Access
CC-EAP-PLAN-BUILDER-001 is available through member-gated access. Active Compliance Crucible membership is required. Records persist to the member’s organization workspace under row-level security and lock with a tamper-evident document verification value; a locked record recomputes to its stored hash. Emergency-resource lookups are performed server-side; no mapping credential is exposed to the browser.
The Emergency Action Plan Builder sits alongside the other live Compliance Crucible documentation tools — including the Respiratory Program Assistant, Silica Program Assistant, Confined Space (PRCS) Documentation Readiness, LOTO Procedure Builder, JHA / AHA Procedure Builder, Fatal Four Recognition, and HazCom / GHS — each tied to a defined regulatory scope with clear output boundaries. Additional program tools are in development.
Scope Limitation
This page is a descriptive scope and application document only. It is not regulatory guidance, a legal opinion, an emergency-management or engineering service, a certification, an approval, or an employer field decision. Emergency planning requirements are complex and employer-, task-, and site-specific. Independent verification of applicable requirements is required for every project and every employer.
Compliance Crucible LLC does not practice law, practice engineering, practice emergency management, verify emergency-service capability, certify conditions, authorize work, or make employer field decisions.