# Job Hazard Analysis (JHA)

> The structured, task-by-task analysis that breaks work into steps, identifies the hazard in each, and specifies the control before anyone is exposed — the planning document at the heart of a proactive safety program.

- Source: https://briq.ai/acu/object/job-hazard-analysis
- Department: Field Operations & Project Controls (https://briq.ai/acu/department/field)
- Catalog code: FLD 203 · Level: Practitioner · Track: Operations · 11 min read
- Also known as: JHA, Job Safety Analysis, JSA, Activity Hazard Analysis, AHA, Task Hazard Analysis

## Definition

A job hazard analysis is a systematic method of examining a specific task by breaking it into its component steps, identifying the hazards associated with each step, and determining the controls needed to eliminate or reduce those hazards before the work begins. It is fundamentally a planning and prevention document, produced by the people who understand the task, that forces hazards to be anticipated rather than discovered through injury. The JHA feeds directly into the crew's briefing and becomes the basis for the toolbox talk, the required PPE, and the sequence of work. A JHA is not a permit, not a generic safety policy, and not a one-time document; it is task-specific and must be revised when the task, the crew, the equipment, or the site conditions change, and a JHA that is written once and never revisited as conditions evolve has stopped being an analysis and become a file.

## Why it matters

It moves safety from reaction to prevention. Every other safety document — the incident report, the OSHA log — records what already went wrong; the JHA is where the hazard is caught on paper before it reaches a person. A program built on JHAs is anticipating the fall, the cave-in, and the arc flash and designing them out, rather than tallying them after the fact.

It applies the hierarchy of controls where it can actually change the outcome. A good JHA does not default to 'be careful' and PPE; it asks first whether the hazard can be eliminated or substituted, then engineered out, then controlled administratively, and only then relies on personal protective equipment. That discipline, applied at the planning stage, is what separates a control that works from one that depends on a worker never making a mistake.

It is the source document for the crew's daily safety communication and for regulatory expectations. The toolbox talk, the required PPE, and often a permit for high-hazard work all flow from the JHA. For high-hazard activities in particular — excavation, confined space, energized electrical, steel erection, crane operations — a documented, task-specific analysis is both an expectation of a serious program and, in many contexts, effectively required.

It is scrutinized after a serious incident, and its quality is exposed there. When an injury occurs, investigators ask whether a JHA existed for the task, whether it identified the hazard involved, whether it specified the control that failed, and whether the crew was briefed on it. A thorough, current, task-matched JHA supports a defensible program; a generic or missing one, or one that never anticipated the actual hazard, is a glaring gap.

## Lifecycle

1. **Task selection and scoping** — The task to be analyzed is defined at the right granularity — specific enough to have real hazards, not so broad that the analysis becomes generic. High-hazard and non-routine tasks are prioritized.
2. **Breaking the task into steps** — The task is decomposed into sequential steps as it will actually be performed. Steps that are too coarse hide the hazards; the analysis is only as good as the honesty of the step breakdown.
3. **Hazard identification per step** — Each step is examined for the hazards it presents — energy sources, heights, atmospheres, struck-by and caught-between exposures, chemical and ergonomic risks. Involving the crew who does the work surfaces hazards a planner alone would miss.
4. **Control selection** — For each hazard a control is chosen using the hierarchy of controls, preferring elimination and engineering over reliance on PPE. Defaulting straight to PPE is the most common way a JHA produces weak controls.
5. **Review and approval** — A competent person reviews the JHA for completeness and adequacy, and for high-hazard work it may require sign-off. A JHA approved without genuine review is a rubber stamp on an untested analysis.
6. **Communication to the crew** — The JHA is delivered to the crew, typically through the toolbox talk and pre-task briefing, in a language they understand. An analysis that never reaches the people doing the work protects no one.
7. **Field verification and revision** — As the work proceeds, actual conditions are checked against the JHA, and it is revised when the task, crew, equipment, or conditions change. A JHA frozen at its first draft drifts out of alignment with reality.
8. **Retention and reuse** — JHAs are retained and reused as templates for similar tasks, improved by lessons from near-misses and incidents. The library becomes an organizational asset when it learns rather than merely accumulates.

## Anatomy

- **Task / activity description** — The specific work being analyzed, scoped precisely. Too broad a task produces a generic, low-value analysis.
- **Job steps in sequence** — The task broken into the steps as actually performed. The granularity here determines whether hazards are exposed or hidden.
- **Hazards per step** — The specific hazards present at each step — fall, struck-by, caught-between, atmosphere, energy, chemical, ergonomic. The core analytical content.
- **Controls per hazard** — The control for each hazard, selected up the hierarchy of controls. Preference for elimination and engineering over PPE is the mark of a strong JHA.
- **Hierarchy-of-controls level** — Which level each control sits at — elimination, substitution, engineering, administrative, PPE. Makes the strength of the control explicit rather than assumed.
- **Required PPE** — The personal protective equipment for the task, as the last line of defense rather than the first control reached for.
- **Competent / qualified persons** — Who must be present or in charge for high-hazard steps, such as a competent person for excavation or an attendant for confined space.
- **Permits and prerequisites** — Any permits, atmospheric tests, lockout, or inspections that must be completed before the step proceeds.
- **Reviewer and approval** — Who reviewed and approved the analysis and when, establishing that a competent person validated it.
- **Crew acknowledgement** — Confirmation that the crew was briefed on and understood the JHA, linking the analysis to actual communication.
- **Revision history** — Changes to the JHA as conditions evolved. A static revision history on a long task is a sign the analysis has stopped tracking reality.
- **Linked records** — The toolbox talk that delivers it, permits, incidents on this task, and the schedule activity it governs.

## Failure modes

- **Generic JHA that fits no actual task** — A boilerplate analysis is pulled from a library and applied without tailoring it to the real task, crew, and conditions. It lists plausible-sounding hazards and controls that do not correspond to what the crew is actually doing, so it neither guides the work nor holds up when the real hazard causes an injury it never named.
- **PPE used as the default control** — Every hazard is answered with 'wear the appropriate PPE' rather than asking whether it could be eliminated or engineered out. The controls sit at the weakest level of the hierarchy, depending entirely on a worker never erring, which is exactly the assumption serious incidents violate.
- **Steps too coarse to expose hazards** — The task is broken into two or three broad steps like 'set up' and 'perform work,' hiding the specific moments where the real exposure occurs. The hazard that lives inside a sub-step nobody wrote down is the one that never gets a control.
- **Written by a planner without the crew** — The JHA is composed at a desk by someone who does not perform the task, and the field-specific hazards the crew knows about — the awkward reach, the pinch point, the way the task is really done — never make it onto the page. Involving the crew is where the most valuable hazard identification comes from.
- **Never revised as conditions change** — The task, the equipment, the weather, or the site condition changes, and the JHA is not updated. Work proceeds against an analysis that no longer describes the actual hazards, which is common on long-duration or evolving tasks.
- **Never delivered to the crew** — A thorough JHA is filed but the crew doing the work is never actually briefed on it, or is briefed in a language they do not understand. The analysis is sound and the protection is zero, because the controls only work if the people exposed know them.
- **Approved without genuine review** — The JHA carries a signature but no competent person actually scrutinized it for whether the hazards and controls are adequate. The approval implies a validation that never occurred, which is exposed when the analysis is examined after an incident.

## Metrics

- **JHA coverage of high-hazard tasks** — Share of high-hazard and non-routine activities with a current, task-specific JHA before work begins. The core proactive-coverage metric.
- **Control-hierarchy distribution** — How controls distribute across elimination, engineering, administrative, and PPE. A PPE-heavy distribution signals weak analysis regardless of how many JHAs exist.
- **Crew involvement rate** — Share of JHAs developed or reviewed with input from the crew performing the task. Predicts how many real field hazards were captured.
- **Revision responsiveness** — Whether JHAs are updated when conditions change. Distinguishes a living analysis from a filed one.
- **Briefing linkage** — Share of JHAs actually delivered to the crew through a documented briefing. Measures whether the analysis reached the people it protects.
- **Incident correlation** — Whether incidents occurred on tasks with a JHA that named the hazard, versus tasks with no or a generic JHA. The truest measure of effectiveness.
- **Reuse-and-improve rate** — How often JHAs are improved from near-miss and incident learning rather than merely copied. Shows whether the library learns.

## The AI shift

- **Conversational** — The JHA library becomes an analytical resource you can question. You ask which high-hazard activities scheduled this month have no current JHA, which JHAs rely predominantly on PPE where an engineering control exists, or whether the task involved in a recent incident had a JHA that named the hazard, cited to the analyses.
- **Generative** — Drafting shifts from a blank template to a reviewable first analysis: given a task description and the equipment and conditions, a model proposes a step breakdown, candidate hazards per step, and controls ranked up the hierarchy, drawing on the organization's library and incident history, which the competent person and crew refine — critically, the model proposes and the humans validate, never the reverse.
- **Orchestrated** — The JHA stops being a standalone document. It is tied to the schedule activity it governs so it is prepared before the work is scheduled, its controls flow into the toolbox talk and PPE list, its prerequisites trigger the required permits and atmospheric tests, and it is cross-referenced against incidents on the same task so lessons feed back into the controls.
- **Autonomous** — The routine motion runs continuously: upcoming high-hazard activities are checked for a current, task-specific JHA and gaps are surfaced before the work is scheduled, JHAs are flagged for revision when the task or conditions change, PPE-heavy analyses where stronger controls exist are highlighted for reconsideration, and incident learning is routed back to the relevant JHAs, while hazard identification adequacy, control selection, competent-person review, and approval remain human.

## Prompts

### Conversational — Auditing the strength of JHAs before a high-hazard phase.

```text
We are entering the structural steel erection phase next month. Review the JHAs for the erection activities and assess their quality, not just their existence. Tell me which activities have a current, task-specific JHA and which are missing one; for the ones we have, analyze the distribution of controls across the hierarchy and flag any hazard answered only with PPE where an engineering or administrative control is available; and identify any JHA whose step breakdown is too coarse to expose the real hazards of connecting, bolting, and decking at height. Then check whether any of these tasks have a history of incidents that the current JHA does not address.
```

**Expected output:** A quality assessment that separates coverage gaps from weak analyses, flags PPE-default controls and coarse step breakdowns, and connects each finding to incident history, cited to the specific JHAs.

**Follow-ups:**

- For the PPE-only fall hazards, propose stronger controls up the hierarchy.
- Which erection activities are scheduled without any JHA and must be resolved first?
- Which prior incidents on these tasks should be folded into the revised JHAs?

### Generative — Building a first-draft analysis for a non-routine task.

```text
Draft a job hazard analysis for the following non-routine task so my crew and I can refine it. Task: removing and replacing a section of a suspended structural steel beam on an occupied floor, using a temporary support and a rigging operation, in a confined interior space. Break the task into realistic sequential steps as it would actually be performed. For each step, identify the specific hazards. For each hazard, propose a control and label which level of the hierarchy of controls it sits at, preferring elimination and engineering over PPE, and only defaulting to PPE where nothing stronger applies. Identify the competent or qualified persons required, any permits or atmospheric tests needed, and the PPE. Mark clearly where you are uncertain and where the crew's field knowledge is needed to confirm the analysis.
```

**Expected output:** A step-by-step draft JHA with hazards and hierarchy-labeled controls, competent persons and permits identified, and uncertainty explicitly flagged for the crew and competent person to validate rather than accept.

**Follow-ups:**

- Deepen the rigging and temporary-support steps; those carry the highest consequence.
- Which controls here should trigger a permit or a pre-task hold point?
- Turn the confirmed JHA into a toolbox talk for the crew.

### Orchestrated — Making the JHA drive the controls that depend on it.

```text
For the excavation and shoring activity starting next week, connect the JHA to everything that should flow from it. Confirm a current, task-specific JHA exists and identifies the cave-in, atmospheric, and utility-strike hazards with adequate controls. Then trace the downstream: ensure the required competent-person inspection, atmospheric testing, and any permit are set as prerequisites tied to the schedule activity; ensure the controls and PPE flow into the toolbox talk for the crew; and cross-reference any prior excavation incident whose lessons should be reflected. Return a readiness summary that tells me whether this activity is safe to schedule, each conclusion tied to the JHA and the linked record.
```

**Expected output:** A readiness summary confirming the JHA's adequacy and that its prerequisites, briefing, and lessons are wired to the schedule activity, with any gap that would block a safe start named and cited.

**Follow-ups:**

- Draft the toolbox talk directly from this JHA in the crew's languages.
- Which prerequisites are not yet set up and would block a safe start?
- Fold the lessons from the prior excavation near-miss into the JHA controls.

### Autonomous — Standing policy for keeping JHAs current and effective.

```text
Operate our JHA program continuously under these rules. As activities are scheduled, check each high-hazard and non-routine task for a current, task-specific JHA and surface any gap to the safety lead before the work is scheduled. Draft candidate JHAs from the task, equipment, conditions, and our library and incident history for human refinement — never treat a draft as approved. Flag any JHA for revision when its task, crew, equipment, or site conditions change. Highlight any analysis that answers a serious hazard with PPE alone where a stronger control exists. Route incident and near-miss learning back to the relevant JHAs. Ensure each JHA's controls flow into a toolbox talk and its prerequisites into permits and inspections. Never approve a JHA, never sign off hazard-identification adequacy or control selection, and never authorize high-hazard work to proceed on your own; route all of those to a competent person with your reasoning.
```

**Expected output:** Current, coverage-checked JHAs with weak controls and needed revisions flagged, where hazard adequacy, control selection, approval, and authorization to proceed always stay with a competent person, fully audited.

**Follow-ups:**

- Show me this week's high-hazard activities without a current JHA and every PPE-default flag.
- Which JHAs need revision because conditions changed but were not updated?

## Maturity ladder

- **Level 0 — Level 0 — Absent or generic** — Either no JHAs exist or a generic template is applied to every task. Hazards are discovered through incidents rather than anticipated on paper.
- **Level 1 — Level 1 — Documented per task** — Task-specific JHAs are written for high-hazard work with steps, hazards, and controls, reviewed and retained, but rarely revised or crew-driven.
- **Level 2 — Level 2 — Crew-driven and linked** — JHAs are developed with the crew, use the hierarchy of controls deliberately, feed toolbox talks and permits, and are revised as conditions change.
- **Level 3 — Level 3 — Assisted** — Draft analyses are proposed from the task and library, coverage gaps and PPE-default controls are surfaced, and incident learning is routed back for human refinement.
- **Level 4 — Level 4 — Operated** — Coverage checking, drafting, revision flagging, and learning feedback run within guardrails, while hazard adequacy, control selection, approval, and authorization to proceed stay with a competent person.

## FAQ

### What is the difference between a JHA and a JSA?

In practice, very little — 'job hazard analysis' and 'job safety analysis' are largely interchangeable terms for the same method of breaking a task into steps, identifying hazards, and selecting controls. Some organizations and agencies prefer one term, and government construction work often uses 'activity hazard analysis' (AHA) for essentially the same document. The label matters far less than whether the analysis is genuinely task-specific, crew-informed, and current.

### What is the hierarchy of controls and why does it matter in a JHA?

The hierarchy of controls ranks hazard controls by effectiveness: elimination first, then substitution, then engineering controls, then administrative controls, and personal protective equipment last. It matters because controls near the top remove or contain the hazard regardless of human behavior, while PPE depends on a worker using it correctly every time. A JHA that reflexively answers every hazard with PPE has chosen the weakest option; a strong JHA asks whether each hazard can be eliminated or engineered out before it settles for PPE.

### Who should write the JHA?

It should be developed by, or in close collaboration with, the people who actually perform the task, and reviewed by a competent person. A JHA written entirely at a desk by someone who does not do the work reliably misses the field-specific hazards — the awkward reaches, pinch points, and real-world shortcuts — that the crew knows intimately. Crew involvement is not a formality; it is where the most valuable hazard identification comes from.

### How often should a JHA be updated?

Whenever the task, the crew, the equipment, the sequence, or the site conditions change, and after any incident or near-miss on that task. A JHA is an analysis of a specific set of conditions, so when those conditions shift the analysis can silently stop matching reality. On long-duration or evolving tasks, a JHA that still shows its original draft with no revisions is usually a sign that it has become a filed document rather than a living control.

## Related objects

- [Toolbox Talk](https://briq.ai/acu/object/toolbox-talk)
- [Safety Incident Report](https://briq.ai/acu/object/safety-incident-report)
- [Quality Inspection Checklist](https://briq.ai/acu/object/quality-inspection-checklist)
- [Daily Report (Daily Log)](https://briq.ai/acu/object/daily-report)
- [Certification & Training Record](https://briq.ai/acu/object/certification-training-record)
- [CPM Schedule](https://briq.ai/acu/object/cpm-schedule)