RAMS for Slate and Tile Roofing UK — Access, Edge Protection & Weather Controls

Riskora structures a roofing RAMS around the parts reviewers care about — fragile surfaces, edge protection, weather triggers, rescue arrangements and sign-off — ready to issue. 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

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
You're probably here because…
  • Principal contractor returned the RAMS for a weak rescue plan
  • Fragile surface controls missing or vague on the last submission
  • No weather stop-work triggers documented
  • Need a method statement specific to this roof type and access
What to add to the box
  • Roof type and access method (scaffold / MEWP / ladder)
  • Client or principal contractor's email or scope
  • Survey notes on fragile surfaces and edges
  • Existing roofing RAMS to update for this job
  • Site address and conditions
Inside the document

What a Riskora roofing RAMS includes

The sections principal contractors, clients and reviewers expect on a roofing RAMS.

Site & roof details

Site, roof type, condition and survey notes.

Access method

Scaffold, MEWP, ladders or roof access — and how it is inspected.

Work-at-height controls

Edge protection, harness, fall arrest, exclusion zones and competent supervision.

Fragile surface controls

Identification, marking, walk boards and harness/anchor arrangements.

Weather triggers

Wind, rain and heat triggers — when to stop work and re-secure the area.

Tools, equipment & PPE

Equipment in use, inspection requirements and roofing-specific PPE.

Rescue & emergency

Rescue arrangements for fall arrest, suspension trauma and incident response.

Briefing & sign-off

Crew briefed, signed on and recorded against the document.

Example output

See the roofing RAMS you'll issue

Built around the high-risk parts of roof work — access, fragile surfaces, edge protection, weather and rescue — set out in clean tables and method steps. Preview the structure before you build yours.

Not a blank template

Not a generic RAMS with the word 'roof' added.

Generic templates skip the parts that matter on a roof. A real roofing RAMS identifies fragile surfaces, sets out edge protection, documents weather triggers and includes a rescue plan with names, equipment and timescales. Riskora prompts every one of those.

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

Build your roofing RAMS now

Describe the roof type, the access plan or the client's email. Riskora structures the RAMS around the work-at-height controls reviewers expect to see.

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

FAQ

Questions for this exact situation

Site and roof details, access method, work-at-height controls, fragile surface and edge protection arrangements, weather triggers, tools and equipment, manual handling, public/occupier interface, rescue arrangements and briefing/sign-off.

Where workers use fall arrest, suspension trauma is a real risk. A documented rescue arrangement — who responds, with what equipment, in what timescale — is normally expected by principal contractors.

Yes. Fragile surfaces are a major cause of serious roof-work incidents. The RAMS should identify which surfaces are fragile, how they will be protected and how access will be controlled.

Roof work normally needs both a risk assessment and a method statement — combined as a RAMS for most UK contractor workflows.

No tool can. Riskora helps you produce a clearer, more reviewable roofing RAMS, but acceptance always depends on the client, the actual conditions on site and competent-person review.

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.