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
Admin  
#1 Posted : 27 July 2007 14:11:00(UTC)
Rank: Guest
Admin

Posted By mark foster
Despite applying all the usual pressures I have been unable to generate a culture of reporting incidents from our team of site based installation engineers. As a result I have been coerced by our H&S comittee into implementing a new system where each engineer has to submit at least one report a month. I have suceedded in softening this requirement to one near miss / accident report or safety observation.

This has promoted some debate as to what constitutes a near miss, I would welcome any input the forum has!
Admin  
#2 Posted : 27 July 2007 14:27:00(UTC)
Rank: Guest
Admin

Posted By Shane J
A near miss incident would have to be defined as some that in other circumstances could have caused an accident.


Object falls from a height onto a walkway = Near miss.

Object falls from a height onto a walkway (where someone is walking) = Accident

So as a formula. Hazard + Occurrence = Near miss
Hazard + Occurrence + Result = Accident.

Hazard = Anything that can cause harm
Occurrence = Mechanism for that harm to be caused

Result = Injury, loss/damage to systems.
Admin  
#3 Posted : 27 July 2007 14:48:00(UTC)
Rank: Guest
Admin

Posted By Steve B
Or to put it in simple terms:

Near Miss
An event or condition which if not rectified or left unattended may result in personal injury, damage to plant or other loss.



Regards
Steve
Admin  
#4 Posted : 27 July 2007 15:13:00(UTC)
Rank: Guest
Admin

Posted By Edward Shyer
Mark,

By softening the reporting of near miss incidents to only requiring one to be reported a month are you not indicating that near misses are not all that important as they are not all going to be reported.

Better to have stuck by your guns and insisted that all near miss incidents are reported. It would also be a good idea that they are all also investigated. This will show your employees that you are taking this seriously and not just using the report for lip service.

regards

Ted
Admin  
#5 Posted : 27 July 2007 15:25:00(UTC)
Rank: Guest
Admin

Posted By mark foster
Thanks Ted I fully take your point but the problem is that if as a manager supervisor you do not witness the near miss yourself it is difficult say what is not being reported. The staff in question are roaming teams of service and installation engineers working away fom the organisations offices so it is difficult to be constantly looking over their shoulder.

The actual requirement is AT LEAST one a month, currently I'm getting none so I feel this is a realistic minimum. The concern is if we insisted on a higher number people might just make them up!

The process of education and training will have to continue and its the definitions of near misses that I want to effectively convey. We already have two very different definitions as responses
Admin  
#6 Posted : 28 July 2007 08:32:00(UTC)
Rank: Guest
Admin

Posted By Dave West
Make it simple.
Admin  
#7 Posted : 28 July 2007 08:50:00(UTC)
Rank: Guest
Admin

Posted By Ian G Hutchings
Hi Mark

I think the problem may be in front of you, in your question. 'I have been unable to generate the near miss reporting culture'. Presuming that you are the health and safety adviser/manager, here lies the problem. You will struggle to be able to do this.

The only people that can generate the culture are the directors, managers and front line staff/supervision. If you try and drive this alone it is likely to fall down, unless you have an unusually conscientious group of people.

You probably need to take a longer and more educative approach, rather than a directive one. People need to have a genuine value for why they should report a near miss and really want to do it. This needs to then be supported by thorough investigation, led by the manager not you.

I am concerned about the targets. I have come across this in the past and it, in my opinion, is not effective in the long run. People will then be doing it for the wrong reasons.

I am happy to have a chat next week or via email link if you want some more thoughts and what I have done previously to make this work.


All the best

Ian
Admin  
#8 Posted : 28 July 2007 08:54:00(UTC)
Rank: Guest
Admin

Posted By Ian G Hutchings
Sorry, forgot my definition of a near miss.

'A situation which could have led to injury, ill health, property damage or damage to the environment, had the circumstances been slightly different'.

Ian
Admin  
#9 Posted : 28 July 2007 11:39:00(UTC)
Rank: Guest
Admin

Posted By Pete48
Ah, the near miss. I remember her well. She sat alongside me in everything I did, always near and yet so far away. Move towards her and she moves away, move away from her and she gets annoyed and causes an accident.

The biggest issue with near miss reporting is "what happens next" or "can anything actually be done about the circumstances or events". If you can solve that part, then you will get better reporting of what most of us would call "near miss".

I doubt you will ever get individuals to report any event in which they feel they, or their workmates are the main contributing factor. (e.g tripped on the step or over my hammer which I had left laying there)
The only time I ever had any lasting success with the principle of reporting non-injury incidents was when we classed them as safety defects. Just report anything that is not as it should be or where you had difficulty in following the SSOW.
Admin  
#10 Posted : 28 July 2007 12:11:00(UTC)
Rank: Guest
Admin

Posted By John N Jones
Mark,

How easy is your reporting system?

to report a near miss at our site we can use the computer, near miss form, tell your supervisor, tell a union rep and a recorded near miss telephone line with a memerable number.I'll even take them on the back of a fag packet.
if your engineers are in the field they are likely to have mobiles so this may be the easiest way of getting your reports in.
More work for you but the result you want in the end,

John
Admin  
#11 Posted : 30 July 2007 23:21:00(UTC)
Rank: Guest
Admin

Posted By Chris Jerman
I think that we're all missing the important step here. When we talk about accidents, what we really mean is injuries. That's the difference between a near miss and an accident, if I read your definitions correctly. People are quite used to reporting accidents, because we put them in the accident book - ie we record the injury and treatment but little about the event because that's seen as investigation and we don't teach 1st aiders much about taking details concerning the event.

So which is more important. An EVENT that resulted in a minor injury or a near miss that could have resulted in a fracture? Answer - well that's not enough information. The key here is to use a forecast of the reasonable limits of predictable injury as we do in risk assessment. (remember incident investigation is only risk assessment in reverse; what are you doing what could go wrong? - what were you doing what did go wrong?) Apart from traditionally, we only state the ACTUAL injury in investigation not the reasonable worst.

For true synergy between the reactive and pro-active we must get away from 'injury' completely and focus on the event itself. How many times do we hear "That was an accident waiting to happen" or "If I had a pound for every time that had happened"? How come someone has to be injured before it gets attention? Well, because historically, we ask people to report injuries not events.

Ditch 'accident' and near-miss and go for 'incident' or 'event' reporting. It's tough to get going, but believe me it's the right way.

Action, effort and priority should be driven by POTENTIAL, not forgetting likelihood of recurrence of course. So, if an event results in minor injury (actual) and reasonable worst injury (virtual) would never be more than minor - go and look at something more important like an event with actual of zero but virtual of major. To use anything else as a basis for driving the system is totally reactive.

See the point?

C
Admin  
#12 Posted : 31 July 2007 11:25:00(UTC)
Rank: Guest
Admin

Posted By Bob Shillabeer
Am I understanding you correctly that you are being pushed into introducing a process of reporting even if nothing has happened just because someone fails to report something?
This is a muggs game they will soon let the system fall into disrepute. Forcing someone to report something will lead to them reporting false incidents just to comply with the incident reporting requirement. Would it not be better to explain to everyone that reporting near misses is not a diciplinary thing but more of a fact finding thing to help create a safer workplace. Not all employees are against this you know, in fact most people when treated correctly can be a great source of info.

For God's sake treat people with a bit more respect and explain to them why it is important to report true incidents not force them to report fictisious things in order to justify your position.
Admin  
#13 Posted : 31 July 2007 12:25:00(UTC)
Rank: Guest
Admin

Posted By Robert.
Why not re-name as near loss reporting as an means to prevention or control as this could cover environmental, safety, quality, rework, financial.
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.