How to Evidence RAMS Sign-Off for an HSE Inspection: A Complete Guide

An HSE inspector does not usually ask whether you have RAMS. They assume you do. What they ask is harder: show me that the people doing this task were briefed on this version of it, and show me when.

That is a different question, and a signature sheet in a folder in the site office often cannot answer it. The sheet proves a name was written down. It rarely proves which revision was on the table, whether the person who signed is the person on site today, or whether anyone updated the record when the method changed three weeks ago.

This guide covers what RAMS sign-off evidence actually has to demonstrate, what the law does and does not require, the records that hold up under questioning, and the failures that quietly undermine an otherwise well run site. If you want the wider picture of how safety records fit together on a project, our overview of construction compliance management covers that ground.

Key Takeaways: Evidencing RAMS Sign-Off

• No regulation says “get a signature on a RAMS”. The signature exists to evidence duties that are in the regulations: risk assessment, information, instruction, training and supervision.
• Evidence has to connect four things: the person, the document version, the date, and the work they then went and did.
• Version control is where most RAMS files fail. A signature against a superseded revision is worse than no signature, because it shows the system was not maintained.
• Subcontractor RAMS are your problem too. Accepting a document is not the same as evidencing that the operatives were briefed on it.
• The test is retrieval speed. If producing the record for one operative on one task takes longer than a few minutes, the file is a filing cabinet rather than an audit trail.
• Briefing records, competency records and site access records are read together. Gaps between them are what an inspector follows.

What RAMS actually is, and what the law says

RAMS is shorthand for risk assessment and method statement. The two halves do different jobs, and conflating them is the first thing that weakens a file.

The risk assessment identifies the hazards in a task and judges their significance. This one is squarely a legal requirement. Under the Management of Health and Safety at Work Regulations 1999, employers must assess the risks to which employees and others are exposed, and employers with five or more employees must record the significant findings.

The method statement turns those findings into a sequence. The HSE describes it as drawing together the information about hazards and the ways in which they are to be controlled for a particular job, then setting out the steps for carrying out the work safely.

Here is the part that surprises people. There is no regulation that says a method statement must be signed by the operatives carrying out the work. The signature is not the legal requirement. It is evidence that you discharged requirements which are legal, and those sit in three places:

• The Construction (Design and Management) Regulations 2015, regulation 15, which requires a contractor to provide each worker under their control with appropriate supervision, instructions and information, including site induction where the principal contractor has not already provided it.
• CDM 2015 regulation 13, which requires the principal contractor to ensure all workers have site specific inductions and any further information and training they need.
• The general duty to provide information, instruction, training and supervision under the Health and Safety at Work etc. Act 1974.

Understanding that changes what you collect. You are not collecting signatures. You are collecting proof that the right people knew the right method at the right time. Our guide on choosing construction QA software makes a similar point about quality records, and the principle is identical: the record has to be created at the moment the work happens, not assembled afterwards.

Why a signature sheet is not evidence

A printed sheet with a list of names has three weaknesses, and an inspector will find all three in about ninety seconds.

It is not tied to a version. The sheet says the operative was briefed on the RAMS. It does not say which RAMS. If the method statement has been revised twice since, the sheet proves nothing about the method actually in use.

It is not tied to a date that can be trusted. A handwritten date can be written at any time, including the morning of the inspection. Inspectors know this. So do clients.

It is not tied to attendance. The sheet shows who signed. It does not show who was on site that week, which means it cannot show who worked on the task without being briefed. That gap is the one that leads to enforcement, because it is the one that leads to harm.

A record that survives scrutiny closes all three. It fixes the document version, fixes the time independently of the person signing, and reconciles against who actually signed in to site that day.

What an HSE inspector actually asks for

Inspections vary, but the line of questioning on a specific task is fairly consistent. Expect some version of these six.

1. Show me the RAMS for this activity. Straightforward, and almost always answered. This is the warm up.

2. Is this the current version? The first real question. You need a revision number or date on the document, and a way to demonstrate that nothing newer exists.

3. Who is doing this work today? Names, and ideally the trade and employer for each.

4. Show me that each of those people was briefed on this version. This is the question that separates a working system from a folder. It requires a per person, per version record.

5. When were they briefed, and by whom? A date and a briefer. If the briefing happened before the revision, you have a problem.

6. What happened when the method changed? Revisions are normal and expected. What is not acceptable is a revision that never reached the work face. Inspectors are far more interested in whether your process catches change than in whether your original document was elegant. The same logic applies to monthly site safety inspections, where the value is in the action that followed rather than the form that was filled in.

Question four is where most sites come unstuck, and question six is where the ones that survive question four come unstuck. If you take one thing from this guide, build your system around those two.

The evidence chain, step by step

Seven links. Break any one of them and the chain does not hold.

1. The document carries a version identity

Every RAMS needs a revision number or letter and an issue date printed on the document itself, not only in a folder name. If the version lives only in the file name, it disappears the moment someone prints it or forwards it.

2. Issue is recorded, not just performed

Record that the document was issued to the project, when, and by whom. Emailing a PDF to a site manager is issuing. Whether it is recorded is a separate question, and the answer is usually no. If you are still building your document set, our free inspection templates show the structure these records take.

3. Briefing is delivered by a named person

Someone briefs the operatives. Record who. A briefing with no briefer looks like a document that was left on a table.

4. Acknowledgement is captured per person, per version

This is the core record. One operative, one version, one timestamp. Not a group sheet. Not a tick against a team. Digital RAMS sign-off exists for exactly this, because the alternative is reconciling handwriting against a payroll list.

5. Competence is attached to the same person

Being briefed is not the same as being competent to do the work. The operative’s cards, tickets and training records need to sit alongside the briefing record, with expiry dates visible. Induction and competency card records are read together with RAMS sign-off, not separately.

6. Site access reconciles against the briefing list

If someone signed in and worked on the task but never signed the RAMS, you want to know before the inspector does. The check has to run at the gate, not in a monthly review.

7. A revision triggers re-acknowledgement

When the method changes, everyone previously briefed needs to acknowledge the new version, and the old version needs to remain retrievable rather than be deleted. Archive, do not overwrite.

Version control: the failure that undoes everything

Almost every RAMS file that falls apart falls apart here. The pattern is always the same.

A method statement is written and briefed. Conditions change: a different access method, a substituted plant item, a sequence adjusted to suit the programme. Someone updates the document. The updated version reaches the office and the client. It does not reach the seventeen people holding the tools.

Now you have a worse position than if you had never revised it, because the paperwork shows a control measure that is not being applied on site. That is not a documentation failure. It is evidence that the control was not implemented.

Three habits fix it. Keep exactly one current version in circulation. Make the current version the only one accessible at the point of sign-off. Keep a visible list of who has signed the current version and who has not, so the gap is a number somebody is looking at rather than a discovery made later.

The same discipline runs through permits to work and site inspections, where a control that was signed but never re-issued after a change is the most common finding of all.

Subcontractor RAMS are still your evidence problem

Most RAMS on a site are written by somebody else. Accepting them is an approval step. It is not evidence of briefing.

Three things are worth being firm about:

Acceptance is recorded with a date and a reviewer. Who read it, when, and what they were satisfied about. A RAMS that appeared in an inbox and went straight into a folder has not been accepted, it has been received.

Briefing evidence comes back to you. If the subcontractor briefs their own operatives, you still need the record. Agree at the start of the package that acknowledgement records are visible to you, not held on a system you cannot see.

Operatives are reconciled against your access records. The people on the subcontractor’s briefing list and the people who badged onto your site should be the same people. Where they differ, you have either an unbriefed operative or an out of date list, and both matter.

Contractors working the other way round, as the subcontractor rather than the principal, face the mirror image of this problem: producing the same evidence on demand for several main contractors who each want it in a different format. One consistent internal record makes that manageable.

What to keep, and in what form

There is no single statutory retention period covering RAMS. In practice, keep them for the life of the project and well beyond it, because the claims that reference them arrive years later. Civil claims have their own limitation periods, and a method statement is frequently the document a dispute turns on.

Form matters as much as duration. The HSE’s general position on statutory records is instructive: they should be readily available to enforcing authorities, held securely, and capable of being reproduced in written form. That is a reasonable standard to apply to RAMS evidence too.

The practical test is retrieval. Pick one operative and one task from six months ago and try to produce the version they were briefed on, the date, and the briefer. If that takes an afternoon, the records exist but the evidence does not. Sample reports are a useful way to see what a retrievable record looks like laid out on the page.

Common mistakes

• Group sign-off sheets with no per person, per version detail.
• Version numbers in the file name only, so printed copies lose their identity.
• Briefing dates recorded as a day rather than a timestamp.
• Revisions issued to the office and the client, but not re-briefed on site.
• Superseded versions deleted rather than archived, so the history cannot be reconstructed.
• Subcontractor acknowledgement records held on a system the main contractor cannot access.
• Competency card expiry tracked separately from briefing records, so an expired ticket and a valid signature sit side by side unnoticed.
• Toolbox talks used as a substitute for RAMS briefing. They are complementary, not interchangeable. Free toolbox talks cover general awareness. A RAMS briefing covers a specific task and a specific method.

Why Insite Is the Best Choice for RAMS Sign-Off Evidence

Every item in the evidence chain above depends on the record existing at the moment of the briefing, tied to a person and a version. That is what Insite is built to produce.

Signatures tied to the version, not just the document. Operatives read and sign on any device, and each signature is time-stamped and tied to the worker, the project and the specific document version. Answering “was this the current revision” stops being a judgement call.

Existing PDFs, unchanged. Upload the RAMS you already produce. There is no reformatting step, which means the system does not depend on anyone rewriting their documents before it starts working.

One current version, earlier ones archived. When the method changes, the new version becomes current and the previous one stays retrievable. The history can be reconstructed without anyone digging through email.

Unsigned RAMS flagged at sign-in. When a worker signs in, Insite checks whether they have signed the current RAMS for that project and prompts them before they continue. That closes the gap between who was briefed and who was on site, which is the gap inspectors follow.

A live list of who has signed and who has not. Pending sign-offs are visible with one-tap reminders, so the outstanding number is something a site manager acts on rather than discovers.

Briefing, competence and access in one worker profile. Cards, tickets and training records with expiry alerts sit alongside induction and competency records, so an expired ticket cannot hide behind a valid signature.

Records that export for auditors. Insite customers report producing an inspection record for auditors in around three minutes, with 100% of operatives inducted before first entry. Simon Prince, Health and Safety Manager at Jennor, reports saving at least £1,000 every month by removing paper based setup and cutting admin time.

Frequently asked questions

Is it a legal requirement to sign a RAMS?

No. There is no regulation requiring an operative’s signature on a method statement. The signature is evidence that you met duties which are legal requirements: assessing risk under the Management of Health and Safety at Work Regulations 1999, and providing information, instruction, training and supervision under CDM 2015 and the Health and Safety at Work etc. Act 1974.

What does an HSE inspector want to see for RAMS sign-off?

That the operatives carrying out a task were briefed on the current version of the RAMS for that task, when they were briefed, and by whom. They will also want to see what happened when the method was revised, because a revision that never reached the work face shows the control was not implemented.

Is a digital signature acceptable for RAMS?

Yes. What matters is whether the record reliably identifies the person, the document version and the time. A time-stamped digital acknowledgement tied to a named worker and a specific revision is stronger evidence than a handwritten signature on an undated sheet, not weaker.

How long should RAMS records be kept?

There is no single statutory retention period for RAMS. Keep them for the life of the project and well beyond, because civil claims referencing a method statement can arrive years after practical completion. Specific record types such as health surveillance records have their own statutory periods, so check those separately.

Do operatives need to re-sign when a RAMS is revised?

Yes. A signature against a superseded revision does not evidence briefing on the method actually in use. Everyone previously briefed should acknowledge the new version, and the superseded version should be archived rather than deleted so the history remains reconstructable.

Who is responsible for subcontractor RAMS on site?

The subcontractor writes and briefs their own RAMS, but the principal contractor still has to be able to evidence that briefing happened. Agree at package award that acknowledgement records are visible to you, and reconcile the briefing list against your own site access records.

What is the difference between a toolbox talk and a RAMS briefing?

A toolbox talk covers general awareness of a hazard or topic. A RAMS briefing covers a specific task, a specific method and the specific controls in that document. A toolbox talk does not evidence RAMS sign-off, and recording one in place of the other leaves a gap.

Where to start

Pick one live activity on one site. Try to produce, in under five minutes, the current RAMS version, the list of operatives briefed on that version, the timestamp for each, and the reconciliation against who signed in that week.

Whatever you cannot produce is the part of the chain to fix first. For most contractors it is link four, the per person per version acknowledgement, and link seven, re-acknowledgement after a revision.

If you want to see how Insite handles RAMS sign-off, inductions and competency records against the chain in this guide, the product pages walk through it.