Safety risk and safety data: Exploring management line of sight

I have recently done a video presentation on a fatality at the Adelaide Desalination plant, which you can find by following this link.

Recently, I was reading some of the transcript of the South Australian Senate Inquiry into the desalination plant (which you can find by following this link), and was struck by one manager’s description of all of the activity undertaken in the name of safety:

We start with the inductions when new staff join the project. So, at 6.30am, usually three times a week—I attend probably two of them; I was in one yesterday—we induct new staff onto the job. The first thing I point out is the list of non-negotiables. The second thing I point out is for each person to look after their mate. It starts there. We then have a standard list of documents. I will read from this list, because it’s quite a large list. There is the HSC risk register, task specific for each job. There is a construction execution plan. There is a JSA, task specific.

We have daily start cards for each area, which is another thing I introduced. I am not sure if we gave you a copy, but it’s a small easily-filled-in card where a work team can assess the risks of adjacent trades, etc. So, that is a specific thing. We have a pre-start meeting every day. There are SafeWork instruction notices posted at each of the work areas. We toolbox the job weekly, because the pace of this job changes. You can go out there in two-day gulps and the whole access can change, so we need to make sure people see that. We have the non-negotiables in place. We have site and work-front specific inductions, which is what I told you about. Again, I attended one yesterday.

I have regular safety walks. I have trained all of my management team and the two layers beneath that to go on safety walks. We have our OHSC risk register. There is a just culture model in place. So, if I need to address an incident and it turns out that this person needs retraining or perhaps needs to be disciplined or work outside the fence somewhere, we use this just culture model for that. We have all been trained in that. There are safety KPIs for management. There is a safety enhancement committee, which is a mixture of workers and staff. I actually chair a weekly safety leadership team, and that’s improving safety over and above. We are looking to refresh it all the time. And so it goes on. I have two pages of this stuff.

Now, there may have been far more information that sat behind all of this activity, but it seemed to me to be a typical approach to safety management – and one that typically gives no insight into whether the risks in the business are actually being managed.

One of my particular areas of interest in the context of safety management is “management obligations”, and more particularly how managers (at all levels) get assurance that the health and safety risks in their business are being effectively managed. It is a concept that I have referred to before and written about (Smith, 2012) as “management line of sight”.

An area of speciality for me is management obligations training; courses that are designed to help managers understand their legal obligations for safety and health, and how their behaviour – what they “do” – contributes to effective safety management.

Over the last 3 or 4 years I have put the following scenario to the various courses:

Who here knows about a risk in their business or area of responsibility that could kill someone?

Invariably, most hands go up.

Who has safety information that comes across their desk on a regular basis.

Again – most hands go up.

OK. What I would like you to do is to think about the risk. Then I want you to think about the data that you have looked at in the past 3 months.

Pause ……

What does that data tell you about how well the risk is being controlled?

And then the lights come on, with the realisation that their organisations spend inordinate amounts of time and resources producing volumes of information that tell them nothing about whether risks in the business are actually being controlled.

This “gap” was most recently highlighted in the Royal Commission into the Pike River Coal Mine Disaster (Pankhurst et.al, 2012), in which 29 men died in an underground coal mine explosion in New Zealand. The Royal Commission noted the following:

The statistical information provided to the board on health and safety comprised mainly [LTI rates]. The information gave the board some insight but was not much help in assessing the risks of a catastrophic event faced by high hazard industries.

… The board appears to have received no information proving the effectiveness of crucial systems such as gas monitoring and ventilation. (My emphasis).

Typically, in a training course discussion there is no meaningful consensus on  what the “crucial systems” are in a business, much less how we prove that they are effective.

What we can say with a high degree of certainty is that traditional measures of safety performance do not prove the effectiveness of crucial systems – certainly LTI and other personal injury rates do not, and we have known that for at least 25 years. However, other indicators are equally poor in creating insight into the control of crucial systems. The number of management site visits do not enlighten us, nor do the number of audit actions that have been closed out, the number of “behavioural observations” don’t help, the number of people trained, the number of corrective actions completed, the number of JHAs or “take 5s” done and on it goes.

These things are all indicators of activity, which are designed to ensure that the safety management systems are effective, but ultimately, they leave us in no better position as far as understanding the effectiveness of crucial systems.

There is another interesting challenge that falls out of exploring management line of sight, and that is, what should I be looking at?

Historically, and as I touched on above, we typically consider safety in the context of harm and risk: what can hurt people and how likely is it that they will be hurt? But line of sight and assurance demands a wider gaze than hazards and risks.

The Royal Commission (2012, volume 2, p. 176) also stated:

Ultimately, the worth of a system depends on whether health and safety is taken seriously by everyone throughout an organisation; that it is accorded the attention that the Health and Safety in Employment Act 1992 demands. Problems in relation to risk assessment, incident investigation, information evaluation and reporting, among others, indicate to the commission that health and safety management was not taken seriously enough at Pike. (my emphasis)

“Crucial Systems” mean more than gas monitoring or ventilation. They are more than the control of physical risks. They incorporate broader organisation systems around hazard identification and risk assessment, contractor safety management, management of change, incident investigation and so on. All elements that are designed to work together so that the “system” as a whole is effective to manage risk.

If organisations are weak insofar as they cannot “prove” that physical risks are being controlled, the reporting, assurance and line of sight to prove that these other “crucial” systems are effective is almost non existent.

When was the last time you received a report “proving the effectiveness” of your incident investigations, for example?

What are the “crucial systems” in your business, and how would you “prove” that they were effective. Food for thought.

References

Pankhurst, G., Bell, S., Henry, D (2012). Royal Commission on the Pike River Coal Mine Tragedy. Wellington, New Zealand

Smith , G. (2012). Management Obligations for Health and Safety. CRC Press, Boca Raton

25 Years on: Remembering Piper Alpha

In the past few weeks I have been asked to do presentations and share my views about the legacy of Piper Alpha in this, the 25th anniversary year of the disaster.

For me, the positive legacy is the advancement in safety regulation, engineering and “safety in design” that has seen the improvement of the physical safety of high hazard workplaces. Safety in design has also improved the “survivability” of disasters so that when accidents to occur, their consequences are better mitigated.

The ongoing disappointment, however, is the persistent failure of management oversight and assurance to properly understand if health and safety risks are being managed. This is a failure that has played out in every major accident inquiry since Piper Alpha and continues to undermine effective safety management.

You can see a video presentation of these ideas and concepts here.

Fatalities, Insurance and failed paper systems: Hillman v Ferro Con (SA) [2013] SAIRC 22

On 16 July 2010 a fatality occurred during lifting operations at the Adelaide desalination water plant. A rigger employed by Ferro Con (SA) Pty Ltd was killed when he was struck on the head by a 1.8 tonne steel beam.

The Company, Ferro Con, and its Director, Paolo Maione were prosecuted under South Australian health and safety legislation, and in June 2013 were handed fines of over $200,000.

The case has attracted some attention because Mr Maione was able to call on an insurance policy to pay his penalty – effectively avoiding the punishment of the Court. It has long been thought, in my view correctly, that insurance to pay for effectively criminal penalties is counter to public policy and unlawful and it will be interesting to see if there is any “public policy” response to the decision.

Over and above the insurance aspects of the case, the judgement offers some good insights into the weaknesses of “paper based” safety management systems, a compliance mentality and lack of assurance. The judgement also explores some issues in the Principal/Contractor relationship.

You can see a video presentation about the case here.

Also, set out below are links to various references and materials referred to in the discussion if you would like to explore some of the concepts further.

Links to material referred to in the presentation.

Video presentation – case review: Capon v BHP Billiton Iron Ore Charge No. 1917/11

Video presentation – case review: Fry v Keating [2013] WASCA 109

Court judgement: Silent Vector v Shepherd & Anor [2003] WASCA 315

Court judgement: Hillman v Ferro Con (SA) Pty Ltd (in Liquidation) & Anor [2013] SAIRC 22

Article: Borys, D. (2009). Exploring risk-awareness as a cultural approach to safety: Exposing the gap between work as imagined and work as actually performed. Safety Science Monitor, 13(2), Article 3.

Are health and safety managers “company officers” and should they be?

This post has been prompted by recent activity on various blogs and safety discussion boards about whether a health and safety manager could be a Company Officer for the purposes of recently adopted health and safety legislation.

For those of you who follow this blog outside of Australia, part of this post is particular to recent legislative developments is Australia, although part of the discussion also looks at the broader accountabilities of health and safety managers.

Since about 2008, Australia has been engaged in a discussion about a legislative change agenda commonly referred to as “harmonisation”. The object of harmonisation was to achieve nationally consistent health and safety legislation across all jurisdictions in Australia. Although due to commence in 2013, and despite “harmonised” laws having been implemented in a number of jurisdictions, to date, the objectives of harmonisation have not been achieved.

You can read more about harmonisation here.

One of the key elements of harmonisation is a positive obligation of “due diligence” imposed on “company officers”.

Previously, under Australian law Company Officers could be held personally liable for breaches of safety legislation where offences occurred due to the company officers consent, connivance or neglect. A recent example of this type of case was the Western Australian decision, Fry v Keating, and you can see a presentation of this type of case here.

The due diligence obligations mean that relevant individuals must demonstrate positive actions to be satisfied that health and safety risks are being effectively controlled. So for example, the “model bill” used to frame harmonised legislation provides that due diligence includes taking reasonable steps:

  • to acquire and keep up-to-date knowledge of work health and safety matters; and
  • to gain an understanding of the nature of the operations of the business or undertaking of the person conducting the business or undertaking and generally of the hazards and risks associated with those operations; and
  • to ensure that the person conducting the business or undertaking has available for use, and uses, appropriate resources and processes to eliminate or minimise risks to health and safety from work carried out as part of the conduct of the business or undertaking; and
  • to ensure that the person conducting the business or undertaking has appropriate processes for receiving and considering information regarding incidents, hazards and risks and responding in a timely way to that information; and
  • to ensure that the person conducting the business or undertaking has, and implements, processes for complying with any duty or obligation of the person conducting the business or undertaking under this Act; and
  • to verify the provision and use of the resources and processes referred to above.

Given that harmonisation is about legislation aimed specifically at managing health and safety risks, it does suggest two important questions: Could health and safety managers by company officers for the purposes of the due diligence obligations, and should they be?

In my view, the answers are “probably not”, and “yes”.

Although health and safety managers, are often “senior managers”, they are not by default company officers. The term “officer” of a corporation is defined by s 9 of the Corporations Act 2001, and relevantly for this post includes a person who makes, or participates in making, decisions that affect the whole, or a substantial part, of the business of the corporation.

A relatively recent case looking at the issue of who may be a company officer was Shafron v Australian Securities and Investments Commission [2012] HCA 18, which you can access here. The case was one of a series of cases that concerned the prosecution of a number of company officers and executive managers of James Hardie arising out of disclosures by the company over its ability to fund potential asbestoses liabilities.

Mr Shafron was both Company Secretary and the General Legal Counsel, and the relevant arguments turned on whether Mr Shafron could be a company officer in his capacity as General Legal Counsel.

Part of the argument run by Mr Shafron was that he could split the two roles, Company Secretary and General Counsel; so that when he was acting in his capacity as a Company Secretary, he was a Company Officer, but that in his capacity as General Counsel.

That majority of the High Court “greatly doubted” that the capacities could be spilt in that way, but usefully for this discussion went on to discuss whether Mr Shafron was a Company Officer when acting in his capacity as General Counsel.

In forming the view that Mr Shafron was a person, who makes, or participates in making, decisions that affect the whole, or a substantial part, of the business of the corporation  the High Court made a number of observations.

First, that Mr Shafron was a senior officer, the second or third most senior executive in the company.

Second, Mr Shafron was one of a small group of three people who were “responsible for formulating” the relevant proposals.

Third, Mr Shafron’s “participation” went beyond merely providing advice – he played a large and active part (along with two others) in putting together the proposal that they chose should be put to the Board and adopted.

What is clear from the decision is that in some circumstances, whether a person is a Company Officer is situational – it is not fixed. So a person in making (or participating in making) some decisions may be regarded as a Company Officer, but in other cases may not.

On the face of the reasoning of the High Court, it is difficult to envisage too many circumstances where a health and safety manager would be likely to be found to be a Company Officer.

In my experience, health and safety managers are not typically amongst the senior echelon of executive managers, nor do they put proposals directly to the Board. To the extent that health and safety management proposals are put before a Board, they often come via a CEO or “sustainability” manager who put their own imprimatur on the proposal.

So to answer the first question, could health and safety managers be company officers for the purposes of the due diligence obligations? In my view – I cannot rule it out, but probably not,

As interesting (or otherwise) as this discussion might be, the more fundamental question is whether health and safety managers should be regarded as company officers – or at least have equivalent obligations of due diligence under safety legislation.

By way of comparison, there was and continues to be ongoing debate about how the mining industry is some parts of Australia will implement the principals of harmonisation.  At one point, a draft set of what were referred to, as “non-core” mining regulations were prepared, and without going into the rationale behind, and operation of the non-core regulations they did propose:

  1. The appointment of a senior person on a mine site who would be responsible for safety under the regulations – the Site Safety executive or SSE; and
  2. That the SSE would be “deemed” a company officer for the purposes of the health and safety regulations.

In doing this, the regulations were clear that the positive obligations of due diligence would apply to that position.

There seems to me to be no reason in principle why a similar approach could not be adopted in relation to health and safety managers. And if you look at the due diligence obligations as set out above, there is no reason that I can think of why you would not expect a health and safety manager to be across all of those requirements.

So, even is a health and safety manager may not be a company officer, there is no reason why they should not have the positive obligations of due diligence. After all, where would we expect the company officers to get the information top discharge their obligations if not from the health and safety manager?

Transpacific Industries: Disciplinary action as a safety control

This is a case I have looked at before, and often use in management training to help explain the concept of reasonably practicable, and the relationship between reasonably practicable and the hierarchy of controls.

I was prompted to post it following the release of Safe Work Australia’s guidance material on reasonably practicable.

The case involved the prosecution of Transpacific Industries following a fatality in 2009. In an earlier, almost identical  incident, Transpacific had responded to a breach of its procedures with what the Court described as “robust disciplinary action“. When the repeat incident occurred in 2009 the question that was argued was whether the earlier disciplinary action was a “sufficient response“: Was it reasonably practicable? You can access the video discussion of the case here, and a copy of the case here.

To receive future updates and case studies, please subscribe to the blog, or follow me on twitter.

Regards.

Greg Smith

Unfair dismissal, delphic motherhood statements and other observations on safety documentation

Delphic adj. ambiguous, enigmatic, obscure. Also Delphian [L Delphicius, from Gk Delphikos of Delpji (the ancient city in central Greece, famed for its oracle of Apollo, which was noted for giving ambiguous answers.) (The Macquarie Dictionary)

Let me apologise for the somewhat ‘delphic’ nature of the title for this blog, but it is an accurate description of a recent case and other findings, which has led to the observation on safety documentation. Although I might say less of an observation and more an update on, or restatement of, a long running concern that I have had about how safety documentation continues to actively undermine our efforts to create safer workplaces.

First are the recent unfair dismissal proceedings in Paul McGrath and Maitland Hayward v Sydney Water Corporation t/as Sydney Water [2013] FWC 793.

The case involved two workers who had their employment terminated after apparently breaching their company’s ‘lock out/tag out’ (LOTO) procedures. In the end, the termination was overturned and they were reinstated to their original positions. A number of the reasons for the decision turned on matters particular to Australian unfair dismissal laws, and included things such as:

• The long period of service of the two workers.

• The long and unblemished safety records of the two workers.

• The workers’ age and work history.

• The impact of the termination on the workers.

• The workers’ remorse.

However, the quality of the LOTO procedure was also a factor. The tribunal dealing with the claim noted:

• The LOTO procedure did not expressly detail the steps required to be taken to isolate power sources.

• The LOTO procedure requires formal training every two years, which did not occur.

The tribunal noted that there was “some attraction” in a submission that Sydney Water was itself in breach of its own policy.

• Evidence of experienced electricians was that the LOTO procedure was, at best, unclear, and at worst, confusing.

The tribunal noted that Sydney Water seemed to acknowledge this problem by undertaking extensive retraining of its employees on the procedure, because employees were concerned that they could also be subject to disciplinary action for a breach of the procedure.

The issue of the quality of safety documents in a safety context was also explored in the Royal Commission into the Pike River Coal disaster. The Commission noted in that case:

By November 2010 there were over 398 documents in the electronic system. Of these 227 were in draft as they were not signed off by two managers, although they were still used in the meantime. The number, and length, of the documents posed a challenge to the credibility of the system.

Although many of the documents were helpful, there were problems, not only with the sheer volume of material, but also with some of its content. For example, in 2010 two consultants and a Pike manager assessed the ventilation management plan and concluded it needed a complete review. (Volume 1, page 73)

Unfortunately, there is nothing surprising in this. The quality of safety documentation has been implicated in most major disasters for the past 25 years. And again, unfortunately, the response of the safety profession (and others) seems to be to keep doing the same thing and expect a different result. A few examples should suffice to make the point:

Longford Royal Commission: Fire and explosion at Esso’s gas plant in Longford, Australia. Two fatalities.

Esso’s [safety management system], together with all the supporting manuals, comprised a complex management system. It was repetitive, circular, and contained unnecessary cross referencing. Much of his language was impenetrable. These characteristics made this system difficult to comprehend both by management and buy operations personnel. (Page 200)

Montara Commission of Inquiry: Uncontrolled release of hydrocarbons off the north-west coast of Australia on 21 August 2009. No fatalities.

A number of aspects of PTTEPAA’s Well Construction Standards were at best ambiguous and open to different interpretations. The fact that a number of PTTEPAA employees and contractors interpreted aspects of the Well Construction Standards differently illustrates the ambiguity and inappropriateness of the Well Construction Standards. (Page 9)

The Deepwater Horizon: Fire, explosion and uncontrolled release of hydrocarbons in the Gulf of Mexico in April 2010. 11 fatalities.

If you look at the [Transocean’s safety] manual, you’re really impressed by it. It’s a safety expert’s dream. Everything anybody could ever imagine is in there. …because as one looks at it, everything under the sun is covered. It’s hard to see at a particular place somebody saying symptoms of that or this. If you see that, do this. This is not said by way of criticism. People have tried like hell in this manual to get it right. But it may be that when time is short, there might have been different ways to make clear exactly what should have been done in a short period of time. (Page 168-169)

I do not have any firm evidence about why this continues to be a problem, but I do have a number of observations based on my experiences over the past couple of decades.

Some of the issues appear to be systemic, for example, it does not seem to me that many health and safety professionals receive training in writing quasi-legal documents – which is ultimately, what safety management documentation is.

Another issue is the continuous “layering” of the safety documentation. This is often evident after an incident where the automatic response appears to be to amend or write a new procedure. More often than not, this is done without actually understanding why the initial procedure failed. Over time, this builds a volume of safety documentation incapable of being implemented.

However, the biggest concern I have observed in the last three or four years in particular is the ubiquitous “thumb drive” or USB stick. More and more we are observing safety documentation that has not been developed for a business or a particular risk, but rather has been cut and paste from some other organisation with no real regard for its application.

When you consider the quality of safety documentation in a general sense, it is not unreasonable to conclude that nobody is really reading these documents with any care or attention. I find it extraordinary how often I have to deal with safety management plans and other documents that contain the name of a totally unrelated company. Clearly the document is nothing more than a cut and paste from some other plan, but has been signed off by four, five or move different managers – yet even something as basic as the wrong company in the documentation is not being picked up. If the people responsible for developing and approving these documents were not reading them, why on earth would we expect the workforce to?

OK. So what does this have to do with the oracle of Apollo? It is taken from the Montara Commission of Inquiry:

The Inquiry also considers that (i) the Hazard Identification (HAZID) workshops which were conducted between PTTEPAA and Atlas to identify and manage risks at Montara; and (ii) the Safety Case Revisions/SIMOPS Plans which were produced by both entities, were pitched at far too great a level of generality. For instance, the workshops and documents did not deal in any specific way with management of barriers. Moreover, the SIMOPS documents were replete with delphic ‘motherhood’ statements, such as the following:

Safety management in the field is primarily the responsibility of the Vessel Masters/Superintendents, FPSO OIM, Rig OIM and WHP Person In Charge (PIC). The prioritisation of all activities in the Montara field is the responsibility of the PTTEPAA Project Manager. However, control of the individual activities during the field development remains with the relevant supervisors.

All parties in the Montara field development shall have clear structuring of HSE interfaces to ensure that there is no confusion as to: approval authority; roles and responsibilities of personnel; organisational structures, management of HSE; operating procedures; reporting structures; and SIMOPS. (page 135)

In the end, if our safety documentation does not provide good guidance about how the health and safety risks in the business are to be managed, what value does it add? And if it cannot be understood by the people expected to implement it, if it creates ambiguity and confusion, it is not overly pessimistic to think that it could be undermining our efforts to create safer workplaces.

Directors conviction in relation to workplace fatality upheld

On 23 April 2013 , the Western Australian Supreme Court confirmed the conviction and increased the penalties of two Company directors charged in relation to a workplace fatality.  The charges against the Directors aleged “neglect” undr section 55(1) of the Occupational Safety & Health Act 1984 (WA).

You can access a copy of the case at the following link:

Fry v Keating [2013] WASCA 109

or see a short presentation about the case here.

What should your health and safety manager know?

In November 2012, the Pike River Royal Commission[1] (Commission) published its report into the underground coalmine explosion in New Zealand in which 29 the miners were killed.

The Commission made some very clear and unambiguous observations about the sort of information that senior executive management, up to and including the board, should receive about health and safety.  The Commission (2012, volume 2, p. 53) stated:

The statistical information provided to the board on health and safety comprised mainly [LTI rates]. The information gave the board some insight but was not much help in assessing the risks of a catastrophic event faced by high hazard industries. … The board appears to have received no information proving the effectiveness of crucial systems such as gas monitoring and ventilation. (My emphasis).

I do not know how long the safety profession has understood that statistical information about injury rates provides no meaningful insight into the effectiveness of safety management systems, yet it persists as a fundamental measure of performance.

What major accident inquiries of the past 25 years, and the Commission make clear, is that effective health and safety management requires more.

However, I think that there is a legitimate question mark over the health and safety profession’s capacity to deliver truly effective health and safety management.

I have been doing a lot of executive level assurance work lately: Working with senior managers and boards to help give them insight into whether or not the health and safety management system is operating effectively. Often, the starting point for this work is to sit down with the most senior health and safety manager of the organisation and asked the question:

What are the key things that I should be concerned about, and how do we know that they are being properly managed?

More often than not, the senior health and safety manager cannot answer those questions and they are often very reluctant to give an opinion about whether or not the safety management system is operating effectively. In a number of cases, the health and safety manager believes that it is not their job to know if the health and safety management system is working effectively – that is the job of line management.

For what it is worth, in my view this is a complete misinterpretation of the notion of line management responsibility, and a complete abrogation of the obligations of a health and safety professional.

I believe that health and safety professionals are responsible for building a system that is effective to control the health and safety risks in a business. It is not the job of the health and safety professionals to ensure that that system is implemented; that is the responsibility of line management. However, it must be the obligations of the health and safety professionals to know whether that system is effectively implemented and to be able to advise the organisation one way or the other.

The Commission (2012, volume 2, p. 176) also stated:

Ultimately, the worth of a system depends on whether health and safety is taken seriously by everyone throughout an organisation; that it is accorded the attention that the Health and Safety in Employment Act 1992 demands. Problems in relation to risk assessment, incident investigation, information evaluation and reporting, among others, indicate to the commission that health and safety management was not taken seriously enough at Pike.

Typically, the senior executives in the organisations that I work with have never received a report or a presentation from anyone that gives them assurance that critical health and safety system elements are working. True, they have never asked for it but they did not know they needed to and nobody has ever told them otherwise.

They are not given advice that elements like incident investigation, hazard identification, risk assessment and so on are actually being implemented in accordance with the requirements of the documented system and are operating effectively (or not) to control the risks that they were designed to control.

The fundamentals of safety management have not changed:

  • Do you know what the hazards in your business are?
  • Do you know the risks that arise from those hazards?
  • Have you developed controls to manage those risks?
  • Are the controls implemented and effective?

What we cannot hide from, is that effective safety management and governance requires that we provide honest and accurate information to the most senior levels of an organisation about the crucial safety system elements and critical risks in our business – whether those elements are effective, and those risks are controlled.

Currently, it appears that as a “profession”, we do not, and we may not even be equipped to.

As a health and safety professional, ask yourself:

  • What information does your board get?
  • Is health and safety taken seriously enough in your organisation?

And most importantly, how do you know that the safety management system is operating effectively and the risks in your business are being controlled?


[1] Pankhurst, G., Bell, S., Henry, D (2012). Royal Commission on the Pike River Coal Mine Tragedy. Wellington, New Zealand

Zero harm and reasonably practicable: Inherently contradictory?

There is a lot of discussion in safety circles around the concept of zero harm and its place in safety management (see the following example).

On one side of the debate proponents of zero harm say that it is an “aspiration” rather than a hard target, and that aiming to prevent all injuries is the right thing to do.

On the other side, the argument suggests that the use of zero harm actively disengages the workforce from safety: “They” do not believe in zero harm and it is just another corporate slogan used as a substitute for addressing the workforce’s genuine safety concerns.

My personal view is that slogans like zero harm probably do undermine safety, at least insofar as the organisations’ conduct is inconsistent with their statements.

I might leave that part of the debate to people far better placed to argue it than me, but recently I was involved in a discussion with a client about zero harm in a slightly different, but related context.

Under the safety management system the client strove to achieve Zero Harm by managing all risks as far as “Reasonable Practicable”. This seems to be the stated aim of most organisations to a greater or lesser degree.

What the client did not understand was that reasonably practicable is a legal concept that inherently recognises that accidents do happen.

The law is clear that it is not the responsibility of the employer to ensure that accidents never happen, rather an employer must do everything practicable to ensure that its employees are not exposed to hazards.

So, if we genuinely believe in zero harm, and want to do more than the minimum “legal” requirements, then surely we should adopt a philosophy or measure of safety performance that is consistent with what we want to achieve? Surely there is no place for the concept of reasonably practicable in an organisation that believes in zero harm?