A GUIDE ON HOW TO DEVELOP A WORLD CLASS INCIDENT MANAGEMENT PROGRAM

In July 2006, a bouncy castle with 30 people inside it, broke free from its moorings and took off into the air in a freak gust of wind. It flew 50 feet into the air, turned over, and travelled 150 feet before landing on the ground. The castle seriously injured 13 people and killed two. An eye-witness described the event thus: “I heard the snapping of tent pegs and a lot of screaming, then the inflatable flew up into the air and bodies were dropping from it. It was just carnage. There were people everywhere lying on the ground. Some had been on the inflatable when it took off, others were hit on the ground.”

Who would predicted an incident like this! Whilst most companies today – rightly so – focus on incident prevention, they are nearly impossible to mitigate completley so, if and when they do occur, you need to make sure your company is equipped to deal with it as quickly and effectively as possible. A proper incident management program is also a key part to any Business Continuity Plan.

Here is a brief outline on how you go about doing this:

  • Appoint the incident team

    The first step in any incident management program must be to appoint an Incident Leader. Someone who is ultimately reponsible for the implementation, maintenance and execution of the incident plan. They must be able to take charge when an unplanned event occurs, either personally or via their incident management team.

    This person will be responsible for other incident team members, ensuring they are properly trained, know the incident management program and how to execute it when required. They could be the OHS Manager, the HR Manager or, depending on the organisation, a specifically appointed incident manager.

  • Design and document your incident templates

Critial to any incident management program is a well designed template for the correct response to each incident that could occur. This template must ensure that all stakeholders can clearly understand the steps they must take when specific types of incidents occur. Stakeholders must have access to them and be versed on what to do (there’s no time to read up when in the middle of a critical incident).

Stakeholders must also be able to easily identify types of incidents, so that the correct action is taken and the right people advised. Reporting the severity of an incident is essential, as the same incident description can require 2 very different responses depending on how severe it is. Ensuring that stakeholders rate incident severity consistently is not an easy task and clear guidelines are needed to achieve this.

Some of these templates could include:

  • Accident Incidents
  • Force of nature incidents
  • Employee Incidents
  • Offense incidents
  • Security incidents
  • Workplace violence incidents
  • Workplace harrassment incidents
  • Environmental incident

Some of the rating criteria could be:

  • Life threatening
  • Severe
  • Major
  • Moderate
  • Minor
  • Insignificant
  • Gather and relate information

    Once an incident has occurred, information supplied late, inaccurately or incompletley and to the wrong people could cost lives, result in far more serious than necessary injury and / or cost your organisation a significant amount of money. You therefore need to be able to ensure you are able to quickly gather as much information as possible, that it is accurate and communicated to the right people. A process is therefore required to ensure stakeholders know how to go about this.

    With technology available today, and especially with incident reporting software solutions, it is not difficult to report incidents via your mobile device, as and when it happens. They also allow for pre-determined workflows, based on the type and severity of incident, upload of videos’s, photos and voice notes, so that the ability to communicate quality information is much improved. Designing and implementing a workflow process in this manner is quick and relatively simple to do.

  • Implement the incident management plan

    Now that you know the who’s and the how’s, its important to ensure that stakeholders can actually action the incident management plan once an incident occurs. Of course this takes training, not only of the incident management team, but all stakeholders in the organisation.

    As an organisation is in continual flux, training needs to keep pace with the constant changes. It is important therefore to ensure training is ongoing, not just for new inductees but for all members of the organisation, as their roles, responsiblities and locations change. Training needs to be such that it is not just a tick box exercise – remember lives could be lost with the incorrect action. It needs to ensure that stakeholders are properly versant on required actions and also on how to physically deploy those actions.
    The training itself must also be kept updated and any changes effectively communicated to all stakeholders.

    Continual testing of the incident management plan must take place all the time – including tabletop discussions and in-depth operational exercises – to ensure the plan is robust and keeps pace with the changing organisational needs.

    Version control and ongoing training is also something that is easily deployed using software solutions available today. These solutions allow for online access to material by stakeholders at convenient times and in a format that is easy to understand. They also allow for knowledge testing and knowledge rating.

  • Report and maintain your plan

    No incident management plan would be effective without reporting tools that allow you to analyse, track, trend and rate incidents. These reports will help you to minimise your risk of incidents by allowing you to better predict incidents. They also allow you to undersand, from a high level, what your macro business risk is and how best to protect your organisation. This information will also ensure your incident management program is properly maintained, as the reports will highlight gaps and areas where improvement is required.

    If an incident reporting software solution is being used, this information is easily extracted in easy to use formats.

Conclusion:

This may appear a daunting task, but fortunately in this modern world cost effective and easy to implement software solutions will help! Incident reporting software solutions, like the Rapid Incident Reporting software solution, will take care of all of these steps for you. They are flexible based on the size of your company, quick to implement and easy to use. Their years of experience ensure the implementation process is as painless as possible, minimise administration and let you get on with the job.

Companies like OVS Solutions (Pty) Ltd, the Africa Licensee of the award winning Rapid Global Software, have been delivering Health & Safety software solutions for over 18 years. Their only business is the continued development and improvement of their software, to make sure that the solutions keep pace with the ever-changing landscape. All their solutions come with mobile apps. (change this link text to ‘Click Here’) https://rapidglobal.co.za/products/rapid-app/ to see what their solutions offer.

OVS Solutions, the Africa Licensee of Rapid Global, also have a great support team who are available to assist with live or online demonstrations, user guides and relevant information you may require. They will share their tips on how to best maximize user adoption and can help you deliver on your plan!