Does OSHA require a JHA? Short answer — and a generator you can use today

OSHA doesn't mandate JHAs by that name, but many OSHA standards require a documented hazard assessment before work — and every GC expects a JHA. Riskora builds an OSHA-aligned JHA in minutes. 100+ industries supported.

US (JHA) example document — Rooftop HVAC Unit Changeout — 1400 Larimer Commerce Center, Denver. Client: Larimer Commerce Center Property Management. Site: 1400 Larimer Commerce Center, Denver, CO 80202. Scope: Removal and replacement of two 15-ton packaged rooftop units on an occupied four-story commercial building: refrigerant recovery, electrical lockout, 90-ton crane lift from a permitted lane closure, curb adaptation, duct transition welding under hot work permit, gas reconnection and commissioning. Works programmed over 5 working days with a crew of 5.

Example US (JHA) front cover produced by Riskora
Try the new compact mode. Same document, just more compact

Full version

Preview first. No card needed. Download when you're happy.

  • Free to start
  • No signup to preview
  • Done in ~60 seconds

Not a blank template. Not loose AI prose. A structured JHA — the sections a competent reviewer expects to see — from a brief you can paste in under a minute.

  • UK · IE · US · CA · AU · NZ
  • RAMS · SWMS · JHA · JSA · COSHH · Task Analysis · Toolbox Talks
  • Site-specific — not a blank template
  • First document free · No card required
You're probably here because…
  • Your GC is asking for a JHA — you're not sure if OSHA actually requires one.
  • You need to point to the OSHA standards that back the JHA.
  • An audit is asking whether your JHAs are documented.
  • You want a JHA aligned with OSHA 3071 guidance.
What to add to the box
  • A client email asking for paperwork
  • A site manager's WhatsApp or text message
  • Scope of works or job description
  • Tender or PQQ notes for the package
  • A previous RAMS to update or improve
Inside the document

What Riskora builds for this JHA

Every section is built around your actual scope of work and the framework this page is about — not boilerplate. You confirm what applies to the site before you issue it.

OSHA-aligned structure

Follows OSHA Publication 3071 four-step method.

Task step breakdown

Numbered steps in the actual sequence workers perform them.

Hazards per step

Each step gets identified hazards — physical, chemical, ergonomic.

Hierarchy of controls

Elimination → substitution → engineering → admin → PPE.

PPE by task step

Task-appropriate PPE aligned with 1910.132 / 1926.28.

Sign-off + toolbox

Named competent person, crew sign-on for the pre-task briefing.

Example output

A site-ready JHA, ready to review

See how Riskora shapes your brief into a JHA your reviewer will accept — every section structured, edit anything before you issue it.

Not a blank template

Not a template. Not loose AI prose. A structured JHA.

Most 'JHA template' downloads are blank docs you still have to fill in, and generic AI tools produce loose prose a competent reviewer will bin. Riskora produces a structured JHA — with the sections the relevant framework expects — from a brief you can paste in under a minute.

Inside the document

What your JHA actually contains

Riskora builds a structured, client-facing document — not a generic AI paragraph. Every section is shaped around your job, your site and your team.

  • Hazards

    Task-specific hazards for the job, captured row by row — not a generic list pulled from an old JHA.

  • Controls

    Control measures mapped to each hazard with residual risk scoring after controls are applied.

  • PPE

    PPE requirements tied to the activity and site, ready to brief to the team.

  • Method steps

    Step-by-step method statement structured around how the work is actually sequenced on site.

  • Emergency arrangements

    First aid, rescue plan, emergency contacts and site-specific escalation routes.

  • COSHH prompts

    Substance prompts when the work involves chemicals, dusts, fumes or sealants — flagged early, not missed at review.

  • Sign-off

    Operative sign-off captured against the document — names, dates and acknowledgement of the brief.

  • Version history

    Every change tracked so you can show what was issued, when, and which version the team signed.

  • Approval status

    Clear approval state on every document — draft, in review, approved, issued — visible across the team.

  • Audit trail

    Who created it, who reviewed it, who signed it. A complete trail you can hand to a principal contractor or auditor.

Before & after

From copied-and-pasted to site-specific

The reason JHA get rejected is rarely the format — it's that the document is obviously generic. Riskora rebuilds it around this job, this site and this task.

Before

Generic template copied from an old job.

  • • Hazards and controls that don't match this site or task.
  • • Method steps written for a different sequence of work.
  • • No emergency arrangements specific to the location.
  • • Client flags it as generic and asks for a rewrite.
After

Site-specific document structured around this job, site and task.

  • • Hazards captured from the actual scope you pasted in.
  • • Method steps sequenced for how the work runs on site.
  • • Emergency arrangements and rescue plan tied to the location.
  • • Approved internally, briefed to the team, signed off and stored.
How it works

From job details to signed-off document

A four-step workflow used by contractors, consultants and safety teams to turn informal job details into client-ready safety paperwork.

  1. 1
    Paste job details

    Drop in a client email, a WhatsApp from the site manager, a scope of works or a tender note. Anything that describes the job.

  2. 2
    Riskora structures the document

    Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.

  3. 3
    Review, edit and download

    You stay in control of every section. Tweak anything, then download a clean PDF or share a link.

  4. 4
    Brief the team and record sign-off

    Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.

Built for site reality

Built by people who've written this paperwork on real sites

Riskora is built by a founder with hands-on site and document experience — designed for contractors, consultants and safety teams who need to issue, brief and prove safety paperwork without losing a day to admin.

  • Built for contractors, consultants and teams
    Solo trades, principal contractors and in-house safety teams all run on the same workflow.
  • Supports multiple countries
    UK, Ireland, Australia, New Zealand, US and Canada — wording and document types match the local standard.
  • Not just documents
    Sign-off, approvals, version history and an audit trail — the management workflow around the paperwork.
Start in seconds

Build your JHA now — done in minutes

Describe the job details, an email from the client, or a rough scope of works. Riskora shapes the rest around the actual task so you can review, edit and issue today.

Preview first. No card needed. Download when you're happy.

FAQ

Questions for this exact situation

OSHA does not have a single standard mandating JHAs by name. However, many OSHA standards require hazard assessment or written procedures — fall protection (1926 Subpart M), PPE (1910.132), lockout/tagout (1910.147), confined spaces (1910.146 / 1926 Subpart AA), respiratory protection (1910.134). In practice, OSHA inspectors and GCs treat a documented JHA as expected.

OSHA Publication 3071 — Job Hazard Analysis — sets out the four-step method (select the job, break it into steps, identify hazards, determine controls).

Inspectors commonly ask for the documented hazard assessment referenced by the applicable standard. A JHA is the format most employers use to satisfy this.

For routine low-hazard tasks, a general JHA can cover the activity. For high-hazard, non-routine or changing work, a task-specific JHA is expected before work starts.

Riskora helps structure a site-specific safety document. It does not replace competent review, site supervision, client requirements or legal duties. Always check the final document before issue.