Build RAMS for site managers

Site managers get stuck between subbies who submit templated RAMS and PCs who won't accept them. Riskora gives you a fast review, brief and sign-on workflow — plus the ability to rebuild any RAMS that isn't fit for site. 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.

  • Free to start
  • No signup to preview
  • Done in ~60 seconds

Riskora structures your brief into a site-specific RAMS for site managers — hazards, controls, PPE, permits, method steps and emergency arrangements. Not a generic template.

  • 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…
  • Pre-start in 45 minutes and one subbie's RAMS still isn't fit for brief.
  • PC won't accept subbie RAMS marked as 'generic'.
  • You need sign-on captured before crews go past the gate.
  • New crew turned up unbriefed — you need something on paper today.
What to paste into the box
  • Scope of works for the site managers
  • A client email, PQQ note or RFI
  • A site manager's WhatsApp or text message
  • Pre-start meeting notes or programme
  • A previous RAMS to update or improve
  • Drawings, permits or site rules to align with
Inside the document

Inside a Riskora RAMS for site managers

Every section is built around the actual task — not boilerplate. These are the task-specific items Riskora drops in by default for site managers, ready for you to refine and sign off.

Task-specific hazards

Subcontractor RAMS not site-specific · Unbriefed operatives on site · Missing sign-on / competence evidence · Interface between overlapping packages · Revisions issued without re-brief · Permits in place but not held at task

Controls matched to each hazard

Structured review of every submission before brief · Pre-start toolbox with signed brief record · Sign-on register captured against current version · Interface controls between packages (permit + sequence) · Any revision triggers a re-brief and re-sign · Daily walk with escalation to PC

Likely PPE

Standard site PPE (helmet, hi-vis, boots, gloves) · Package-specific PPE per RAMS

Permits & hold points

Site induction · Hot works, height, isolation, excavation per activity

Emergency arrangements

Muster point + assembly · Named first aider on shift · Nearest A&E route · Escalation to PC + client

Method steps & sign-off

Numbered method sequence with responsible person, briefing register, and competent reviewer sign-off before work starts.

Example output

A site-ready RAMS for site managers

See how Riskora structures hazards, controls, PPE, permits and method steps into a single document specifically for site managers — edit anything before you issue it.

Not a blank template

Not a generic Site Managers template

Most "RAMS for site managers" templates online are blank docs you still have to fill in, or AI prose with no structure. Riskora reads your brief and writes the right sections — hazards, controls, PPE, permits, method steps, emergency arrangements and sign-off — built for the actual task on the actual site.

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

Start your site managers RAMS now

Describe the job details, site message or scope of works. Riskora builds the rest around the task.

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

FAQ

Questions for this exact situation

Riskora produces a briefable summary from any RAMS — a single page you can talk to at pre-start. Sign-on is captured on the same doc so the paperwork is done before crews leave the meeting.

Reject with the review checklist. If it can't be fixed in time, build a temporary RAMS in Riskora yourself for the specific activity so the crew can start, then get the subbie's version updated to replace it.

Yes — any material change triggers a re-brief and re-sign. Riskora versions the doc and starts a fresh sign-on for you.

Yes — the builder works on mobile so you can review, brief and capture sign-on from the site cabin or the deck.

Yes — your first RAMS pack is free, no card.

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.