Why Are Incident Reports Done So Poorly

​Let’s be honest! Nobody likes writing incident reports. They’re kind of annoying, time consuming and just another bit of paper work that you have to do on top of everything else! Added to this, so many schools and organisations make it difficult for their teachers and instructors to complete.
 
Consequently, when you combine added work with difficult to complete, this results in poor reporting, late reporting and quite often non-reporting of incidents. Ironically, WHS research has shown that the more senior a staff member, the less likely they are to complete a report. Added to this is the deterioration of memory that adversely impacts the accuracy and validity of any report. No matter how good someone thinks their memory is, the longer they delay in writing an incident report, the fuzzier and less accurate it becomes. Important details can be overlooked and left out. Such details about actions taken, mitigation or treatment, could become vitally important years down the track and without a rock-solid incident report, the person and the organisation can be massively exposed to a variety of potential liabilities. However, everyday things happen. The writing of an incident report is put off until ‘later’ and when ‘later’ comes, the events of yesterday or last week are nothing but a distant memory in amongst a busy life of work, family, traffic and cups of coffee.
 
Yet incident reports are critical to our understanding of what happened, causation, consequence and how to avoid it happening again. The ‘bury your head in the sand,’ ‘it’ll be right’ and ‘I’ll do it later’ options are not options at all and all incidents, no matter how seemingly minor or insignificant, need to be reported in a timely and accurate manner. Consistent and timely reporting can highlight patterns or risks which might otherwise have been missed.
 
With so many potential negatives of trying to get someone to write an incident report, no wonder they’re done so poorly. Add remoteness or overseas to the equation and you’re not getting anything wonderful or insightful anytime soon. The end result is an unintended exposure to liability and the inability to learn vital lessons from what went wrong. It was this exact situation and combination of factors which led me to develop the Xcursion software platform. I didn’t want to be doing incident reports at the end of a multi day expedition when I was tired and about to have a day off. I wanted to have it all done way before then. However, at the same time as a director of outdoor ed, I wanted incident reports sent to me from the field as fast as possible, so I could understand what had happened and help provide an appropriate response. Hence, I built the Xcursion mobile app to solve both my problems at once and in doing so, came up with a solution that made it easier, faster and a far more reliable way of doing incident reports.
 
What was the result? Suddenly, there was an increase in incidents!!! Well that’s probably not quite true. There were the same number of incidents, but now they were actually being reported. From this we could finally understand the prevalence of the type, severity and causation of incidents, with some reliable level of detail and accuracy, rather than… nothing.
 
Essentially, as soon as you make something easy for someone to do, then you have a greater chance of it being done. The more difficult and complex the task, the less likely you are to get anything. It baffles me that something so important is often such a low priority until a major incident occurs and everyone is demanding answers. Why not make it easy on everyone? No more inaccurate hand-written reports which are days or weeks old that you have to scan and file somewhere. Just leverage a bit of mobile tech to do it all for you and what can often take ages or not get done at all, could just take a couple of minutes and give you more detail than ever before, helping protect the first responder, students and with greater insight, help you reduce risk for every activity you do.