Risk assessments and method statements (RAMS) that get accepted first time

Risk assessments and method statements are the documents a principal contractor, a client's adviser or an HSE inspector reaches for first, because together they are supposed to show that a task has been thought through and will be done safely. They are also the documents most likely to be sent back. A rejected RAMS holds up the work, and the reason is almost always the same: the paperwork describes a job in general terms when the reader needs to see this job, on this site, with these people and this plant. Getting a RAMS accepted first time is less about length and more about specifics.

What suitable and sufficient actually means

The legal anchor for the risk assessment is regulation 3 of the Management of Health and Safety at Work Regulations 1999, which requires every employer to make a suitable and sufficient assessment of the risks to workers and to anyone else who might be affected. Suitable and sufficient is the test a reviewer is applying, whether they name it or not. It means the assessment is proportionate to the risk, that it identifies the significant hazards rather than listing every conceivable one, and that it leads to real control measures rather than a note to take care.

HSE now frames the assessment as a short sequence: identify the hazards, decide who might be harmed and how, evaluate the risk and decide on controls, record the significant findings, and review when something changes. A generic template fails at the middle steps, because the people and the controls are the parts that only make sense once you know the task and the location. A reviewer can tell in under a minute whether those steps were done for the job in front of them or lifted from the last one.

Why method statements get sent back

The method statement is the safe system of work written down. It is not named in a single regulation, but the duty to provide one flows from section 2 of the Health and Safety at Work etc Act 1974 and, on construction, from the Construction (Design and Management) Regulations 2015, which require the work to be planned, managed and monitored. The common failings are easy to list and easy to fix:

• It describes the activity in general terms and never sets out the sequence of operations in the order they will happen.
• The hazards from the risk assessment are not carried through, so the controls in the method statement do not match the risks that were identified.
• Responsibilities are vague. A reviewer wants to see who supervises, who is competent to do what, and who can stop the job if conditions change.
• Plant, access and materials are assumed rather than stated, so there is no way to check that the method is actually workable.
• Emergency and rescue arrangements are missing, which is the first thing a reviewer looks for on higher risk tasks such as confined spaces, lifting and work at height.
• It still carries the name of another site or another contractor, which tells the reviewer it was never written for this job.

Use the hierarchy of control, in order

Schedule 1 to the Management Regulations sets out the principles of prevention, and they are an order, not a menu. A method statement that reaches straight for personal protective equipment as the main control is one of the clearest reasons a RAMS is rejected. The reviewer wants to see the question asked in sequence: can the hazard be removed, can a less hazardous method or material be substituted, can it be engineered out or guarded, can it be controlled by how and when the work is organised, and only then what protective equipment is needed to deal with the risk that is left. Showing that reasoning is what turns a list of hazards into a controlled task.

Make it specific to this task on this site

The single habit that gets a RAMS accepted first time is specificity. Name the actual location and the actual activity, not a category. Reference the drawings, the permit, the temporary works design or the lifting plan that the method depends on, so the reader can see the controls are real. Where the risk assessment identifies a significant hazard, the method statement should answer it in plain terms a supervisor can brief on site. If the task interfaces with others, say so, because simultaneous operations, shared access and overhead work are where incidents cluster, and a reviewer will look for them.

Briefing and sign-off, the step that gets skipped

A RAMS that has not been briefed to the people doing the work is just paper, and a reviewer increasingly asks for the evidence that it was. The record that the operatives were briefed, understood the sequence and the controls, and signed to that effect is part of the safe system of work, not an afterthought. It is also the record that protects everyone if something goes wrong, because it shows the plan reached the point of work. Keep the briefing record with the RAMS and the toolbox talk that supports it, and make sure the version briefed is the version that was approved.

A quick pre-submission check

Before a RAMS goes in for approval, read it as the reviewer will:

• Does it name this site, this task and this date, with no leftovers from another job?
• Do the controls in the method statement answer every significant hazard in the risk assessment?
• Is the sequence of work set out step by step, with the plant, access and materials each step needs?
• Are the competent and responsible persons named, including who can stop the work?
• Are emergency and rescue arrangements stated for the higher risk elements?
• Is there a place to record the briefing and the sign-off, and a trigger to review if conditions change?

What good looks like

A RAMS that stands up is specific, sequenced and honest about the risk that is left once the controls are in place. The risk assessment identifies the significant hazards and follows the hierarchy of control to real measures. The method statement turns those measures into an ordered plan a supervisor can brief and follow, names who is responsible, and sets out what happens in an emergency. It references the drawings, permits and designs it relies on, and it carries a briefing record so there is proof the plan reached the people doing the work. None of that adds length for its own sake. It is the difference between a document that describes a task and one that controls it, and it is what gets the work approved the first time it is read.

This is general guidance based on the regulations and HSE guidance current at the time of writing. It is not a substitute for the regulations, the relevant Approved Codes of Practice or professional advice, and it is written with Great Britain in mind.