If you're in construction safety, you don't need someone to explain what 1926.501 is. You know it's fall protection. You know 1926.650 is excavations. You probably have the top-10 citation list memorized because OSHA publishes it every year and fall protection is always number one.
The problem isn't knowing the standards. The problem is this: you've got a 400-page spec with safety requirements scattered across at least 5 different sections, your safety plan is due in a week, and you need to map every one of those requirements to the right OSHA standard with specific citations. Not "fall protection — OSHA 1926 Subpart M." The actual subsection. 1926.502(d) for personal fall arrest. 1926.502(b) for guardrail systems. Because when the inspector shows up, "Subpart M" isn't going to cut it.
Where Safety Requirements Hide in Specs
On a typical commercial project, safety requirements aren't in one place. They're spread across:
- Section 01 35 26 (Safety Requirements) — the obvious one, but often just a summary with references to other sections
- Supplementary Conditions — additional contractor obligations that modify the general conditions, sometimes with insurance and indemnification requirements that have safety implications
- Technical sections — silica exposure requirements buried in the concrete division, lead paint protocols in the demolition scope, confined space in the mechanical section
- Exhibits and appendices — the owner's safety program that your plan needs to comply with, referenced on page 8 but located on page 290
Miss one of these, and your safety plan has a gap. Maybe nobody notices. Maybe the GC's safety director catches it during review. Or maybe the OSHA inspector finds it during a site visit, and now you've got a citation that could have been prevented.
The Mapping Workflow
Here's what the mapping process actually involves: for each safety requirement in the spec, you need to identify the applicable OSHA standard (or EM385 section for federal work), determine the specific subsection that applies, document the control measures your team will implement, and record all of it in a format that holds up during an audit.
Manually, this is a 2-3 day effort for someone who knows the standards well. For a complex project with 200+ safety requirements across multiple divisions, it's a week. And it needs to be done for every project.
Halozen automates the extraction-and-mapping step. It reads the full spec, identifies every safety-related requirement regardless of which section it appears in, and maps each one to the specific OSHA 1926, OSHA 1910, or EM385-1-1 standard that applies. Your safety manager reviews the mapping and adds site-specific context instead of spending days on the lookup work.
What an Inspector Actually Looks At
When OSHA walks your site, they're not checking whether you have a safety plan. Everyone has a safety plan. They're checking whether your plan addresses the actual hazards on your site with specific, implementable controls. They want to see:
- Specific standard citations that match the work being performed — not just "Subpart M" but the actual subsection for the fall protection method you're using
- Controls that follow the hierarchy — if your plan jumps straight to PPE without documenting why engineering controls aren't feasible, that's a finding
- Evidence that the plan was developed for this project, not copied from the last one — site-specific hazards, project-specific scope
- Training records that match the hazards identified in the plan
Automated mapping doesn't replace your safety program. It makes sure the documentation behind it is complete, correctly cited, and traceable — the kind of thing that turns a stressful site visit into a routine one.