RAMS (Risk Assessments and Method Statements) are one of the most common documents on construction sites, yet they are frequently the least effective. Many are written to satisfy paperwork requirements rather than to genuinely control risk.

When done properly, a RAMS should give people clear, practical information about the hazards involved in a task and exactly how those hazards will be controlled. When done poorly, it becomes a generic document that sits in a folder and has little connection to what actually happens on site.

Key definitions

Before writing effective RAMS, it helps to be clear on the basic terms:

A good RAMS combines both the risk assessment and the method statement. It should clearly show what the hazards are, how serious they are, and exactly how they will be controlled during the work.

Understanding the risk matrix

Most construction businesses use a risk matrix to help score risks. This is a simple grid that multiplies the **likelihood** of something happening by the **severity** of the harm if it does happen.

Typical scoring looks like this:

Example Risk Scoring

  • Likelihood: 1 = Very unlikely, 2 = Unlikely, 3 = Possible, 4 = Likely, 5 = Almost certain
  • Severity: 1 = Minor injury, 2 = First aid injury, 3 = Lost time injury, 4 = Major injury, 5 = Fatality

Risk Score = Likelihood × Severity

A score of 1–6 is usually considered low, 8–12 medium, and 15+ high. Any high residual risk after controls should be reviewed carefully.

Before and after controls

Effective RAMS should show both the **initial risk** (before controls) and the **residual risk** (after controls are applied). This demonstrates that proper thought has gone into reducing the risk to an acceptable level.

If the residual risk remains high, the task may need to be redesigned or additional controls introduced before work starts.

Hierarchy of control measures

When deciding on controls, always work through the hierarchy in this order:

  1. Eliminate — Remove the hazard completely if possible.
  2. Reduce / Substitute — Replace with something less hazardous.
  3. Isolate / Engineering controls — Physical barriers, guards, or separation.
  4. Administrative controls — Procedures, training, permits, supervision, signage.
  5. PPE — Personal protective equipment (last line of defence).

Good RAMS show that the writer has worked down this hierarchy rather than jumping straight to PPE.

Writing the method statement

The method statement should describe the safe system of work in a clear sequence. It should include:

High-risk activities and permits

Certain activities require extra controls and often a permit-to-work system. These include:

Where permits are required, the RAMS should clearly state who issues the permit, what conditions must be met, and how the permit is closed out at the end of the task.

High-risk plant and machinery

When the work involves significant plant or machinery (e.g. excavators, telehandlers, piling rigs, mobile cranes), the RAMS should cover:

Environmental considerations

RAMS should also address environmental risks where relevant, including:

Common mistakes to avoid

Frequent weaknesses in RAMS

  • Copying generic templates with minimal changes for the specific task
  • Focusing heavily on hazards but giving weak or generic control measures
  • Writing method statements that describe an ideal process rather than how the work will actually happen on site
  • Producing documents that are too long and complex for anyone to use practically
  • Failing to involve supervisors and operatives in the development of the RAMS
  • Not reviewing or updating RAMS when site conditions change

Frequently Asked Questions

What is the difference between a hazard and a risk?

A hazard is anything that has the potential to cause harm. Risk is the combination of how likely it is that harm will occur and how serious that harm could be.

Do I need to use a risk matrix every time?

Not necessarily for every small task, but it is good practice on anything beyond routine low-risk work. The matrix helps you demonstrate that you have properly considered the level of risk before and after controls.

How detailed should a method statement be?

Detailed enough that someone competent can understand the sequence of work and the controls, but not so long that no one reads it. Focus on clarity and practicality over volume.

Should RAMS be written by the site team or by someone in the office?

The best results usually come from a combination. The person writing the RAMS should have good technical knowledge, but they should also involve the supervisors and operatives who will actually carry out the work.

When should I review and update a RAMS?

Whenever the work, conditions, or sequence changes significantly. A RAMS written at the start of a project can quickly become out of date as the job progresses.

Writing effective RAMS is not about producing impressive documents. It is about creating clear, practical guidance that helps people understand the risks and apply the right controls when they are actually doing the work.