Last-minute job and need RAMS?

Build a structured safety document before you attend site or send it to the client. 100+ industries supported.

UK (RAMS) example document — Two-Storey Rear Extension — 14 Birchwood Lane, Reading. Client: Mr & Mrs A. Whitfield (Private Client). Site: 14 Birchwood Lane, Reading, RG1 5JT. Scope: Construction of a two-storey rear extension (6.4m × 4.2m) to an existing semi-detached dwelling. Works comprise breaking out of existing rear elevation, trench-fill foundations to 1.0m, traditional cavity blockwork to first floor, pre-stressed concrete lintels, timber roof structure with natural slate finish, plus alterations to existing rear wall to form structural opening with rolled steel joist (RSJ 203×102 UB23). Works programmed over 9 weeks with a peak site team of 6 operatives. Hazards assessed: Manual handling — blocks, lintels, plasterboard, Working at height — independent scaffold & roof structure, Buried services strike during excavation, Collapse of excavation / trench wall, Hand-arm vibration (HAVS) — breaking out, drilling, Silica dust — cutting blocks, brick, concrete, Vehicle/pedestrian segregation — narrow domestic street.

Example UK (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

For contractors who need paperwork fast without digging through old templates.

  • 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…
  • Picked up a job overnight — needs RAMS by morning.
  • Subcontractor pulled out — taking over their works with no paperwork.
  • Reactive call-out with new hazards not in our old RAMS.
  • Short-notice weekend works that still need documentation.
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

Don't send a copied old RAMS

Last-minute does not have to mean generic. Riskora uses the job details you provide to structure the document around the actual work, site, hazards and controls.

Start from the job

Add site details

Include hazards

Strengthen controls

Add emergency arrangements

Review before download

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

  • 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 RAMS 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

Don't send a copied old RAMS

Riskora structures the document around the actual work, site, hazards and controls — not a recycled file from last year.

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

FAQ

Questions for this exact situation

Yes. Paste what you know about the job and Riskora builds a structured RAMS quickly so you can review and download it before mobilising.

Usually yes. Editing an old RAMS often leaves the wrong site name, wrong hazards or missing controls. Riskora structures the document around the new job instead.

Paste what you have. Riskora prompts for anything missing — site, hazards, PPE, controls and emergency arrangements — so you don't ship gaps.

Yes. Every field is editable in the builder and the document remains in your account so you can update before downloading.

Yes. Many contractors use Riskora for short-notice subcontractor RAMS, either for their own attendance or to standardise paperwork across trades.

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.