OSHA-compliant Job Hazard Analysis — built around your actual task
A useful JHA breaks the job into steps, identifies hazards for each step, and applies controls in hierarchy order. Riskora shapes an OSHA-aligned JHA for safety-manager and general-contractor review. 100+ industries supported.
- 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
- Your GC is asking for a site-specific JHA before mobilization.
- Your existing JHA is a generic copy-paste from another project.
- You need a JHA that lines up with OSHA 3071 guidance.
- An OSHA inspection is coming and your paperwork is thin.
- 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
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.
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, not blanket site PPE.
Emergency response
First aid, muster, nearest hospital, EAP alignment.
Sign-off + toolbox
Named competent person, crew sign-on for the pre-task briefing.
A site-ready JHA, ready to review
See how Riskora shapes your brief into a JHA designed for competent review — every section structured, with everything editable before issue.
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.
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.
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.
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.
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.
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.
- 1Paste 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.
- 2Riskora structures the document
Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.
- 3Review, edit and download
You stay in control of every section. Tweak anything, then download a clean PDF or share a link.
- 4Brief the team and record sign-off
Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.
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.
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.
Questions for this exact situation
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.