If you’ve worked across different job sites, you’ve probably seen the terms JHA and AHA used almost interchangeably — and then seen a client or auditor insist there’s a difference. Both are hazard analysis tools that break a task into steps, identify the hazards in each step, and define controls. The distinction is mostly about terminology, context, and expectations rather than a fundamentally different method. Here’s how to think about when each label applies.
What a JHA is
A Job Hazard Analysis (JHA) — sometimes called a Job Safety Analysis (JSA) — breaks a specific job or task into its component steps, identifies the hazards associated with each step, and specifies the controls or safe work practices that address them. It’s the workhorse document of everyday safety planning: focused on a task, written in plain language, and used to brief the crew before work begins.
What an AHA is
An Activity Hazard Analysis (AHA) follows the same step / hazard / control logic but is the term used most often on federal and military construction projects — particularly work governed by the U.S. Army Corps of Engineers EM 385-1-1 safety manual. AHAs typically carry additional expectations: listing the competent or qualified persons for the activity, the training and equipment required, and inspection requirements. In practice, an AHA is a more formally structured cousin of the JHA.
The practical difference
The analysis method is essentially the same — break the work into steps, find the hazards, control them. What changes is the audience and the required fields. A JHA satisfies most general-industry and private construction expectations. An AHA is what you produce when the contract or governing manual specifically calls for one, and it usually demands more detail around personnel qualifications, equipment, and inspection.
When do you need each?
Use a JHA for routine task-level hazard planning on typical job sites, and whenever you want a clear, briefable safety document for a crew. Use an AHA when a contract, a government client, or a governing safety manual (such as EM 385-1-1) explicitly requires one — and check that specification early, because retrofitting a stack of JHAs into AHA format under deadline pressure is where teams lose time and consistency.
Keeping them consistent
Whichever term applies, the value comes from consistency: the same steps analyzed the same way, controls that map to real hazards, and a document someone can actually follow. Our JHA/AHA Procedure Builder structures the step-hazard-control logic so the same task is documented the same way every time. It’s a documentation framework only — it does not certify compliance, authorize work, or replace competent-person judgment.
Leave a Reply