How to Write a RAMS Document

If you work in construction, contracting, or any hands-on trade in the UK, you've been asked to produce a RAMS. Probably many times. It's one of those documents that everyone needs but few people enjoy writing — and getting it wrong means rejected submissions, delayed site access, and wasted time.

This guide is the definitive reference for writing RAMS documents in the UK. It covers structure, content, real-world examples, common rejection reasons, and includes a checklist you can use on every project.

What does RAMS stand for?

RAMS stands for Risk Assessment Method Statement. It combines two documents into one:

• Risk Assessment — identifies hazards, evaluates the likelihood and severity of harm, and defines control measures
• Method Statement — describes the safe system of work step by step, covering the sequence of operations, resources, and safety precautions

Together, these answer two questions: what could go wrong? and how will we do the work safely?

RAMS aren't a named legal requirement, but they support compliance with the Management of Health and Safety at Work Regulations 1999, the Construction (Design and Management) Regulations 2015, and the Health and Safety at Work Act 1974. In practice, principal contractors won't grant site access without one. For more on the legal framework, see our guide to risk assessment legal requirements in the UK.

The complete structure of a RAMS document

There's no legally mandated format, but the sections below represent industry best practice across UK construction and contracting. Missing any of these is a common reason for rejection.

1. Project information

Site address, client name, principal contractor, your company name, project reference, document reference number, and the date. This seems basic, but missing or incorrect project details are a surprisingly frequent reason documents get sent back.

2. Scope of works

A clear, specific description of the work being carried out. Avoid vague descriptions. "Electrical installation" tells the reviewer nothing useful. "First fix electrical installation to ground floor residential units, Block C, including containment, cabling, and back-box installation" tells them exactly what you're doing, where, and what it involves.

3. Hazard identification

List every significant hazard associated with your specific task. Think about what could realistically cause harm in the conditions you'll be working in. Common categories include:

• Working at height (even from step ladders)
• Manual handling of heavy or awkward loads
• Electrical contact — both your own work and existing services
• Slips, trips, and falls
• Dust, noise, and vibration exposure
• Interface with other trades or site traffic
• Confined spaces, if applicable

The key is relevance. A hazard list that includes "shark attack" or "volcanic eruption" for a Birmingham refurbishment project suggests copy-pasting rather than thinking.

4. Risk evaluation

For each hazard, assess:

• Likelihood — how probable is it that this hazard will cause harm? (1 = very unlikely, 5 = almost certain)
• Severity — if it does cause harm, how serious? (1 = minor injury, 5 = fatal)
• Risk score — likelihood × severity. This gives you a prioritised view of which risks need the most attention.

Score both before controls (inherent risk) and after controls (residual risk). This demonstrates that your controls actually reduce the risk level.

5. Control measures

For each hazard, describe exactly what you'll do to reduce the risk. Follow the hierarchy of controls:

1. Eliminate — can the hazard be removed entirely?
2. Substitute — can a less hazardous alternative be used?
3. Engineering controls — physical measures (guardrails, LEV, barriers)
4. Administrative controls — procedures, permits, supervision, training
5. PPE — the last line of defence, not the first

Be specific. "Workers will wear appropriate PPE" is meaningless. "All operatives will wear Class 3 hi-vis vests, hard hats with chin straps, steel-toe boots, and safety glasses during all site activities. RPE (FFP3 masks) will be worn during dust-generating activities" gives the reviewer confidence you've thought it through.

6. Method statement

The step-by-step procedure for carrying out the work safely, written in chronological order. Each step should be specific enough that someone unfamiliar with the task could follow it. Include:

• Preparation and set-up
• Each work stage in sequence
• Quality checks and hold points
• Clean-up and demobilisation
• Handover arrangements

Link each method step to the relevant hazards from the risk assessment. This cross-referencing demonstrates that the safe system of work is designed to manage the identified risks — not written as a separate, disconnected document. For more guidance on structuring this section, see our guide on what must be included in a method statement.

7. PPE requirements

List all required personal protective equipment, specifying standards where relevant (e.g. EN 397 for hard hats, EN ISO 20345 for safety footwear). Distinguish between site-wide PPE requirements and task-specific PPE.

8. Emergency procedures

What happens when things go wrong. Cover:

• First aid arrangements and nearest first aider
• Fire evacuation procedures and assembly point
• Task-specific emergencies (rescue from height, electrical isolation, chemical spill)
• Emergency contact numbers
• Nearest A&E location

9. Sign-off and review

Document who prepared the RAMS, who reviewed it, who approved it, and the scheduled review date. A RAMS without a review date looks like a document that was written once and filed away — which undermines its credibility with reviewers and inspectors.

Minimum Requirements for a Legally Defensible RAMS Document

While there's no single legal definition of a "compliant" RAMS, this checklist represents the minimum standard expected by principal contractors, health and safety professionals, and regulators across UK construction:

• ☐ Accurate project details (site, client, contractor, dates)
• ☐ Specific scope of works — not a generic description
• ☐ Task-specific hazard identification (not a universal hazard list)
• ☐ Risk scoring with both inherent and residual risk levels
• ☐ Control measures following the hierarchy of controls
• ☐ Specific PPE requirements with standards referenced
• ☐ Sequential method statement linked to identified hazards
• ☐ Emergency procedures including task-specific scenarios
• ☐ Competent person named as author
• ☐ Reviewed and signed off by a responsible person
• ☐ Review date set (and actually honoured)
• ☐ Site-specific — reflects actual conditions, not a previous job
• ☐ Briefed to all workers before work begins

If your RAMS meets every point on this list, it will satisfy the expectations of most principal contractors in the UK and provide a defensible record if questions arise.

Create your RAMS instantly with Riskora →

Common mistakes that get RAMS rejected

These are the patterns that principal contractor reviewers flag most frequently:

• Copy-pasting from previous jobs — the single most common problem. If your RAMS for a roofing job in Manchester reads identically to your RAMS for a drainage job in Bristol, it hasn't been assessed — it's been duplicated.
• Vague control measures — phrases like "appropriate precautions will be taken" or "risks will be managed" add no value. Name the precautions. Describe how they'll be managed. By whom.
• Missing the method statement entirely — many RAMS are actually just risk assessments. Without the method statement, the document is incomplete. The method statement generator helps ensure this section isn't overlooked.
• Generic hazard lists — including every hazard from a master list, regardless of relevance to the task, signals that you haven't actually assessed the work.
• No review date — suggests the document is a one-off effort, not a living part of your safety management.
• Risk scores that don't make sense — rating a "fall from 15m scaffold" as likelihood 1, severity 1 will not pass scrutiny.
• No site-specific detail — references to "the site" without naming it, or weather conditions appropriate to a different region or season.

Tips from the field

Practical advice from people who write, review, and approve RAMS daily:

• Start with the method statement — it's easier to identify hazards once you've mapped out the sequence of work.
• Walk the site before writing — a RAMS written from a desk often misses conditions that would be obvious on a site visit.
• Be specific about roles — "the supervisor" is vague. Name the role and, ideally, the named individual.
• Use plain language — your RAMS will be read by operatives, not academics. Clarity beats complexity.
• Version control matters — if conditions change, issue a new version. Keep superseded versions on record.
• Brief it properly — the best RAMS in the world is useless if the workers haven't seen it. Toolbox talks work.

Using a RAMS generator

If you produce RAMS regularly — for different sites, trades, or clients — writing each one from scratch is inefficient and error-prone. A RAMS generator gives you a structured starting point with relevant hazards and control measures already suggested based on your work type.

This approach is particularly useful for construction RAMS, where you might need separate documents for each trade on a single project. It also helps smaller firms that need professional-quality documentation without dedicated safety staff.

Understanding the difference between a RAMS and a standalone risk assessment matters too — especially when clients use the terms loosely. Our guide on RAMS vs risk assessment clarifies which document you actually need.

Summary

A good RAMS document is specific, structured, and practical. It identifies the real risks of the actual work on the actual site, describes exactly how the work will be done safely, and is briefed to everyone involved. The checklist and structure above provide a reliable framework for getting it right every time. Focus on substance, not length — and review it for every new project.

Where each section of your RAMS comes from in law

Knowing which regulation drives each section of a RAMS helps you explain — and defend — the document under review. The risk-assessment half is mandated by Regulation 3 of the Management of Health and Safety at Work Regulations 1999 ("suitable and sufficient"). The method-statement half evidences the "safe system of work" duty in Section 2 of the Health and Safety at Work etc. Act 1974. On construction, both halves combine to discharge CDM 2015 Regulation 8 and feed up into the principal contractor's plan under Regulation 12.

Activity-specific sections inherit their own regulations: working at height pulls in WAHR 2005 Regulation 6; lifting plans satisfy LOLER 1998 Regulation 8; substance control sits under COSHH 2002 Regulation 7; equipment selection is governed by PUWER 1998 Regulation 4. Excavations bring in CDM 2015 Regulation 22 for collapse and underground services. Reportable incidents must be notified under RIDDOR 2013.

HSE's operational standards extend these into actionable detail. HSG150 covers construction health and safety generally; HSG47 sets the standard for buried services; HSG185 for excavations; HSG258 for airborne dust control; HSG33 for roofing; HSG250 for permit-to-work. The L23 ACOP on manual handling and INDG163 on the 5-step assessment are the most-cited supporting documents in UK construction RAMS.

Last reviewed: 1 May 2026 · Sources: HSWA 1974; MHSWR 1999; CDM 2015; WAHR 2005; LOLER 1998; PUWER 1998; COSHH 2002; RIDDOR 2013; HSE HSG150, HSG47, HSG185, HSG258, HSG33, HSG250, INDG163, L23.