Build RAMS for working at height
Working at height RAMS must show the hierarchy of control was followed — avoid, prevent, mitigate. Riskora structures the RAMS with collective protection chosen first, fall arrest justified where used, and a written rescue plan. 100+ industries supported.
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 working at height — 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
- Any work above 2m and the principal contractor wants RAMS first.
- MEWP hire confirmed — operator needs the rescue plan documented.
- Last submission rejected for 'hierarchy not demonstrated'.
- Public area below — exclusion zone needs to be in writing.
- Scope of works for the working at height
- 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 a Riskora RAMS for working at height
Every section is built around the actual task — not boilerplate. These are the task-specific items Riskora drops in by default for working at height, ready for you to refine and sign off.
Task-specific hazards
Fall from height — edge, ladder, MEWP basket, platform · Falling tools, materials or fixings onto people below · Fragile surfaces — rooflights, asbestos cement, old skylights · Equipment failure — ladder, MEWP, scaffold · Adverse weather affecting stability · Inadequate ground for MEWP outriggers · Suspension trauma in fall-arrest event
Controls matched to each hazard
Hierarchy of control — avoid (do it from ground), prevent (collective edge protection), then mitigate (harness) · MEWP / scaffold / podium chosen over ladder where reasonably practicable · Edge protection or harness with rated anchor and restraint · Exclusion zone with hi-vis barriers and banksman · Pre-use inspection (LOLER for MEWPs, weekly for scaffold) · Wind speed and weather hold thresholds · Written rescue plan with rescue lead and rescue equipment
Likely PPE
Hard hat with chin strap · Full body harness + shock-absorbing lanyard · Restraint lanyard for MEWP work · Safety boots · Hi-vis vest · Cut-resistant gloves
Permits & hold points
Permit to work at height (site-issued) · MEWP authorisation + IPAF cards on file · Roof access permit from building owner · Public area / pavement licence
Emergency arrangements
Written rescue-from-height plan (not 'call 999') · Pre-rigged rescue kit or second MEWP on site · Rescue lead named and trained · Suspension-trauma awareness in first aid brief · Emergency contact list + A&E grid reference
Method steps & sign-off
Numbered method sequence with responsible person, briefing register, and competent reviewer sign-off before work starts.
A site-ready RAMS for working at height
See how Riskora structures hazards, controls, PPE, permits and method steps into a single document specifically for working at height — edit anything before you issue it.
Not a generic Working at Height template
Most "RAMS for working at height" 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.
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.
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.
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.
Start your working at height 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.
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.
Related Riskora pages
- Working at height RAMS (UK)Full WAH Regs guide
- RAMS for roof repairsCommon WAH scenario
- RAMS for scaffolding erectionCollective protection setup
- RAMS for window cleaningCradle / pole / abseil
- RAMS generatorBuild any RAMS from a brief
- Method statement generatorMethod statement only
- Risk assessment generatorRisk assessment only