How to add Incident consequences

When an Incident occur, they often have some sort of consequence. If it is a “near-miss” there is might not be actual consequences but potential consequences. When creating a new incident report, the first question asked by the system is if the new incident is considered a “near-miss” or an incident with actual consequences. If “Near-miss” is selected only “potential consequences” are possible to link to the incident report. If the Incident has an actual consequence it can’t be recorded if the incident is recorded as a “near-miss”. The procedure adding a “potential” versus an “actual” consequence is the same.  

1. Open Incident report in question
2. Click the “Consequences” tab.
3. Depending on the selected Incident being recorded as a “near-miss” or an “incident with actual consequences” this tab will appear differently.
   1. If it is a “Near-Miss” only the “Potential consequence” grid will be available.
   2. If it is a “Incident with actual consequences both the “potential consequence” and the “actual consequence” grid will appear.

The “Consequences” tab on an “Incident with actual consequences”, showing both the potential and the actual consequence grids 

1. To add a consequence, click the [New Consequence] button.

1. Select if this is considered a “Potential consequence” or and “actual consequence”
2. Specify what type of consequence this is. The consequence type selected will affect the available options and selections in the consequence form that will appear next. In this example we chose the “Personnel” consequence.
3. Click [OK]

The Personnel consequence form 

Consequence details field group. 

1. The three first fields should already be populated
   1. Consequence category: This field will show if the consequence is an actual or a potential consequence  
   2. Consequence type: This field will reflect what type of consequence this is   

(the choice made in step 4.)   

1. Consequence number: Will be constructed using the full Incident number and then adding a running number at the end using an “\” as a separator. Consequences created at the office will have a running number starting with “1000”, consequence running number recorded onboard will start at “0001”

1. Enter the details that apply:
   1. Consequence Name: Enter a short consequence description
   2. Person in charge: If somebody was in charge when the consequence occurred, select that person’s name from either the Crew list, user list or contact list.
   3. Recurrence probability: Select the considered probability value for this consequence.

This value will be used to calculate the “risk” related to the consequence.

Dates field group. 

It is possible to record several dates and times for the consequence, some serve just as information, and some are used to calculate “Lost time”.

1. Noticed date: The date and time for when the consequence was discovered
2. Reported date: The date and time the incident was reported.
3. Stopped Work: If the consequence caused the affected person to stop work specify the date and time for when this occurred.
4. Recommenced work (estimate): If the person affected by the consequence has not yet started working again, and estimate can be set for when this is expected to happen.
5. Recommenced work (actual): The date and time the person returned to work.
6. Lost time: The difference between “Stopped Work” and “Recommenced work (actual)” is used to calculate the “lost time”. It is displayed int eh following format “1d 10H 45M”

Consequence classification 

1. Category: This field is used to categorise the consequence, the category options available will depend on what consequence type this is. Only options that are designated for “personnel” consequences will appear as available choices. The category codes can also be tagged with a “severity rating”. When the category is selected the “severity” tag will appear in the “severity” field next to it.
2. Remedial Action: What was done as a remedial action, again the codes available in this fields are also linked to the “consequence type” selected. Remedial action codes can be tagged as a “First aid” case or a “Medical treatment” case. This is coding used to as part of the “Lost Time Injury” calculation.
3. Outcome: What was the “result” of the consequence. Outcome codes can be tagged with additional “Lost Time Injury” case tags, such as “Restricted Workday case”, “Lost Workday case”.

Please refer to the Outcome code list description for more details.

1. Severity: This field can not be edited directly, the value shown in this field is the “Severity” tag on the selected consequence Category code. Please refer to the consequence “Category” code list description for more details.  
2. Risk: This field is set based on the selected “Consequence” reoccurrence probability selected and the selected consequence category’s severity tag. It uses the “Risk matrix” to set the value.
3. Case type: This field will be set by either the “Remedial Action” or “Outcome” selected. Any of the “Outcome” case type tags will overrule any “Remedial action” case types. “Remedial action” case types will only remain if the selected “Outcome” code is not tagged with a case type. For more information relating to the “Lost Time Injury” (LTI) and Calculation of the “Lost time injury frequency” (LTIF) please review chapter “How to read and use the Incident KPI module?” The Case types only apples to the “Personnel” consequences.
4. Consequence Description: Enter a textual description of the consequence

1. Depending on the selected “Consequence type” some may have an additional specific tab for additional consequence details. This apples to the following consequence types o Pollution: This consequence type has an extra tab where the following details can be recorded. 
   • Quantity: The amount of pollutant 
   • UOM Code: The Unit of measure for the amount specified above 
   • Pollution type: Select the general type of pollution  
   • Pollution code: Specify the pollution substance o Personnel