Incidents

The Incidents Module provides users an easy-to-use way to gather information from the community, catalog details of an incident, investigate the incident, and analyze trends over time.

Incidents may be reported in many ways, and Salute makes it easy to gather information directly via the Community Portal or track information if an incident is reported via phone/radio/email/in-person.

Incident Reporting Request

The most efficient and common way that incidents are reported to Salute is via the Community Portal. By selecting Request/Report, from the landing page, Community members can report an incident to the safety team.

Incident Report on Salute Portal 

Once an incident has been submitted, it arrives in the request section of the Salute Portal.

To access Incident Reports

1. From the Salute landing page, select Requests from the Administration module
2. From the Requests landing page, select Event Reports
3. On the Incident Report landing page, you will see two tabs, Open and Completed, which separate Event Reports by Status
4. Once an open Incident Report is selected, you will be directed to the specific report page
5. On this page, in addition to the information submitted by the community portal member, safety teams can classify the incident, and assign the follow-up to a team member
6. Once the information is confirmed, selecting Resolve will allow the user to either dismiss the report, or start an Incident for investigation within the Incident module

Using the Incident Module

The incident module is used to review and manage all the incidents that occur within the organization. 

To access the Incident Module:

1. From the Salute landing page, select Incidents from the Events modules
2. The Incidents landing page allows users to:
   1. Select an individual incident to see more detail, add information, or conduct an investigation
   2. Filter the list by selecting a column header (can do multiple filters) to see a select list of items
   3. Create a new Incident
   4. Export the item details to excel for additional analysis
3. Once an Incident is selected, the detailed Incident screen provides you the ability to track specifics of an Incident, including:
   1. Overview
      1. Incident ID and Creation Date (Salute assigned)
      2. Status (Open, Completed, Recurrence Prevention On-Going)
      3. Responsible Person: Used to assign ownership, can change during the course of an incident investigation based on stage (reporting, investigation, corrective actions, or recurrence prevention)
   2. Details
      1. Source: How the incident was reported
      2. Created By: Who initiated the Incident record within Salute (defaults to logged in user)
      3. Date & Time of Occurrence
      4. Building
      5. Floor
      6. Space / Room 
      7. Department
      8. Reported By: The person who reported the Incident to EHS
      9. Date Reported
      10. Follow-Up Contact Detail
      11. Incident Owner: May be a manager or departmental lead that should receive information about this incident
      12. Incident Type: Pulls from a list of incidents types maintained by Salute but custom to your organization
      13. Incident Title

1. 1. 1. Incident Issue: Provide longer explanation of the incident
      2. Labels
   2. Response
      1. Incident Responder: Who responded to the incident and filled out this section
      2. Date/Time of Response (first contact)
      3. Responder Assessment
   3. Summary
      1. Executive Summary: Provides a high-level overview of the Incident
   4. Corrective Actions 
      1. Corrective Actions Required
      2. Corrective Actions Due Date
      3. Corrective Actions Taken
      4. All Corrective Actions Completion Date
      5. Completed Corrective Actions Verified By
   5. Preventative Actions: May be used if there is an underlying issue and the team wants to close the incident, but keep on record that they are still working to put in place recurrence prevention tactics
      1. Preventative Actions Required
      2. Preventative Actions Due Date
      3. Preventative Actions Taken
      4. All Preventative Actions Completion Date
   6. Report Attachments: These will appear in the PDF report if they are jpeg or other image file
   7. Internal Information: This information will not be included in system generated reports 
      1. Internal Notes
      2. Impact Type 
      3. Length of Impact (days)
      4. Risk Rating
      5. Cost Implication
      6. Report to Regulatory Agency 
      7. Attachments 
      8. Links
   8. Assign
      1. Responsible Person: The person currently responsible for tracking, managing, and ensuring resolution of the incident 
      2. Send Email Notifications