Event and Incident Report Software (Tutorial)
There’s a famous phrase in business, “what gets measured, gets managed“. In other words, if you can’t measure it, you can’t manage it. This goes a long way to explaining why reporting incidents and events is so important to companies. If it is not reported, it is not managed. However, just reporting an incident or event is not enough. The speed of a report and the quality of the report itself are both important. The full incident report software tutorial is further below.
However, just reporting an incident or event is not enough. The speed with which it is reported and the quality of the report itself are both of crucial importance.
Click here if you want to go straight to the tutorial.
Quick and Rich
Getting reports to decision makers in a timely fashion is big business. Think about the entire financial reporting industry, billionaires like Mike Bloomberg made their fortune by getting market data to traders quicker than any one else.
Although less well paid, there is still a need for incident report software in facilities management to be swift. In major incidents for example, decisions made in the first hour after an incident determine the next 72 hours. As a result, a report’s value diminishes over time.
Of equal importance is the need for good quality reporting. If a report does not have enough useful information it’s useless. Rich report formats that include media, images and video are now very popular because they give the decision maker a better idea of what has happened.
Fortunately, SIRV reporting and tracking software makes reporting quick and rich. You can create forms that use lots of easy to complete data capture tools, such as drops downs and lists. You can also send reports real-time via email to whoever requires the report.
When Are You Reporting? Before, During or After?
Typically people report:
- After an incident.
Imagine for a moment that you’re stood in a loading bay and you see a truck reversing. It narrowly avoids hitting someone. You may record this as a near miss incident, occurring before. One week later in the same loading bay a truck hits someone causing them an injury. You may report this as an incident, immediately after the incident. One day after the truck hits someone you are conducting an investigation into the loading bay injury and its consequences. You may record this as a post incident report, occurring after.
This way of thinking is how the risk industry analyses incidents. Often referred to as the Bowtie model because of its appearance, it’s a smart way to think about how you want someone to use your incident report form, before, during or after.
Incident Vs Event
SIRV allows users to build forms for incidents or events. Both are nearly identical however, event forms do not automatically include location and time.
Events and incidents are kept separate in SIRV because of the assumption that incidents are negative and events are neutral. If SIRV placed events and incidents together analysis would be made difficult, a chart would reflect a mixed message.
One way to think of incidents and events is to imagine the following: A light bulb has been smashed by someone. This is building damage, it is harm done to your company and therefore negative, an incident. However, if a light is not working owing to a light bulb blowing, it is building maintenance, expected and therefore recorded as an event.
Typically, negative occurrences are incidents, for example theft and injury etc. Whereas, are checks and internal reporting such as return to work forms, CCTV checks etc. A comprehensive list of commonly used forms is available here.
SIRV: Event and Incident Report Software Tutorial
Note: The below security incidents and events tutorial applies to both incidents and events. For the purpose of this article we will refer only to incidents.
Lets look at how to:
- Build incident report forms
- Add image tiles to incident report forms
- Report incidents
- Analyse reported incidents
1) Build Incident Report Forms
SIRV allows you to build as many incident reports as you like.
We strongly encourage you to build different types of reports for different types of incidents. This is because catch-all forms often include irrelevant fields and questions. For example, if you’re a security guard reporting lost property do you really want to complete a section asking about skin codes?
A form’s attribute can have advice added to accompany it. This advice appears as a icon with the letter ‘i’ next to the attribute.
Once the icon is selected a pop-up is displayed. This advice can be made-up of text, tables and/or contact details.
2) Add Image Tile
Once an incident form is made you can decide to add a text or image tile.
Regardless of your selection once an incident form is made it will automatically appear on the SIRV website and the mobile app, under the tile named ‘library’.
If you want to add the incident as a specific tile on the mobile application itself then you probably want to give it an image tile.
To show a dedicated image tile on the mobile app you will need to to go ’tile configuration’ (Settings>Mobile>Tile Configuration).
The following video takes you through how to add an image tile and configure the look of the mobile application:
3) Report Incidents
Incidents are made on both the SIRV website and the SIRV mobile app.
The difference between recording an incident on the mobile app and SIRV website are as follows:
- Some features, such as the camera are only available on the mobile app.
- If you have no data connection you can still use the mobile app to create incidents. These are held locally and submitted when data connection is re-established.
- You can ‘store’ incomplete incidents on the mobile app. Access is possible at a later time by going to the settings menu. Once a stored incident has been submitted it’s removed from the mobile app and seen on the SIRV website.
The video below takes you through how to report incidents:
4) Analyse Incidents
SIRV provides two options to review recorded incidents:
- Search Incidents
- Analyse Incidents
View any incident using the filter search form. From here you can take a look at any incident and perform one of the following actions:
Every incident automatically has a ‘history’ section allocated to it. This allows user of the SIRV website to add a narrative to the incident. Each entry has a history field, timestamp and the name of the user.
It’s not possible to delete an incident. However, new versions of an incident are made.
By selecting ‘Edit’ you’re able to change fields in the incident and re-submit. The new version of the incident has a version number (for example version 1, version 2 etc). The latest version of an incident will automatically appear in any future search results. However, the old version(s) remain accessible, simply select ‘include old versions’ in the search parameters.
This action allows you to roll forward an incident and its content. A designated user can then download it onto their mobile app. This is useful when you want to carry forward content from a previous incident.
Similar to the ‘Allow Load’ functionality, this feature means you can load the incident and make changes to it through the SIRV website.
Format for Print
Select this option if you want to create a PDF copy of an incident. The PDF will include updated history along with all the other information included in the incident (except video).
Once you have performed your incident search you van download the information into a CSV file. After an incident search, select ‘Back To Incident Search’ and then select ‘Download’.
This feature allows you to build four different graph types:
To build a graph first select your criteria then opt for the different variables you want to show. Bear in mind a pie chart can have only one variable, line/bar chart two and a bubble graph can have up to three variables.
The bubble graph is dynamic. It’s popular with a wider audience that are less familiar with your day-to-day activity. It’s ideal for monthly, quarterly and annual security reviews.
A PDF conversion of the pie, line and bar charts is possible.
Event and Incident Report Software Tutorial: Bonus – Alarms
Can you predict the future? Have you ever wondered whether recording incidents and events could help you predict them occurring in the future? We include a threshold alarm feature. Similar to those used by retail banks it provides incident and event pattern recognition. Threat sensitive companies find this feature valuable.
The nature of incidents are changing all the time. However, good reporting rules remain the same, useful reports delivered in a timely manner.
If you put effort into establishing a good reporting culture, along with a reporting system fit for purpose then you will measure more and get more done.