Briefing and signing a RAMS
A signature on a RAMS is evidence of a briefing, not proof the document is right. What to say on the morning, and when to stop.
The signature block is the last thing people look at and the first thing an investigator will. It shows who was told, and when. It does not show that the method matched the site. A page of signatures on a generic file is weaker than a short briefing that changed two lines because the roof light was not where the draft said it was.
Before anyone signs
Walk the area, or look from a safe place if walking it is the hazard. Confirm the access, the other people, and the thing that made you pick this trade’s template. If the job is not the job in the draft, stop. Edit it. Then brief.
Say the controls in the order people will meet them. On a scaffold, that is the ground and the exclusion before the first lift. On electrical work, that is isolation and proving dead before a cover comes off. On a security shift, that is the check-call and the point at which the officer withdraws.
The method statement template is the script. The risk scores are the reason the script is in that order.
What the operative is agreeing
They are agreeing they have heard the plan and will stop if it changes. They are not agreeing to be liable for the company’s assessment. They are not a competent person just because they signed. The review line on the PDF is a separate signature, for the person who checked the draft against the site.
After the briefing
Keep the signed copy with the job for as long as you keep the RAMS. If the weather, the scope or the people change, the old signatures are for the old plan. Rebrief. A note in the margin that nobody was told about is not a revision.
RamsBox puts the briefing rows and the competent-person block on every PDF. Filling them in is your part of the morning, not the software’s. If you are unsure the document should exist at all, read is a RAMS a legal requirement? and who should write it.