Reportable Means Reportable: Fix Your Incident Pathway in 30 Minutes

Reportable Means Reportable: Fix Your Incident Pathway in 30 Minutes

Regulators are sharpening their focus on how mining and quarrying businesses classify, notify and document reportable incidents. For small operators and contractors, the difference between tidy files and fuzzy records can mean stop‑work orders, production loss and reputational damage. Here’s how to translate the current regulatory climate into practical, fast wins.

1) The night‑shift wake‑up call

A vehicle interaction on night shift leads to a medically treated injury. A supervisor makes a quick call, but the written record is thin—no clear classification, no verification of critical controls, and no supporting artefacts. By morning, the inspector asks for the file. Inconsistencies trigger a stop‑work and an expanded investigation.

Cost: 12 hours of downtime, a rattled client, and a paper trail that lingers longer than the injury.

Verbal notifications without documented proof create risk.
Gaps in classification and controls verification amplify scrutiny.
Small teams feel it fastest: lost shifts, missed targets, overtime burn.

2) What regulators now expect—and why small operators feel it

Across jurisdictions the bar is clear and rising. In Queensland, Recognised Standards (including RS22 and companion standards) and guidance notes outline risk management and incident recording expectations; WA has firm duties for “reportable incidents” with evidence requirements. Similar obligations exist nationwide through state and territory frameworks (for example, Work Health and Safety Acts/Regulations and mining-specific regulations), and Safety Management Systems (SMS) must document risk arrangements. Reportable incident data often feeds into quarterly WHS reports to the regulator, and operators typically submit annual WHS reports with incident and injury details. In Queensland, events notifiable under Section 16 of the Coal Mine Safety and Health Regulation 2017 should be treated as significant events, with appropriate forms (e.g., Form 5A) completed to a high standard. Initial incident reports should capture essential facts and, where relevant, environmental outcomes/objectives, tenement conditions and measurements.

Bottom line: Clear classification, timely notification and high‑quality documentation are mandatory—not optional.
Evidence matters: Photos, statements, isolation tags/samples, and control verification records substantiate your decisions.

3) Fix the classification gap

Misclassification is the fastest path to regulatory pain. Align your taxonomy with your jurisdiction’s “reportable” definitions so the severity you enter matches the duty you owe.

Action steps

Map your incident types to current regulatory definitions (e.g., WA reportable incident categories; QLD RS22/companion guidance).
Add 5–7 worked examples per category (vehicle interaction, fall from height, energy isolation breach) to reduce ambiguity on night shift.
Embed a decision tree with yes/no prompts to flag “reportable” thresholds.
Require a supervisor sign‑off for classification changes within 24 hours.

4) Get notifications right—every minute counts

Notification delays turn manageable events into compliance failures. Your escalation path must be crystal clear, 24/7, and verifiable.

Build and test your escalation call tree

Define primary and alternate contacts for each time band (days, nights, weekends) including remote/contractor supervisors.
Use a “one call, many alerts” group that auto‑stamps time of notification and acknowledges receipt.
Require written confirmation within 15 minutes (SMS or app) to pair with any verbal call.
Include regulator notification prompts for “reportable” triggers.

Pro tip:

Run a five‑minute after‑hours drill monthly. If the roster changes, the tree updates the same day.

5) Nail the evidence pack and control verification

Verbal isn’t evidence. Your incident form should force the creation of a defensible file—every time.

Pre‑load your incident form with mandatory fields

Time/date of verbal and written notifications with names and roles.
Classification and rationale referencing your matrix.
Critical control verification checklist (isolation, segregation, traffic management, permits).
Reference to the 5‑point personal risk assessment used, if applicable.
Attachments checklist: scene photos, worker/observer statements, isolation samples/tags, training or permit extracts.
Environmental outcomes/objectives and any tenement conditions (where relevant to your site and jurisdiction).

Store everything in a single source of truth with version control. As one superintendent put it: document your business or get out.

6) Make it stick in your Safety Management System (SMS)

Templates don’t change culture—systems do. Your SMS should show how risk is managed, who does what, and how changes are controlled.

From paper to practice

Embed the incident pathway in your SMS: roles, RACI, timeframes, and definitions.
Lock approved templates (e.g., Form 5A in QLD) and archive superseded versions.
Train remote and night‑shift crews with short scenario drills and laminated prompts.
Set change‑management triggers: any regulator update or standard change = immediate matrix review.
Maintain an audit trail: who classified, who verified controls, and when.

Result: a pathway that is designed, tested, and auditable—ready for an inspector by 8am.

7) Strategy: compliance is a production strategy

Turn reporting into uptime

Measure leading indicators: time‑to‑notify, classification accuracy, evidence completeness rate.
Feed data into your quarterly WHS packs (include all reportable incidents) and keep annual reports regulator‑ready.
Standardise across sites and contractors so remote workers follow the same instructions and controls.
Tie performance to bonuses: zero late notifications; 100% evidence packs complete at closeout.

Good files protect production. A clean record today is fewer directives tomorrow.

8) This week’s 30‑minute audit (free checklist)

Classification: Compare your matrix with your jurisdiction’s “reportable” definitions; add examples and a decision tree.
Notifications: Call your escalation tree now; verify timestamps and alternates work after hours.
Forms: Pre‑load mandatory fields (notification time, control verification, 5‑point PRA reference) and an attachments checklist.
Evidence: Confirm photos, statements, and isolation artefacts are easy to capture and store in one place.
SMS: Document the pathway, lock templates, set change triggers, and schedule drills.
Reporting: Ensure reportable incident data rolls into your quarterly submissions and your annual WHS report.

If any of this raises questions about document control, change management or compliance alignment, get your leadership team around the table this week and make the pathway visible on one page.