Welcome Guest! The IOSH forums are a free resource to both members and non-members. Login or register to use them

Postings made by forum users are personal opinions. IOSH is not responsible for the content or accuracy of any of the information contained in forum postings. Please carefully consider any advice you receive.

Notification

Icon
Error

Options
Go to last post Go to first unread
alan w houghton  
#1 Posted : 18 May 2015 08:56:59(UTC)
Rank: Super forum user
alan w houghton

Hello all I am after examples of how rams are signed off and approved I have just reviewed a site and they have about 8 method statements 1 for each area, no problem with that but nobody has approved them and they have been changed over the last couple of months and unsure what is approved and what revision operatives are working to and have they signed onto the revised rams ? Anyway hopefully you get what I mean, has anyone got a idea how to control this through a register or how to ensure the site is working to the latest approved rams and operative have signed onto the latest revision there must be a simple way? If so any chance you can share with me please Thanks
firesafety101  
#2 Posted : 18 May 2015 09:48:04(UTC)
Rank: Super forum user
firesafety101

I suppose a good management system would include a system for recording method statements as they come in and records of who has read and understood them but a small site where ms will not be revised as a rule would possibly not. I have managed both and for the larger project I did keep a record of all method statement and revisions and formal tool box type talks to operatives who needed to know the updates. I don't think there is a requirement for individuals to sign their ms but it is a good idea IMO.
RayRapp  
#3 Posted : 18 May 2015 12:37:10(UTC)
Rank: Super forum user
RayRapp

Good question. Ideally method statements should be controlled the method is not so important as each site may adopt their own process. A MS should have basic information such as date, revision number and be signed off by a responsible person. It is good practice to include a briefing sheet for operatives to sign and counter signed by the responsible person (i.e. supervior, foreman, etc) giving the briefing, otherwise there is a danger that it becomes nothing more than paper safety. If the site has access to electronic information then a project folder could be provided for a suite of documents to include method statements. No system is perfect as I have seen even the best abused by poor practice - good luck.
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.