Upload your existing JSA — get a HSWA-ready one back
Working from a template JSA that doesn't match the actual task? Main contractor knocked back the paperwork before site access? Drop the PDF or Word file in. Riskora reads the whole document, keeps your PCBU, project and scope, and rebuilds it as a structured JSA / Task Analysis — hazards, controls using the hierarchy, PPE, emergency response and sign-on — the way HSWA 2015 and WorkSafe NZ expect. 100+ industries supported.
New Zealand (JSA) example document — Kitchen Reconfiguration & Beam Install — 42 Tinakori Road, Wellington. Client: Mr & Mrs Henderson (Private Client). Site: 42 Tinakori Road, Thorndon, Wellington 6011. Scope: Removal of a load-bearing internal wall in an existing 1910 weatherboard villa, installation of a 250 UB engineered steel beam to form a 4.8 m opening, replacement of kitchen joinery, services first/second fix, and minor strip-out of pre-2000 sheet linings. Works occur in an occupied dwelling within a Heritage Area 1 zone.
Full version
Drop in a PDF, Word doc or old JSA
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready JSA around it.
- PDF · Word · TXT
- Company + scope kept
- Free to start
- No signup to preview
- Done in ~60 seconds
Riskora reads the document the way an experienced H&S officer would — pulls out the real task and site context, drops the boilerplate, and rebuilds the sections a PCBU or WorkSafe inspector expects to see.
- 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've a template JSA that doesn't cover the actual task or notifiable work.
- The main contractor rejected the Task Analysis before site access.
- The document is missing the hierarchy of controls or a sign-on register.
- You need HSWA 2015 structure without rewriting the whole file.
What Riskora extracts from the file you upload
The uploaded document usually has the raw material — PCBU, site, scope, some hazards. Riskora keeps what's yours and rebuilds the rest into a structured JSA / Task Analysis.
PCBU + officer details
PCBU name, address and named officer — kept verbatim from the uploaded file.
Project + site context
Project name, site address, main contractor and access dates pulled from the document.
Task + scope
The actual task — extracted from method paragraphs, scopes and bullet lists.
Hazards (kept + inferred)
Listed hazards are kept; missing ones inferred from the task (fall, mobile plant, hazardous substances, confined space).
Hierarchy of controls
Each hazard is worked through elimination → substitution → engineering → admin → PPE — the WorkSafe NZ expectation.
PPE + fit-for-purpose
Hi-vis, boots, harness, gloves, eye, RPE — matched to the extracted task, with AS/NZS references.
Sequence of work
Numbered steps with the responsible person per step — the section main contractors check first.
Emergency + sign-on
First aid, rescue, WorkSafe notifiable event procedure and the worker sign-on register set up for signatures.
Gap prompts
Riskora flags anything the uploaded file was missing — SDS, confined space entry permit, notifiable work — before issue.
From uploaded PDF to a HSWA-aligned JSA
A generic template becomes a job-specific document with hazards, hierarchy-of-controls measures, PPE and sign-on — ready for the main contractor and WorkSafe.
Not a paragraph rewrite. Not a filename change.
Generic AI tools paraphrase your file into long prose. Riskora reads the uploaded document, extracts the underlying task and site context, and rebuilds the sections HSWA 2015 and WorkSafe NZ expect — hazards, hierarchy of controls, PPE, sign-on register.
What your JSA 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 JSA.
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 JSA 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.
Upload the file — get a proper JSA back
Drop in the PDF or Word file. Riskora rebuilds it as a HSWA-aligned JSA / Task Analysis with hazards, controls, PPE and sign-on register.
Drop in a PDF, Word doc or old JSA
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready JSA around it.
- PDF · Word · TXT
- Company + scope kept
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.