Build an Irish risk assessment in minutes
Section 19 of the 2005 Act requires a written, activity-specific risk assessment. Riskora structures it — hazards identified, controls applied via the General Principles of Prevention, before and after risk visible. 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
Preview first. No card needed. Download when you're happy.
- Free to start
- No signup to preview
- Done in ~60 seconds
Preview before signup · First document free · No card required
- 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
- PSCS or Safety Statement update needs a written RA.
- An activity-specific RA is missing from the Safety Statement.
- Manual handling, DSE, noise or chemical RA is overdue.
- Inspector or auditor flagged generic risk assessments.
- 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's in every Irish risk assessment
Job-specific hazards
Hazards drawn from the task, the site and the scope you describe — not a stock list.
Hierarchy of controls
Elimination first, PPE last. Initial and residual risk shown side by side.
Step-by-step method
Sequenced steps with a person responsible for each, written for this risk assessment.
PPE & equipment
Task-specific PPE, plant and inspection requirements.
Emergency arrangements
First aid, fire, spill and rescue arrangements specific to the work.
Chemicals & substances
Substance prompts appear when materials in scope need a hazardous-substance assessment.
Permits & hold points
Hot work, working at height, confined space and inspection hold points where they apply.
Briefing & sign-off
Pre-start briefing register, version lock and an audit-ready workflow.
Client-ready risk assessment PDF
Branded, paginated PDF you can issue without reformatting.
A Section 19 risk assessment, structured
Hazard identification, persons exposed, controls in the Schedule 3 order, before-and-after risk and a competent-person sign-off line — all in one structured document.
Riskora isn't a blank template or a generic AI text generator
Riskora asks for your job and site context, then structures a client-ready, site-specific Safety Statement: hazards, controls, method steps, PPE, emergency arrangements and sign-off — not a paragraph of AI prose. You stay in control of every section and the output is built for an audit-ready workflow.
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.
Describe the job details — get a structured Safety Statement
Describe the job details, scope of works, email or WhatsApp message. Riskora structures the rest.
Preview first. No card needed. Download when you're happy.
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.