How to report an incident, near-miss or hazard.
About incident reporting in Logiqc
What is an incident?
An incident, near miss, or hazard refers to any event or situation that has the potential to cause harm, damage, or disruption within your organisation.
An incident is an actual event that has occurred, while a near miss is a close call or a situation that could have resulted in harm but did not.
A hazard is a potential source of harm or danger that could lead to an incident or near miss if not addressed.
Why report an incident?
Reporting incidents, near misses, and hazards is crucial for your organisation to identify areas for improvement, implement corrective actions, and prevent future occurrences.
By reporting these events, your organisation can analyse trends, identify root causes, and take proactive measures to enhance safety, efficiency, and overall performance.
This proactive approach helps your organisation mitigate risk, promote a culture of safety, and drive continuous improvement in operations and service delivery.
How to report an incident
These simple steps summarise how to report an incident in Logiqc. Click the info icon for details of each step.
- Describe the incident.
- List the people impacted and involved in the incident.
- List any equipment or assets impacted by the incident.
- Add any corrective actions or improvements you think should be considered to help prevent the incident from happening again.
- Select who should receive your report and manage what needs to be done.
- Select the teams and/or individuals who should be able to view the report.
- Upload any relevant records relating to the incident.
- Submit your report.
Incident details
In this section, you describe the incident, near miss, or hazard. See below for a description of what's required in each field.
Incident type
Choose the type of incident being reported. An incident is an actual event that has occurred, while a near miss is a close call or a situation that could have resulted in harm but did not. A hazard is a potential source of harm or danger that could lead to an incident or near miss if not addressed.
Incident area
Select the area of your organisation that the incident relates to.
Incident category and sub-category
Select the primary category that best defines the incident. This will reveal an additional sub-category menu where you can select a more specific category for the incident.
Did the incident involve company assets/equipment/vehicles?
Indicate if assets or equipment were impacted by the incident. If you choose 'yes', additional fields will be revealed further down in the form for recording specific details of the assets involved.
Date and time of incident
Select the actual or approximate date and time when the incident occurred.
Location of incident
Select the location within your organisation that the incident relates to.
Description of incident
Describe the incident eg. 'Medication dispensing unit dispensed incorrect dosage to post op clients.' You can add up to 2000 characters (300-500 words). Use the Additional comments field to add further information or upload or documents, emails, or photographs using Attach records.
Contributing factors
Describe the factors that you think contributed to the incident occurring. This helps to identify and address what needs to be done to prevent future occurrences. Contributing factors can include human error, lack of training, inadequate procedures or protocols, equipment malfunctions, communication breakdowns, and even external factors such as environmental conditions.
Assign a severity rating
The severity rating (often know as a SAC score) is a numerical score to rate the severity of the event. The score is typically based on the impact of incident, particularly when an injury occurred.
When you choose a severity rating, a recommended response will appear. To check that you've selected the most appropriate rating, click on the Guide button once you've selected the rating.
Immediate action taken
Describe what action you or others took when the incident occurred eg. 'Standard operating protocols were followed in full and relevant parties we notified.'
Persons involved
In this section you can enter the details relating to each person involved in the incident. Enter the details for one person and click OK. This process can then be repeated to enter multiple people.
Each person listed will appear as separate line items on the Persons involved tab on the Incident register which can be searched and filtered for generating reports.
For each person added, you can also include their contact details and information about any injuries they may have sustained related to the incident.
The Nature of injury classifies the type of injury sustained such as a burn or fracture.
The Mechanism of incident classification is intended to describe the circumstances that resulted in the injury such as a fall or being hit by an object.
The Injury classification broadly classifies the treatment or response required such as whether first aid or more serious medical treatment was required, of if no treatment was required but the person needed to take time off work.
Related or damaged assets
If you indicated in the Incident details section that damage to assets or equipment has resulted from the incident, this section will appear for you to complete.
In the Asset/s field you can choose from a list of assets in your organisation. You can select multiple items. If the relevant item is not in the list, select the free text option to describe the asset.
Identified issues and improvements
Click Add to suggest any improvements or corrective actions that should be considered to help reduce the risk of a similar incident happening again. Corrective actions should be coded as a 'non-conformance' in the Improvement type field.
When you submit the incident report, the corrective actions and improvements created here will automatically appear in the Improvements register and be assigned to the person who was identified to manage the issue.
Assign
Specify who should receive the incident report. This person will receive a task to manage the next steps. Additional people who should be notified can also be selected.
Note: In some cases, these fields may be pre-populated by business rules created by a system administrator.
Related business area
Select the business area in your organisation that the issue relates to or occurred in.
Related meeting
Select the team meeting responsible for monitoring the management of the event. This will automatically place the event on their meeting agenda.
Report this issue to
Select who is responsible for managing this type of issue. Only users with permissions to manage events will be displayed. The user selected will be notified immediately of the incident and will be assigned the task to manage the incident.
If you will be the person managing the event and you have the required permissions, select Assign to me. The Submit button will change to Next allowing you to advance directly to the next stage to manage the event.
Notify other users by email (optional) - Select who needs to receive an email notification about the event.
Note: Users sent notifications relating to the incident will need to be included in Access control to see the incident.
Access control
Set which users will have access to view the incident report. You can grant access to all users or specific teams and individual users.
All users can access
Select this option if you would like all users to be able to view the item.
Specify who can access
Select this option to control which users can view this item.
Teams
Select the team/s who need to view the item.
Individual users
Select specific users (if they are not included in the selected team/s) who need to view the item.
Who can view?
Click this button to see a list of users who can see the item based on your selection. The list will also include those users assigned to the item in the workflow. Note: Users with system level permissions to see all items will also be included.
Attach records
This component enables you to upload or link to records related to the issue eg. correspondence, emails, and photographs.
Record name
Name the record ensure the description is meaningful and easily found when searching. For instance, 'Photograph of damaged to vehicle XYZ 123'.
File or Link
Click on Choose file and navigate to the record on your computer. If you have links enabled, toggle to change the control to add a URL to the record. The URL must be a in a web (http://) or Microsoft SharePoint format (https://<company>.sharepoint.com/...).
Viewing permissions - Only users with permissions to see the item will be able to see attached records.
Submit
The green Submit button will save the form and progress the item to the next stage of the workflow. After an improvement is reported, it will progress through a series of workflow stages for management, response, and eventual closure. Learn more about workflows.
Select Create a related item if you want to create a separate linked item on another register when you save the form. A link between the two items will be displayed in each item's System event history. This may be useful when you want to suggest an improvement in response to the improvement.
System event history
The System event history will be displayed once the incident is reported. It's a chronological record maintained by the system detailing entries and changes made to the form including links to any related items created by users.
Click the '+' control on the right to expand the line item to see more information.
