RAMS sign-off: how do you prove your team has read the method statement?

To prove your team has read a RAMS, you need a record that ties each named person to the exact version of the method statement they were briefed on, the time they confirmed it, and evidence that record hasn't changed since. Writing and issuing a RAMS is well covered — by templates, software and consultants. The part that's routinely thin is showing that the people actually doing the work read the version they're working to. That's the gap a principal contractor, an insurer or an HSE inspector tends to find.

This applies the four-part test for proof of acknowledgement to the specific case of a method statement.

What a RAMS is

RAMS stands for Risk Assessment and Method Statement — two related documents usually packaged together. The risk assessment identifies the hazards and the controls that bring the risk down; the method statement sets out, step by step, how the work will be carried out safely. They're most common in construction and other higher-risk work, and they're often requested by a client or principal contractor before you're allowed on site, as part of pre-qualification.

Do RAMS need to be signed? What the law requires

There's no law that says a method statement must be signed, or that "everyone signs the RAMS". What the law requires sits underneath it, in three parts:

• The risk assessment is a legal requirement. Under the Management of Health and Safety at Work Regulations 1999 (regulation 3), employers must make a suitable and sufficient assessment of the risks — and if you have five or more employees, you must record the significant findings.
• The method statement is not a standalone legal requirement. The HSE treats it as one effective way to satisfy the duty to plan and control higher-risk work, and under the Construction (Design and Management) Regulations 2015 construction work must be properly planned, managed and monitored. For some activities — confined spaces, for example — a written safe system of work is required before work begins.
• You must inform the people at risk. Under regulation 10 of the same 1999 Regulations, and section 2 of the Health and Safety at Work etc. Act 1974, employers must give employees comprehensible, relevant information on the risks and the precautions to take.

A signature is simply the common way people try to evidence that last duty. On its own it's a weak record — the same problem any acknowledgement has. None of this is legal advice; it's the practical reason the briefing matters less than being able to show it happened.

Issued isn't the same as read

A RAMS emailed to the team, pinned to the site board, or talked through at a pre-start briefing can all be genuine and well-intentioned. None of them, on their own, produces a record that a named worker read the specific version they're working to, at a known moment, in a form that can't be quietly changed afterwards. "We briefed everyone" is a recollection; the useful answer, when someone asks, is a record. RAMS make this sharper than most documents, because they get revised: when the method, the sequence, the plant or the site conditions change, the RAMS changes with them — and a sign-off against last month's revision doesn't cover this week's method.

What good RAMS sign-off looks like

Good RAMS sign-off is the four-part test for proof of acknowledgement applied to the method statement:

• Who — the named worker who'll do the task, not "the gang" or a circulation list.
• Which version — the exact RAMS revision they were briefed on. This is the one people miss: when the RAMS is reissued, the confirmation has to be against the new revision, not silently inherited from the old one.
• When — recorded at the briefing, at the moment they confirm, not written up afterwards.
• Unaltered — kept in a form that can't be edited later, so the record still means something when the work is long finished.

How Provenly captures this

Provenly applies that test to your RAMS without adding site admin:

• You share the current version of the method statement with the people who need it.
• Each named worker confirms against that exact version — and when you reissue a revised RAMS, you get a fresh confirmation against the new revision rather than an old one carried forward.
• Every confirmation is time-stamped at the moment it's made.
• Each record is sealed and linked into a running chain, so if an earlier entry were ever changed the chain would no longer line up — tamper-evident in the plain sense that any change shows.

The result is a complete, contemporaneous, tamper-evident record of who confirmed which revision of the RAMS, and when.

---

Frequently asked questions

Do method statements need to be signed by law?

No law specifically requires a method statement to be signed. The risk assessment is what's legally required (Management of Health and Safety at Work Regulations 1999, regulation 3), and you must give the people at risk comprehensible information on the risks and precautions (regulation 10). Signing is the common way to evidence that — but a signature on its own is a weak record.

Is a RAMS a legal requirement?

The risk assessment element is — and if you have five or more employees its significant findings must be recorded. The method statement isn't a standalone legal requirement, but it's expected under the CDM Regulations 2015 for construction, routinely required by clients and principal contractors, and for some high-risk work a written safe system of work is required before work starts.

When a RAMS is revised, does the team need to acknowledge it again?

In effect, yes. A confirmation only means something against the version it was made for. If the method, sequence or controls change, the new revision needs fresh acknowledgement — an old sign-off doesn't roll forward onto wording that didn't exist when it was signed.

How do you prove workers read the RAMS, not just received it?

You need a record tying a named worker to the exact revision they were briefed on, the time they confirmed it, and proof the record hasn't changed since. Being sent a RAMS shows it was issued; those four things are what show it was read.

Who should acknowledge the RAMS?

Anyone at risk from the work it covers. Recording that each named person confirmed the current revision is how you can later show the people doing the work had the information they needed.

Sources

• Management of Health and Safety at Work Regulations 1999, reg.3 — legislation.gov.uk/uksi/1999/3242/regulation/3
• Management of Health and Safety at Work Regulations 1999, reg.10 — legislation.gov.uk/uksi/1999/3242/regulation/10
• Construction (Design and Management) Regulations 2015 — legislation.gov.uk/uksi/2015/51/contents
• Health and Safety at Work etc. Act 1974, s.2 — legislation.gov.uk/ukpga/1974/37/section/2

Go deeper

• How do you prove your team has read a policy or risk assessment?
• Tracking H&S sign-offs in a spreadsheet: where it quietly breaks
• What an H&S audit trail has to prove — and why "we sent it round" fails