RAMS vs Risk Assessment: What Is the Difference?

If you have been asked for "RAMS" but only ever produced a risk assessment, this page is the starting point. It defines each document, explains what the RAMS bundle adds, and sets out the one distinction that trips most contractors up: a risk assessment is a legal duty, whereas a RAMS is a contractual requirement. Get that clear and the rest follows.

The short answer: what separates a risk assessment from a RAMS

A risk assessment is a legally required document under UK health and safety law. It identifies hazards, evaluates the likelihood and severity of harm, and records the control measures that reduce risk to an acceptable level.

A RAMS — Risk Assessment and Method Statement — is an industry-standard combination document. It bundles the risk assessment with a method statement: a step-by-step description of how the work will actually be carried out. RAMS is not a defined statutory term anywhere in UK legislation. It carries no independent legal force beyond its component parts. What gives a RAMS its teeth is that main contractors and clients routinely make it a contractual pre-start requirement, which means no RAMS, no access to site.

Understanding this distinction — legal obligation on one side, contractual bundling on the other — is the foundation for producing documentation that is both legally sound and procurement-ready.

---

What a risk assessment is — purpose, legal driver, and core content

The duty to carry out a suitable and sufficient risk assessment is a cornerstone of UK health and safety law, set out in regulation 3 of the Management of Health and Safety at Work Regulations 1999 (MHSWR 1999). That duty applies to virtually every employer and self-employed person carrying out work that could harm employees or others.

A suitable and sufficient risk assessment must:

• Identify the hazards present in the task or workplace
• Evaluate the risk — the likelihood of harm combined with its severity — for each hazard
• Record the control measures that will be put in place to eliminate or reduce the risk
• Identify who might be harmed and how
• Be reviewed whenever there is reason to suspect it is no longer valid (following an incident, a change in the task, or the introduction of new equipment)

Under MHSWR 1999 reg 3(6), any employer with five or more employees must record the significant findings of the assessment. The risk assessment answers the question: what could go wrong, and what stops it? It is an analytical document, not an operational one. It tells you the risks are controlled; it does not tell your workers what to do on Monday morning.

---

What a method statement is — purpose and what it adds to a risk assessment

A method statement is an operational document. It describes the sequence of work — the steps a team will follow to complete a specific task safely. Where a risk assessment asks what are the risks?, a method statement asks how will the work be done?

A method statement typically covers:

• The scope of the task and the location
• The sequence of operations in chronological order
• The plant, equipment, and materials to be used
• The personnel involved and their competencies
• The emergency arrangements specific to the task

Critically, a method statement is not a statutory requirement as a standalone named document under CDM 2015 or any other UK regulation. It is an industry norm — a practical tool that translates risk controls into actionable instructions. Its legal significance arises when it is contractually required (which in construction it almost always is) or when it forms part of a safe system of work under the general duty to plan, manage, and monitor construction work.

A method statement only works when it is built directly from the risk assessment's controls. That translation — each control becoming a numbered step a reviewer can trace — is a discipline in its own right, and it is where most rejected RAMS fall down. We cover it in full in our companion guide: how a risk assessment feeds the method statement. This page stays with the definitions and the decision of which document you need; that page shows how the two connect.

---

What a RAMS is — why the two documents are combined and what each part must cover

A RAMS combines both documents into a single submission because the two are complementary. The risk assessment identifies the hazards and controls; the method statement describes the work sequence within which those controls are applied. Presenting them together allows a principal contractor or client to review, in one document, both what could go wrong and how the work will actually proceed.

Annotated document anatomy: risk assessment vs method statement vs RAMS

Attribute	Risk Assessment	Method Statement	RAMS
Purpose	Identify hazards, evaluate risk, record controls	Describe the sequence and method of work	Satisfy both the legal risk-control duty and the contractual pre-start requirement
Core content	Hazard, likelihood, severity, control measures, persons at risk	Scope, step-by-step operations, plant/equipment, personnel, emergency arrangements	All of the above in a single document
Legal driver	UK health and safety law (MHSWR 1999, reg 3)	No standalone statutory requirement — contractual/industry norm	No standalone statutory definition — contractual requirement backed by component legal duties
Who produces it	The employer or self-employed person carrying out the work	The contractor responsible for the task	The contractor, often prompted by the principal contractor's pre-start requirements
When produced	Before work begins; reviewed when circumstances change	Before work begins; task-specific	Before work begins; submitted as part of the pre-start/mobilisation pack
Who reviews it	Employer, responsible manager, competent person	Principal contractor, site manager	Principal contractor or client reviewer where required by contract/site rules
Retention	For the life of the risk and as required by contract	As required by contract	Best practice: retain for the project lifecycle and any contractual period beyond — specific periods are not prescribed by statute

---

Where CDM 2015 fits: duty-holders, contractors, and the document chain

The Construction (Design and Management) Regulations 2015 (CDM 2015) govern health and safety management across UK construction projects. CDM 2015 — as set out in Parts 2 and 3 of the Regulations — establishes named duty-holder roles: client, principal designer, principal contractor, designer, and contractor, each with specific health and safety obligations.

The Regulations apply to construction work in Great Britain, including preparation for construction, as set out in the application provisions of CDM 2015 (reg 3). Where a project involves, or is likely to involve, more than one contractor, reg 5 requires the client to appoint a principal contractor (CDM 2015, reg 5). The construction phase plan is a document distinct from a RAMS, covering site-wide arrangements rather than task-specific risk controls.

Under reg 15, contractors must plan, manage and monitor construction work under their control so that it is carried out without risks to health or safety, so far as reasonably practicable (CDM 2015, reg 15). This duty does not mention a method statement by name, but it creates the environment in which a method statement becomes practically important: you cannot convincingly evidence planned, managed, and monitored work without describing how that work will be carried out.

The RAMS therefore sits at the intersection of the contractor's legal duty to manage risk (risk assessment component) and the principal contractor's contractual mechanism for verifying that subcontractors have done so (method statement component). CDM 2015 is the framework that makes RAMS the norm; it is not the statute that requires them by name.

---

Decision matrix: which document does your project or task actually need?

Scenario / Trigger	Document Required	Legal or Contractual Basis
Any employer or self-employed person carrying out work that could harm others	Risk assessment	UK health and safety law (MHSWR 1999, reg 3)
Project involving more than one contractor — principal contractor appointed	Risk assessment + method statement submitted to PC (typically as RAMS)	CDM 2015 reg 5 (PC appointment); reg 15 (contractor duty to plan and manage); PC's contractual pre-start requirements
Notifiable project — client, principal designer, and principal contractor all appointed	RAMS per subcontractor trade, plus construction phase plan	CDM 2015 regs 5, 12, 15; contractual pre-start pack
Single-trade contractor on small, non-notifiable, single-contractor works	Risk assessment (method statement best practice but not always contractually required)	UK health and safety law; review any client/contractual requirements
High-risk activity (work at height, confined space, live services, excavation)	RAMS — risk assessment alone is insufficient; method statement essential to demonstrate a safe system of work	CDM 2015 reg 15; Schedule 3 (work involving particular risks); contractual requirements
Client or main contractor pre-start / procurement requirement	RAMS — regardless of project size or notifiability	Contractual — client or PC specification
Principal contractor building the construction phase plan	Construction phase plan (draws on subcontractor RAMS as inputs)	CDM 2015 reg 12

---

Worked example: two-person electrical subcontractor producing a RAMS for first-fix wiring

Scenario: A two-person electrical subcontractor is engaged by a main contractor on a new residential development. The main contractor's pre-start pack requires a RAMS before any first-fix wiring work begins. The subcontractor asks: do we really need a full RAMS, or will our standard risk assessment do?

The answer is RAMS — and here is why each part does different work:

Risk assessment section (what could go wrong?)

Hazard	Who at risk	Likelihood	Severity	Controls
Electric shock (contact with live conductors)	Both operatives	Medium	High	Verify isolation before work; use proving unit; display 'Do Not Energise' locks
Fire (cable overheating, incorrect rating)	Operatives, building occupants	Low	High	Use correctly rated cable; follow BS 7671 installation requirements
Manual handling (cable drums, trunking)	Both operatives	High	Medium	Use drum stands; team-lift heavy drums; pre-position materials
Slips/trips (cable off-cuts, trunking off-cuts on floor)	Operatives, other trades	High	Low–Medium	Continuous housekeeping; off-cuts removed to skip same day

The risk assessment tells the main contractor that the subcontractor has identified the hazards and has controls in place. But it does not, on its own, tell the main contractor — or the operatives — the order in which the work will proceed. That sequencing is the method statement's job, and the worked traceability of each control into a step is covered in detail in the information-chain guide.

For the purposes of this decision — "is a standalone risk assessment enough, or do we need RAMS?" — the answer turns on the main contractor's pre-start requirement, not on the legal minimum. The legal minimum here is the risk assessment under MHSWR 1999. The contractual minimum is the full RAMS. The contractual requirement is the higher bar, so RAMS is what gets you on site.

---

The four most common misunderstandings about RAMS vs risk assessment

These are conceptual mistakes about what each document is — distinct from the gaps that get a RAMS rejected on review, which we cover on the companion page.

1. Assuming "risk assessment" and "RAMS" are interchangeable. They are not. A risk assessment is one component of a RAMS. Submitting a bare risk assessment where RAMS is required will usually be returned, because the method statement half is missing.

2. Believing a RAMS is a legal requirement in its own right. It is not. The risk assessment component is the legal duty (MHSWR 1999, reg 3). The RAMS label adds contractual weight, not statutory force.

3. Thinking a RAMS replaces the duty to do a proper risk assessment. A RAMS is only as robust as the risk assessment inside it. If that assessment is not suitable and sufficient, calling the document a "RAMS" provides no additional legal protection.

4. Producing a method statement and assuming it stands alone. A method statement with no underlying risk assessment is just a generic task description. It cannot evidence that hazards were identified and controlled — which is the whole point of the exercise.

---

How ramsdocs helps you produce the right document, first time

ramsdocs provides structured templates and task-specific content prompts that help contractors decide which document a job actually needs and produce RAMS documentation that is PC review-ready — meaning the structure, content headings, and logic flow match what principal contractors expect to see before authorising work to start.

Every output from ramsdocs is designed to be reviewed and adapted to your specific site, task, and contractual requirements by a competent person. Templates reduce rework by ensuring nothing is missed; they do not remove the need for professional judgement on site conditions.

---

Frequently asked questions

What is the difference between RAMS and a risk assessment? A risk assessment is a single, legally required document that identifies hazards and records controls under MHSWR 1999, reg 3. A RAMS bundles that risk assessment together with a method statement into one combined submission. The risk assessment is part of the RAMS, not an alternative to it.

What is a risk assessment and what must it contain? A risk assessment identifies the hazards associated with a task, evaluates the likelihood and severity of harm, records who might be harmed and how, and sets out the control measures that reduce risk. It is required under MHSWR 1999, reg 3 before work begins, and significant findings must be recorded where the employer has five or more employees.

What is a RAMS? A RAMS (Risk Assessment and Method Statement) is an industry-standard combined document. It is not defined in UK statute. It bundles the legally required risk assessment with a method statement — a step-by-step operational description of how work will be carried out.

Is a RAMS a legal requirement? Not as a named document. The risk assessment component is a legal requirement under MHSWR 1999. The method statement component is not a standalone statutory obligation but is almost universally required by main contractors as a contractual pre-start condition.

Can a RAMS replace a standalone risk assessment? Yes — the RAMS contains the risk assessment. Provided the risk assessment section is suitable and sufficient, you do not need a separate standalone document as well.

When is a standalone risk assessment sufficient? For low-risk, single-contractor work with no PC pre-start requirement, a risk assessment alone may satisfy the legal obligation. As soon as a principal contractor is involved, or the work is high-risk, a full RAMS is expected.

---

This page is for guidance only. All documentation produced using or inspired by this content must be reviewed and adapted to the specific site, task, and contractual requirements by a competent person before use. Nothing on this page constitutes legal advice or ensures compliance with any regulatory or contractual obligation.