Method Statements That Actually Get Signed Off

Walk into any principal contractor’s site office during a busy week and you will find a stack of RAMS submissions waiting to be reviewed, and at least a third of them will be going back. Not because the work is unsafe, but because the document does not give the reviewer what they need to sign it off.

That is the problem. Most method statements describe the job without proving the hazards have been thought through. The document reads like a procedure when it needs to read like a safety case.

What a principal contractor is actually checking

When your RAMS lands on a PC’s desk, they are not reading it word for word. They are scanning for evidence that the person who wrote it understands the risk, not just the task. Three things need to be immediately obvious: who is doing the work, what could go wrong, and what stops it going wrong.

If those three things are buried in paragraphs, or missing entirely, the document comes back. It does not matter how thorough your method is if the structure does not let the reviewer find what they need in thirty seconds.

Structure that works

A method statement that gets accepted first time tends to follow a consistent shape.

Project and scope. One paragraph, no more. Site address, contract reference, the specific activity covered by this document. Not a history of the project.

Personnel and competency. Who is doing the work, what qualifications or tickets they hold, who the supervisor is. If the PC cannot match names to roles, expect questions.

Plant and equipment. What machinery, tools, and access equipment will be on site. Include inspection status where relevant, such as LOLER thorough examination dates or calibration records.

Sequence of works. This is where most documents fall apart. More on this below.

Risk matrix. A table, not a paragraph. Hazard, likelihood, severity, control measures, residual risk. If it takes more than a few seconds to read each row, shorten it.

Emergency arrangements. First aid provision, nearest A&E, muster point, who calls the emergency services.

Getting the sequence of works right

The sequence of works section needs to describe what happens, in order, from when operatives arrive on site to when they leave. Not the whole project, just the activity covered by this RAMS.

Write it as numbered steps. Each step should be short enough to read in one breath. If a step introduces a hazard, say what control is in place at that point rather than referencing another section. The reviewer should not have to cross-reference two parts of the document to understand how you are managing a risk.

A common mistake is writing the sequence too broadly. “Carry out groundworks” is not a step. “Break out existing concrete slab using a breaker, dampen surface to control silica dust, bag and remove arisings to skip” is a step. Specific enough to be checked against, but not so prescriptive that it ties the hands of whoever is on the ground.

Building a risk matrix that holds up

A risk matrix where every residual risk is rated low will raise eyebrows. Reviewers know that some activities carry residual risk even with the best controls in place. Working at height, confined spaces, breaking into live services: these do not become low-risk just because you wrote down a control measure.

Use a 5x5 likelihood-severity grid. Score before and after controls. If your after-control score is still medium or high, say what additional management is in place and who authorises the work to proceed. That is not a weakness in your document. It is evidence that the risk has been assessed honestly.

Keep the language in the controls column specific. “PPE to be worn” is not a control. “Operatives to wear P3 RPE during all cutting and breaking activities, masks to be fit-tested, records available on request” is a control.

A tool worth knowing about

Writing RAMS from scratch is time-consuming, and a blank page is a poor starting point when you have a job to price and a deadline for submitting documentation. SafetyDeskStudio sell a RAMS Generator on Etsy (https://www.etsy.com/listing/4552120405) that gives you a structured template built around the sections above. It is not a substitute for knowing your hazards, but it removes the hour you would otherwise spend formatting before you have written a word of substance.

One last check before you submit

Before the document goes out, read the sequence of works back against the risk matrix. Every significant hazard in the matrix should appear in the sequence at the point where it becomes relevant. If you can find a hazard in the matrix that is not reflected anywhere in the sequence, so can the PC reviewer.

A method statement that comes back once costs you an hour. One that bounces three times costs you a relationship.

If your operation has broader gaps, not just in documentation but in how time and output quietly disappear on the floor, the Six Big Losses framework is worth working through at /six/. For a quicker read on where your site stands overall, the diagnostics tool takes about ten minutes and gives you a structured picture of where to focus first.