When you are inside an active log, click on the Sub-incidents tab.
When there are no active sub-incidents, you will see a button to create new sub-incidents, as well as two sections for active and closed sub-incidents.
Create a sub-incident
Click on the "+ Create sub-incident" button to add a sub-incident.
You will see a list of the different available sub-incident types. As an Account admin, you can edit the types of sub-incidents that fit your organization via the General settings.
Choose which type of sub-incident you want to create. The severity level of the incident is predefined depending on which sub-incident you select, but you can change to another level if needed. If you chose to create a sub-incident from scratch, you can define the level of severity yourself.
If you want to, you can also change the name or title of the incident, before you click "Create".
Manage and view active sub-incidents
The sub-incident tab gives you a great overview of all active sub-incidents. Each sub-incident has its own section where you can both see the updated status, and also make adjustments to the sub-incident.
Each sub-incident section provides the following information:
(The numbers on the image corresponds with the explanation below)
1. ID number and severity level
The sub-incidents are given a number, starting from 1. The color that outlines the number indicates the severity level that has been set for the sub-incident. The severity level can be changed by choosing "Edit sub-incident".
2. Location of the sub-incident
A red icon on the left side indicates that the location of the sub-incident has not been set. A green icon means that a location is set. The sub-incident will be marked in the map when activating the map view.
4. Teams
The number shows the number of teams that have been assigned to the specific sub-incident. Click on the team icon to view assigned teams, or to add new teams by clicking "+ Add team".
5. Tasks
Shows the number of tasks that are connected to the sub-incident. By clicking on the number, you will see a list of all tasks. You can click the tasks to mark them as completed. If you need to add more tasks, click the "tasks" symbol.
6. Affected persons
If the sub-incidents affect specific persons, injured persons, missing persons, etc., you can add the persons here. You will be asked for the name of the person as well as some "identifying traits", to describe the person or his state. You can also set the status of each affected person. You will need to "check out" all affected persons to be able to close the sub-incident.
7. Actions
Click this icon when you need to edit the sub-incident to change the severity level. This is also where you can close the sub-incident. This will move the sub-incident from the section of the Active sub-incidents to the section for closed sub-incidents.
Change the viewing order of the sub-incidents
The active sub-incidents are sorted by their status/severity level. If you click on "Order by status", you can choose other ways of ordering the sub-incidents.
Adding content to the sub-incidents feed
The active sub-incidents are also listed on the left side of the log. By clicking any of these sub-incidents, the log will show the log for that specific sub-incident.
If you need to communicate or log something to the sub-incident, you will first have to select the preferred sub-incident in the bar on the right, and then add the log entry or image. You can easily switch between the different logs or communication feeds.
To switch back to the main log, click on the number-icon on the right side of the log feed. The main log feed will show all updates that are posted in any sub-incident log and the "regular" log-feed.
Close a sub-incident
When a sub-incident has been managed and is ready to close, you can click on the gear icon on the sub-incident in the Sub-Incidents tab.
Choose "Close sub-incident". This will move the sub-incident from Active incidents to Closed incidents. If there are registered any affected persons to the sub-incident, you will be asked to "Check out" all affected persons to be able to close the sub-incident.
After the sub-incident has been closed you can either repoen the sub-incident, or download a sub-incident log for documentation and evaluation of how you managed the sub-incident.
You'll also be able to do this from the archives, if your user has access to the Archive.