Back to Resources

JHA Generation That Doesn't Read Like a Template

Your JHAs say 'wear hard hat' for every task. Here's how to generate site-specific hazard analyses with real citations — not copy-paste boilerplate.

Halozen Team
2026-01-05
7 min read

You're standing up a new project. The GC needs JHAs before mobilization. You've got 30 activities and 3 days. So you do what everyone does — pull the JHAs from the last project, change the project name, maybe update a few line items. Now every task says "wear hard hat, wear safety glasses, maintain 3-point contact." The OSHA inspector isn't impressed. Neither is the owner's safety rep.

The problem with template JHAs isn't that they're wrong. It's that they're generic. "Fall hazard — use fall protection" is technically accurate for steel erection, but it doesn't tell your crew whether they need a personal fall arrest system, guardrails, or safety nets for that specific activity at that specific height. And it definitely doesn't cite the right standard.

What a Good JHA Actually Looks Like

A JHA that passes scrutiny — from an OSHA inspector, a GC's safety director, or a USACE quality manager — does three things:

  • Task-specific hazard identification — not "fall hazard" but "fall hazard during steel decking installation at 35' elevation with open perimeter edges"
  • Controls following the hierarchy — elimination first, then engineering controls, then administrative, then PPE. "Wear a harness" should be the last resort, not the first line item.
  • Real regulatory citations — 1926.502(d) for personal fall arrest systems, not just "OSHA fall protection." Specific enough that someone can look it up.

The EM385 Problem

If you're doing federal or USACE work, your JHAs need to reference EM385-1-1 in addition to OSHA standards. This is where most templates fall apart completely. EM385 has its own section numbering, its own specific requirements that go beyond OSHA in several areas (especially confined space, electrical, and excavation), and inspectors who know the difference between a generic JHA and one that actually addresses the EM385 requirements in the contract.

Manually mapping activities to both OSHA 1926 and EM385-1-1 for 30+ tasks is a multi-day effort. Most safety managers either default to OSHA-only citations and hope nobody checks, or they spend the time but only for the highest-risk activities, leaving gaps in the rest.

How Automated JHA Generation Works

Halozen reads your project spec and identifies the work activities that need hazard analyses. Not just the obvious ones — if the spec mentions demolition in the scope, the system identifies associated activities like silica exposure, lead paint abatement, and structural shoring that might not have their own line items but still need JHAs.

For each activity, it maps hazards to the specific work context, selects controls following the hierarchy (not just "wear PPE"), and cites the applicable standards. OSHA 1926, OSHA 1910 where general industry standards apply, EM385-1-1 for federal work, or WHS regulations for Australian projects. Each citation is a real standard reference, not a generated one.

What You Still Need to Do

Automated generation gets you 80% of the way there in a fraction of the time. The last 20% is where your safety team's site knowledge matters:

  • Site-specific conditions — adjacent live traffic, occupied building, existing underground utilities, weather exposure
  • Crew-specific considerations — new apprentices on crew, language barriers, specialty equipment certifications
  • Toolbox talk integration — pulling the day's high-risk JHA into the morning brief so crews actually review it
  • Incident history — if you had a near-miss on steel erection last project, that specific hazard gets called out

The difference is your safety manager spends their time on the site-specific judgment that only they can provide, instead of formatting tables and looking up standard numbers they already know by heart.

Ready to see Halozen in action?

See Halozen in action on your own documents.