Steel processing & distribution

One incident register for twenty-plus service centres

A national steel processing and distribution group running service centres, coil lines and a large owned fleet, with a central SHEQ function accountable for group-wide safety performance.

The problem

Every branch had its own way of recording an incident. Some used the printed group form, some a locally-modified spreadsheet, some a hardcover book at the weighbridge. Classification was inconsistent, so the same event was a first aid case at one branch and a minor injury at another, and group-level trending was meaningless.

Investigations started late because head office only heard about an incident when the monthly pack arrived. Corrective actions were agreed in meetings and closed out verbally. And the branches with the most disciplined paperwork looked like the branches with the most incidents, which quietly discouraged reporting.

What we built

  • Mobile incident capture
  • Injury, property, environmental and near-miss types
  • Severity and escalation matrix
  • Structured investigation workflow
  • Corrective action register
  • Reportable-incident flagging
  • Branch scorecards
  • Group safety reporting

How it runs

A supervisor logs the event on a phone at the scene — photographs, location, people involved, body part, mechanism, immediate action taken. The form applies the group's own classification rules rather than leaving it to judgement, and the resulting severity drives the escalation: a high-potential incident notifies the group SHEQ manager and the regional executive within minutes.

Events meeting the statutory reporting threshold are flagged the moment they are classified, with the reporting clock shown on the record. Investigation is assigned with a due date. Corrective actions carry a named owner and a closure date, and nothing closes without evidence attached. Branch and group dashboards rebuild off the same records.

What changed

  • High-potential incidents reach the group SHEQ manager within minutes of classification, not at month end.
  • One classification standard across every branch, so group-level trending finally means something.
  • Corrective actions carry a named owner, a due date and evidence at closure.
  • Statutory reporting thresholds are flagged automatically as an incident is classified.
  • The monthly SHEQ pack is a report that already exists rather than a document someone assembles.

Book a discovery call

Tell us what your team is trying to solve and we will come back with a straight answer on whether we can help, and what a rollout looks like.

Having trouble? Email us at sales@moxietech.co.za.

By submitting this form you agree to be contacted about your enquiry and accept our Privacy Policy.