HSA inspector asked for your RAMS?

Riskora builds a structured, site-specific RAMS from the job you paste — aligned to SHWWA 2005 and the 2013 Construction Regulations. 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.

Example Ireland (RAMS) front cover produced by Riskora
Try the new compact mode. Same document, just more compact

Full version

Preview first. No card needed. Download when you're happy.

  • Site-specific structure
  • Editable before download
  • Ready to issue today

Riskora helps structure the document. A competent person must review before it is produced to the HSA inspector.

  • 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're probably here because…
  • HSA inspector unannounced visit — needs current RAMS.
  • Notice of improvement flagged missing RAMS.
  • PSCS on site asked for RAMS ahead of HSA visit.
What to add to the box
  • 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
Inside the document

What HSA inspectors expect

Every section is structured around the brief you paste — not boilerplate. You confirm what applies to the site before you send the RAMS.

SHWWA 2005 alignment

General duties and risk assessment obligations.

2013 Construction Regs

PSDP / PSCS duties referenced where applicable.

Site-specific hazards

Traced to actual works, not template.

Numbered method sequence

Steps with responsible person.

Rescue + emergency plan

Height rescue, first aider, nearest hospital.

Competent-person sign-off

Author, reviewer, date, version.

Example output

A site-ready RAMS, structured

See how Riskora shapes your brief into a RAMS your client or site manager will accept — every section structured, edit anything before you send it.

Not a blank template

Why a RAMS template isn't enough today

A blank template still leaves every hazard, control, method step and emergency arrangement for you to write. Riskora structures a site-specific RAMS around the brief you paste — the sections principal contractors and site managers actually expect.

Inside the document

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.

Before & after

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.

Before

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.
After

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.
How it works

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.

  1. 1
    Paste 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.

  2. 2
    Riskora structures the document

    Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.

  3. 3
    Review, edit and download

    You stay in control of every section. Tweak anything, then download a clean PDF or share a link.

  4. 4
    Brief the team and record sign-off

    Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.

Built for site reality

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.
Start in seconds

HSA visit today or tomorrow?

Paste the job details — Riskora rebuilds the RAMS around what applies to the site.

Preview first. No card needed. Download when you're happy.

FAQ

Questions for this exact situation

No document guarantees acceptance — that's the inspector's call. Riskora produces a structured, Ireland-specific RAMS. Your competent person confirms before it is produced.

Yes — Irish framework references (SHWWA 2005 and the 2013 Construction Regs), PSDP / PSCS duties, and site-language defaults.

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.