Upload your existing SWMS — get a compliant one back
Been handed a template SWMS that doesn't match the job? Principal contractor knocked it back 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 model WHS-aligned SWMS — HRCW activities, hazards, control measures using the hierarchy of controls, PPE and sign-on register. 100+ industries supported.
Australia (SWMS) example document — Tenancy 3 Commercial Fit-Out — 88 Latrobe Street, Melbourne. Client: Latrobe Holdings Pty Ltd. Site: 88 Latrobe Street, Tenancy 3, Melbourne, VIC 3000. Scope: Cat-B fit-out of an existing 220 m² ground-floor tenancy: demolition of partitions, new steel-stud partitioning, suspended grid ceiling, joinery, electrical and data first/second fix, painting and floor coverings. Works occur during occupied-building hours under a building-manager permit. SWMS prepared because HRCW (work > 2 m on scissor lifts and powered mobile plant) is involved.
Full version
Drop in a PDF, Word doc or old SWMS
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready SWMS 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 WHS coordinator would — pulls out the real task and site context, drops the boilerplate, and rebuilds the sections a principal contractor or WHS regulator 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 SWMS that doesn't cover the actual HRCW activity.
- The principal contractor rejected the SWMS and won't allow site access.
- The document is missing the hierarchy of controls or a sign-on register.
- You need model WHS 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 compliant SWMS.
PCBU + contractor details
PCBU name, ABN, address and contact — kept verbatim from the uploaded file.
Project + site context
Project name, site address, principal contractor and access dates pulled from the document.
HRCW activity + scope
The high-risk construction work activity — extracted and matched to WHS Regulation 291.
Hazards + risks
Listed hazards are kept; missing ones inferred from the task (fall, mobile plant, structural collapse, confined space).
Hierarchy of controls
Each hazard is worked through elimination → substitution → engineering → admin → PPE — not a PPE-only cop-out.
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 principal contractors check first.
Emergency + sign-on
First aid, rescue, notifiable incident procedure and the worker sign-on register set up for signatures.
Gap prompts
Riskora flags anything the uploaded file was missing — SDS, permit-required confined space, plant registration — before issue.
From uploaded PDF to a model WHS-aligned SWMS
A generic template becomes a job-specific document with HRCW activities, hazards, hierarchy-of-controls measures and sign-on — ready for the principal contractor.
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 the model WHS Regulations (Chapter 6.3, s.291–299) and state regulators expect — HRCW, hazards, hierarchy of controls, PPE, sign-on register.
What your SWMS 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 SWMS.
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 SWMS 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 SWMS back
Drop in the PDF or Word file. Riskora rebuilds it as a model WHS-aligned SWMS with HRCW activities, controls and sign-on register.
Drop in a PDF, Word doc or old SWMS
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready SWMS 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.