Release notes

Available from 12 August 2025

 

Improvements

 

Introducing New Regulator Quarterly Summary Report

We are excited to introduce key enhancements to the Regulator Quarterly Summary Report to ensure alignment with Western Australia’s Work Health and Safety (Mines) Regulations 2022 and improve reporting accuracy and transparency for our mining customers.

These updates are specifically designed to support submission to the Local Government, Industry Regulation and Safety (LGIRS) (formerly Department of Mines, Industry Regulation and Safety (DMIRS)) via the Safety Regulation System (SRS).

To accommodate additional information in the report, we updated the MPR Number / Company Level Mapping page to provide the data.

We also added a flag to the Event Details to indicate if the event type is an incident, determining if the incident is notifiable to DMIRS and hence included in the report.

How do I enable the report?
By default, this report is disabled. To enable it, go to the InControl system settings page and set “Is Regulator Quarterly Status Report Enabled” to True by ticking the checkbox.

Note: Changing this system setting requires a service restart (Common service), followed by an app pool recycle, to apply the updated value.

By default, access to the report is granted only to the default security roles: InControl Report Reader, InControl Administrator, and InControl System Administrator. Users with other roles must be granted access manually via the Security Roles page.

When the report is enabled and the user role has access to it, the report will be visibile under Statistics.

What Does the Report Contain?

The Quarterly Summary report includes multiple sections that capture various aspects of safety and operations at a mine site for the quarter:

Reporting Details

• Defines the scope of the report (quarter and company).
• Includes:
  • Reporting Period (e.g., Jan – Mar 2025).
  • Mine Type (e.g., Mine, Exploration).
  • Company Name (e.g., Rio Tinto), Site Group, Commodity Processed, Primary Contact details, Secondary Contact details and Exploration details. These data are coming from the MPR table.
• Used to identify which site and time period the report applies to.

Employment Status

• Captures workforce data for employees and contractors for both Surface and Underground workers based on the InControl Exposure page.
  • Shows the average number of company and contractor workers for all contracting companies together. The average number is calculated from the total number of employees on site divided by the number of days throughout the quarter.
    • Note: The average is rounded to the nearest whole number.
  • Shows the total hours worked of the company and contractor workers for all contracting companies together.
• Supports exposure reporting as required by LGIRS

Details of field definition:

• Employment Status: Calculate data from InControl Exposure page where the workgroup’s minetype = report parameter minetype and month-year is within the report period.

• Surface Average Company Employees: Total Staff employees on site (where the workgroup’s location = Surface) / # days throughout the quarter

• Surface Total Hours Company Employees: Total Staff worked hours (where the workgroup’s location = Surface)

• Surface Average Contractor Employees: Total Contractor employees on site (with the workgroup’s location = Surface) / # days throughout the quarter

• Surface Total Hours Contractor Employees: Total Contractor worked hours (where the workgroup’s location = Surface)

• Underground Average Company Employees: Total Staff employees on site (where the workgroup’s location = Underground) / # days throughout the quarter

• Underground Total Hours Company Employees: Total Staff worked hours (where the workgroup’s location = Underground)

• Underground Average Contractor Employees: Total Contractor employees on site (with the workgroup’s location = Underground) / # days throughout the quarter

• Underground Total Hours Contractor Employees: Total Contractor worked hours (where the workgroup’s location = Underground)

Incident-Injury-Illness

• Summarises safety incidents and injury data where the event is flagged as notifiable to LGIRS and not cancelled, and the event’s workgroup mine type is under (a member of) the report parameter mine type.
• Split into:
  • Incident Summary:
    • Number of Incidents
  • Injury/Illness Summary:
    • Number of Lost Time Injuries (LTI).
    • Days lost due to LTIs.
    • Number of Restricted Work / Alternative Injuries (RWI).
    • Days on restricted / alternative duties.
    • Number of Medical Treatment Injuries.
    • Number of Deaths.

Details of field definition

• Incident Summary: The number of records from the event report where the event type has flag Is Incident = true and the event date is within the report period.

• No. of Lost Time Injury: The number of records from the event injury tab where its injury type classification code = ‘L’ (Full Shift Lost) or ‘D’ (Disabled) and the event date is within the report period.

• No. of days lost from work: Sum the value of Days from event injury lost time tab where its injury type classification code = ‘L’ or ‘D’ and work status code = ‘L’ and event is not cancelled and event is notifiable to DMIRS and lost time injury date is within the report period, which includes any carry over injuries.

• No. of Restricted / Alternative Injury: The number of records from the event injury tab where its injury type classification code = ‘R’ (Restricted Duties) and event date is within the report period.

• No. of days restricted duty: Sum the value of Days from the event injury lost time tab where its injury type classification code = ‘R’ and work status code = ‘A’ and lost time injury date is within the report period, which includes any carry over injuries.

• No. of treatment injury: The number of records from the event injury tab where its injury type classification code = ‘M’ (Medical Treatment Required) and event date is within the report period.

• No. of death: The number of records from the event injury tab where its injury type classification code = ‘F’ (Fatality) and the event date is within the report period.

Work Status Timeline

• Detailed worker-level status log, based on event injury lost time tab where its injury type classification code = ‘L’ or ‘D’ or ‘R’ and effective date is within the report period, and the event’s workgroup mine type equals report parameter mine type
• Includes:
  • Worker name (or placeholder).
  • Injury Date and Ceased Work Date.
  • Work Status: L (Lost Time) or A (Alternate Duties).
  • Effective Date of each status.
  • Days Lost (for Lost time / disabled) and Alternate Duty Days (for Restricted duty).
• Drives automated calculations for LTI and RWI figures.

Reportable Incident Listing

• Provides a line-by-line list of reportable incidents.
• Includes:
  • Date of incident.
  • Reference number (incident ID).
  • Event Type and Subtype.
  • Injury Type (e.g., LTI).
  • Workgroup / Description (area and task).
  • Actions Logged (Total/Open).
  • Actual and Potential Severity.
  • Incident Status (e.g., Submitted).
  • Who closed out the event
  • Helps track incident compliance and follow-up actions.

Example report

Typically, this report is compiled and submitted by:

• HSE Managers
• Safety Officers
• Compliance Managers
• System Admins

Change “+” button location in Personal Profile section

In version 5.18.1, we have made a highly requested user experience enhancement by repositioning the ‘Add’ (+) button to the top of the table across all the applicable sections under Personal Profile- improving user experience.

Previously, users managing large lists (like 50+ CCPs or procedures) had to scroll to the bottom repeatedly to add new entries, with the page reverting to the top after each action. The ‘Add’ button is now clearly positioned at the top of the following tabs: Roles, Workgroups, Competencies, Compliances, Procedures, Training Events, and Attachments.

For example, within the Personal Profile > Workgroup and Personal Profile > Procedure sections (see screenshots), the ‘+’ button is now easily accessible at the top-left of the table.

Made the “Actionee Comments:” cell mandatory in Action Editor after “Responsibility” has been assigned and saved.

We have introduced an enhancement to the Action Editor in InControl. Once the Responsibility field is assigned and saved, users are now required to complete the Actionee Comments field before marking the action as completed. This change ensures that each action is closed with clear input from the responsible person, promoting stronger accountability, better communication, and improved audit trails. A clear validation message will appear if comments are missing, and the field will be highlighted in yellow, consistent with other mandatory fields.

Fixes

Overdue Action Notifications suppressed for cancelled events

Resolved an issue where escalation emails were still being sent to Actionees and Supervisors for overdue actions, even after the associated event had been cancelled. The system now correctly checks the event status before sending notifications, ensuring cancelled events do not trigger further action reminders.

Checklist comments no longer trigger system error when containing markup-like text

Entering certain text into checklist comments, such as HTML tags or angle brackets, was incorrectly flagged as unsafe and caused a 500 error on form submission. The system now safely handles and escapes these values, preventing disruptions for users entering descriptive content.

Risk Review report performance improved

Updated the underlying logic in the Risk Review report to improve efficiency and prevent timeouts. By replacing subqueries with streamlined joins, the report now executes more reliably across larger data sets, reducing the likelihood of errors and long load times.

Validation added for Event Type Categories

The system now prevents users from saving Event Type Categories without a name or description. Allowing blank entries previously led to errors in areas like reporting, where filters based on these categories could fail and show a 500 error. This change ensures categories are complete before they can be saved.

Stray character removed from InControl home page

Removed an unintended “>” character that appeared at the bottom of the InControl home page. This visual glitch had no functional impact but has now been cleaned up for consistency.

Notifications now correctly sent to Submitter when expected

Corrected a logic error that prevented notifications from being sent to the Submitter when their role was set as the responsible party and “Notify All Role Members” was enabled. An earlier update introduced a change that unintentionally impacted customers upgrading from version 5.12. The system now respects both the Responsible Role and notification settings, ensuring Submitters receive the appropriate notifications as intended.

Checklist validation errors now remain visible

Improved the behaviour of validation messages on the Checklist tab when progressing an event. Previously, error messages would disappear too quickly due to a page refresh, making it difficult for users to read and respond. These messages now persist as expected, providing a clearer and more user-friendly experience.

Users can now edit Event Custom Fields in Admin area

Resolved an issue where users were unable to edit records on the Event Custom Fields page. Attempts to update existing fields resulted in an error, preventing changes from being saved. A script update has been applied to restore full editing functionality across affected environments.

Duplicate notifications prevented when processing high volumes of scheduled reports

An issue was identified where restarting the scheduler in environments with a large number of daily scheduled reports (typically 40 or more) could result in duplicate notifications being sent. This has now been corrected. The system reliably handles bulk report processing without generating duplicates, even under high load conditions.