Upload your existing Safety Statement — get a HSA-ready one back
Working off a template that doesn't match your work? Sent a Safety Statement the main contractor won't accept on site? Drop the PDF or Word file in. Riskora reads the whole document, keeps your company, project and scope, and rebuilds it as a Section 20 Safety Statement — hazard identification, risk assessments, control measures, method statement and sign-off — the way the HSA and main contractors expect. 100+ industries supported.
Ireland (RAMS) example document — Single-Storey Side Extension — 18 Glasnevin Avenue, Dublin. Client: Mr & Mrs Kavanagh (Private Client). Site: 18 Glasnevin Avenue, Dublin 11, D11 X2K7. Scope: Construction of a 5.0 m × 3.6 m single-storey side extension: strip foundations to 900 mm, cavity blockwork superstructure, flat warm roof with single-ply membrane, rooflight and new structural opening into the existing kitchen. Works programmed over 9 weeks with a peak site team of 4 operatives.
Full version
Drop in a PDF, Word doc or old Safety Statement
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready Safety Statement 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 a competent person under Section 18 would — pulls out the real task and site context, drops the filler, and rebuilds the sections a main contractor or PSCS will actually accept.
- 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 generic Safety Statement template that doesn't match the actual job.
- The PSCS or main contractor rejected the paperwork before site access.
- The document is missing hazard IDs, risk ratings or a proper method statement.
- You need Section 20 structure without rewriting the whole file.
What Riskora extracts from the file you upload
The uploaded document usually has the raw material — company, site, scope. Riskora keeps what's yours and rebuilds the rest into a structured Safety Statement.
Company + competent person
Company name, address, competent person under Section 18 — kept verbatim from the uploaded file.
Project + site context
Project name, location, main contractor, access window and dates pulled from the document.
Scope of works
The actual task — extracted from method paragraphs, scopes and bullet lists.
Hazard identification
Listed hazards are kept; missing ones are inferred from the task (height, chemical agents, traffic, lone working).
Risk assessments + controls
Each hazard gets a likelihood × severity rating and a mapped control measure.
PPE + welfare
Task-specific PPE, welfare arrangements and induction requirements.
Method statement
Numbered sequence with the responsible person per step — main contractors read this first.
Emergency + sign-off
First aid, escalation, HSA notifiable incident procedure and briefing register set up.
Gap prompts
Riskora flags anything the uploaded file was missing — supervisor, chemical agents assessment, emergency arrangements — before issue.
From uploaded PDF to a Section 20-aligned Safety Statement
A generic template becomes a site-specific document with hazard identification, risk assessments, method statement and sign-off — ready for the main 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 Section 20 of the Safety, Health and Welfare at Work Act 2005 requires — hazard identification, risk assessments, method, emergency arrangements and sign-off.
What your Safety Statement 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 Safety Statement.
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 Safety Statement 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 Safety Statement back
Drop in the PDF or Word file. Riskora rebuilds it as a HSA-aligned Safety Statement with risk assessments, method statement and sign-off.
Drop in a PDF, Word doc or old Safety Statement
Riskora reads it end-to-end, keeps what's yours (company, site, scope) and rebuilds a structured, audit-ready Safety Statement 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.