How to Write a JHA (Job Hazard Analysis)

Updated 2026-06-23

Learning how to write a JHA (Job Hazard Analysis) comes down to a repeatable method: break the task into the steps the crew will actually perform, identify the hazards in each step, assign a specific control to each hazard using the hierarchy of controls, and verify the plan against field conditions before the work begins. Done well, a JHA turns a vague "be careful out there" into a specific, signable plan the crew can follow; done poorly, it becomes boilerplate nobody reads. This guide walks through how to write a JHA that holds up — to the crew, and to an auditor.

What you are actually building

A Job Hazard Analysis answers three questions for every step of the work: what are we doing, what could hurt someone, and what are we doing about it. The goal of writing one is not to fill out a form — it is to think through the task deliberately, ahead of time, so the hazards are addressed before the crew is in the middle of the job. A JHA that matches the actual task, location, and conditions protects people; one copied from a template folder does not.

Before you start writing, gather what you need: a clear understanding of the task and its scope, the site conditions, the applicable standards (OSHA, EM 385-1-1, or others), and ideally the input of the people who will perform the work. The crew's knowledge of how the job actually goes is one of the most valuable inputs to a good JHA.

Step 1: Break the job into steps

List the task in the order it will actually happen — usually four to ten steps. Keep each step an action: "set the ladder," "pull the cable," "energize the panel," not a vague phase like "do the electrical work." The right level of detail is enough to capture the distinct hazards: if a part of the job carries its own set of hazards, it deserves its own step.

Avoid two extremes. Too few steps ("set up," "do the work," "clean up") hides the hazards inside vague phases. Too many steps (every minor motion) buries the analysis in detail nobody will read. Aim for the natural breaks in the work where the hazards change.

Step 2: Identify the hazards in each step

For each step, ask what could cause harm, and be specific. Work through the hazard categories — falls, electrical, struck-by, caught-between, chemical, ergonomic, environmental — and name the actual hazard in that step. "Working at height" is weak; "fall from the leading edge at twelve feet while setting forms" is specific enough to control.

Specificity is what makes the difference. A named, located, quantified hazard points directly to its control, while a vague hazard category invites a vague control. Push each hazard description until it describes a real thing that could happen in that step, to a real person, in that location.

Step 3: Assign a control to each hazard

This is where most JHAs fail — they name hazards but hand-wave the controls, or default straight to PPE. Use the hierarchy of controls, in order:

• Eliminate the hazard — can the task be done without it at all?
• Substitute a less hazardous method or material
• Engineering controls — guard, isolate, or design the hazard out (a trench box, a machine guard, local exhaust)
• Administrative controls — procedures, training, signals, exclusion zones
• PPE — the last line of defense, not the first

Tie each control to the specific hazard it addresses. The instinct to jump straight to "wear gloves and be careful" skips the most effective controls — always ask first whether the hazard can be eliminated or engineered out before relying on PPE and procedure.

Step 4: Assign responsibility and verify

Name who is responsible for each control, and build in a check. A JHA that lists controls but never confirms they happened is just paperwork. Before the work starts, the plan is reviewed against the actual field conditions — someone walks the area and confirms the controls are genuinely in place, the conditions match the plan, and nothing has changed since the JHA was written.

A simple JHA structure

The table is a convenient format, but the thinking is what matters — a JHA can be a form, a digital workflow, or a field card as long as it captures the steps, hazards, controls, and accountability.

Common mistakes to avoid

A few failures show up again and again. Reusing yesterday's JHA unchanged, when the task, location, or conditions have changed — the JHA has to change with them. Naming hazards without controls, or pairing every hazard with the same generic PPE line. Describing the job in vague phases instead of real steps. And skipping the field review, so a JHA written at a desk is never confirmed against the conditions the crew actually faces. Each of these turns the JHA from a safeguard into a formality.

From the field: writing a JHA crews will actually use

In fourteen years across federal, heavy civil, and industrial projects, the JHAs that work share one trait above all: they are written with the crew, not at them. When the people doing the job help break down the steps and name the hazards, the analysis captures how the work actually goes — the awkward reach, the blind corner, the step everyone skips — and the crew owns the plan because they helped build it. The JHA written alone at a desk and handed down complete gets signed and ignored.

The other field reality is verification. The best-written JHA in the world is worthless if the controls it lists are not actually in place when the work starts. On the projects I have run, the habit that separates a real JHA from a paperwork JHA is the field check: before the task begins, someone confirms the trench box is in, the anchor point exists, the panel is verified dead — the specific controls the JHA promised. Writing the JHA is half the job; verifying it in the field is the other half. Do both, and the JHA prevents incidents instead of just documenting good intentions.

The bottom line

To write a JHA that holds up, break the job into real action steps, name the specific hazard in each step, assign a control to each hazard using the hierarchy of controls, and assign responsibility and verify in the field before work begins. A good JHA is specific, control-focused, written with the crew, and confirmed against actual conditions — that is the difference between a document that prevents an incident and one that just sits in a binder.

Frequently asked questions

How many steps should a JHA have?

Usually four to ten action steps, broken at the natural points where the hazards change. Too few steps hide hazards inside vague phases like "do the electrical work"; too many bury the analysis in detail nobody reads. Each step should be a real action in the order the work happens.

What is the hierarchy of controls and why does it matter?

It is the order of preference for controlling a hazard: eliminate, substitute, engineering controls, administrative controls, then PPE as the last line of defense. It matters because the most effective controls eliminate or engineer out the hazard, while PPE only protects if it is used correctly every time. A JHA that jumps straight to PPE skips the stronger controls.

Who should write the JHA?

Ideally the people who will perform the work, or at least with their input. The crew's knowledge of how the job actually goes captures hazards a desk-written JHA misses, and involving them creates ownership so the plan is followed rather than ignored.

How do I make sure a JHA is actually followed?

Verify it in the field before work begins. Someone walks the area and confirms the listed controls are genuinely in place and the conditions match the plan. A JHA that lists controls but is never confirmed against the field is paperwork — the verification is what makes it protection.

Related JHAs

• What Is a JHA? — the concept behind the method
• What Is a Pre-Task Plan? — applying the JHA at the point of work
• JHA vs JSA vs AHA — how the terms compare
• What Is an AHA (USACE)? — writing the federal-project version

Written by Mustafa Tok, CSP, ASP, CHST — OSHA Authorized Outreach Trainer with 14+ years of international construction safety experience across federal, heavy civil, and industrial projects.