Incident Register¶

The Mythradon Incident Register is a tool that allows you to track and monitor incidents that have an impact on your organisation. Incidents can include workplaces illnesses, injuries, near misses and cyberattacks. Incidents can be seen as a risk that is occurring or has happened. The Mythradon Incident Register allows you to record how your organisation manages them as well as log the lessons you learnt from these events.

To manage Incidents, select the Incidents tab from the main menu.

Incident List - Light Incident List - Dark

Search for an Incident¶

From the Incident List you can quickly search for the incident that you are looking for using the search box. This will allow you to filter the list of Incidents by the unique incident number or title.

The Search box supports partial name matching and pre-built filters as shown above.

For additional information on searching in Mythradon please refer to Mythradon Search.

Recording an Incident¶

From the Incident List view, click the Create Incident button.

Create New Incident - Light Create New Incident - Dark

Mandatory fields will be identified with an asterisk. i.e.) The Title field.

Click the Save button to save the new Incident record.

Incident Fields

The following are the default fields of an Incident record.

Field	Description
OVERVIEW
Incident Number	System generated unique incident number.
Title	Summary description of the incident.
Type	The Type of incident. Possible values are: Near Miss Injury Exposure Sential Security Property Damage Harassment Bullying IT Outage Cyber Attack .
Severity	The Severity rating of the incident. Possible values are: Minor Moderate Major Critical .
Status	The Status is a read-only field that represents the current status of the incident. Possible values are: Open Closed This field is set to 'Open' by default when a new incident is created. It is automatically set to 'Closed' when setting the 'Close Incident flag' on a related Incident Review record. All changes to the incident status are logged in the related Stream records.
Status Date Time	The date that the Status of the incident was last changed. By default this field is not displayed. This can be displayed using the Layout Manager.
Last Review Date	The date that the last Incident Review was performed on the incident.
Next Review Date	The date that the next Incident Review is due to be actioned. This is also used for triggering notifications.
Incident Owner	The Incident Owner is a User in the system that has been assigned by the business to take control of ensuring the appropriate actions are performed in relation this incident.
Reported By	The User or Contact in the system that reported the incident.
Location of Incident	Description of where the incident occurred.
Incident Date and Time	The data and time of when the incident occurred.
Is the Incident a Notifiable Occurrence	A checkbox used to flag if the incident needs to be reported to the appropriate authority.
PARTIES INVOLVED
Employees Involved	List of Employees (Users) that were involved in the incident.
Contacts Involved	List of Contacts that were involved in the incident.
DETAILS
Description	Detailed description of the incident.
Details of Any Equipment Damage	Detailed description of any equipment damaged in relation to the incident.
Treatment Details	Details of any required treatment to prevent a similar incident recurring.
Financial Impact	Amount of any financial impact in relation to the incident.
Financial Impact Details	Detailed description of any financial impact in relation the incident.
Lessons Learnt	Details of any lessons learnt in relation to the incident. This field is added/editing using the `Lessons Learnt` button.

Reviewing an Incident¶

Reviewing an incident allows you to document its current status and ensure it remains accurate and up to date. Regular reviews help identify incidents that are no longer active and can be closed accordingly.

To log a review:¶

Navigate to the Incident you want to review.
Click Log Review to open the review entry form.
Complete the following fields:
Summary (required): Provide a brief description of the review.
Close (optional): Select this option if the incident should be closed.
Next Review Date (required): Specify the date for the next scheduled review.
Notes (optional): Add any additional context or observations.
Click Save to submit the review.

Note

Once saved, a review entry becomes read-only and cannot be edited.

Incident Log Review – Light Incident Log Review – Dark

You can view all previous reviews in the Incident Reviews related list, located within the Incident Detail View.