Australian mining supervisor and two workers in orange high-vis and hard hats logging a near-miss report on a tablet in front of a haul truck
    Safety

    How to Report Near Misses on Mine Sites

    July 2026 7 min read

    Quick Answer

    To report near misses on a mine site, Australian contractors should:

    • Log every event with potential for harm — not just injuries
    • Report on a phone or tablet within the same shift
    • Classify by potential worst-case outcome, not what actually happened
    • Notify the state regulator for high potential incidents (HPIs)
    • Investigate to root cause, assign corrective actions with owners
    • Feed outcomes back — close the loop to keep reports flowing

    What counts as a near miss?

    A near miss is any unplanned event on a mine site that could have caused injury, illness, environmental damage or asset damage — but didn't. The outcome this time doesn't matter. What matters is the outcome next time, if the same thing happens under slightly different conditions.

    Every fatality in Australian mining has been preceded by dozens of near misses that were either not reported, not investigated, or not actioned. The near miss is the cheapest data point in your safety system — a warning without the bill.

    Common near misses on mine sites

    Haul truck rolling past a stop bar or intersection
    Light vehicle in a heavy vehicle blind spot
    Tyre or rim releasing energy during service
    Worker on foot inside an exclusion zone
    Isolation missed during maintenance (electrical or stored energy)
    Load slip during lifting operations
    Slope failure or highwall material fall — no one struck
    Uncontrolled release of hydrocarbons or reagents
    Sleeping or fatigued operator observed at controls
    Fire ignition source — extinguished before spread

    What to capture in a near-miss report

    The report has to be short enough to actually get done in the field, and complete enough to be useful in an investigation. This is the minimum viable set.

    FieldWhy it matters
    Date, time and shiftFatigue and shift-change trends are real
    Location (site + GPS + landmark)Repeat hotspots become obvious
    Who was involvedReporter, witnesses, crew, contractor
    Equipment / asset involvedLinks back to the plant register
    Description of what happenedPlain English, no jargon or blame
    Actual outcomeWhat happened this time (usually nothing)
    Potential outcome (worst case)Drives the HPI classification
    Photos and sketchesOne photo saves a paragraph
    Immediate action takenBarricades, isolations, comms
    Contributing factorsEnvironment, equipment, procedure, people

    Near miss vs high potential incident (HPI)

    Near miss

    • Any event with potential for harm
    • Logged in the internal register
    • Investigated proportional to potential
    • Trended monthly to find hotspots

    High potential incident (HPI)

    • Realistic worst-case: serious injury or fatality
    • Reportable to the state regulator (RSHQ, NSW RR, DMIRS)
    • Full ICAM investigation with client involvement
    • Board-level visibility for Tier-1 contractors

    Reporting definitions and timeframes vary by state — check your jurisdiction's current guidance. If in doubt, notify.

    A 6-step framework for near-miss reporting

    1. 1

      See it — report it, same shift

      Anyone on site can log a near miss on a phone or tablet. The 60-second version — what, where, photo — is enough. Detail can be added later. Never wait for end of shift.

    2. 2

      Triage against potential outcome

      The supervisor classifies the potential worst-case: low, medium, high (HPI). HPIs trigger regulator notification and a formal ICAM. Everything else still enters the register.

    3. 3

      Contain the immediate hazard

      Barricade, isolate, tag-out, remove the plant from service. Nothing else matters until the same thing can't happen to the next shift.

    4. 4

      Investigate to root cause

      For HPIs run an ICAM or 5-Whys. For lower-level near misses, a short investigation and a documented cause code is enough. Blame is not a cause code.

    5. 5

      Corrective actions with owners and due dates

      Every action has one owner, one due date and a verification step. 'Toolbox talk' by itself is not a corrective action — it's a communication, not a control.

    6. 6

      Close the loop

      Feed the outcome back to the reporter, the crew and the client. Publish the monthly near-miss Pareto — top 3 causes, top 3 locations, what's being done. This is what keeps reports coming in.

    Corrective actions: use the hierarchy of controls

    A corrective action lower on this list is weaker than one higher up. If your near-miss closeouts are mostly "toolbox talk" or "reminder to crew," your program is not actually reducing risk — it's just documenting it.

    Control levelExample
    EliminationRemove the reversing task — one-way haul road
    SubstitutionSwap the manual tool for a remote-operated one
    Engineering controlsProximity detection, positive isolation, stop bars
    Administrative controlsProcedure changes, training, permits
    PPELast line of defence — high-vis, gloves, glasses

    Building a culture where reports actually come in

    The report rate is a leading indicator — a low number is a bad number.

    • Make reporting take under 60 seconds on a phone
    • Never punish the reporter — blame kills the pipeline
    • Supervisors log their own near misses first
    • Share monthly outcomes: 'here's what changed because you spoke up'
    • Recognise the reporter of the month at pre-start
    • Track and publish the number of open vs closed actions by owner

    Common mistakes to avoid

    These are the patterns regulators and Tier-1 auditors flag every time

    • Classifying by actual outcome ('no one hurt, low priority') instead of potential
    • Investigating only what happened, not why the controls failed
    • Corrective actions with no named owner or no due date
    • 'Retrain the operator' as the closeout for a systemic issue
    • No trend analysis — every near miss treated as a one-off
    • Report register in a spreadsheet that nobody outside HSE ever opens

    How SprintSuite manages near-miss reporting

    SprintSuite lets any worker log a near miss from the field in under a minute — with photos, GPS and the asset picked from the plant register — and routes it to the right supervisor for triage, investigation and closeout.

    Frequently asked questions

    Keep reading

    Turn near-miss reporting into a live pipeline

    Stop losing near misses to the ute floor. SprintSuite captures them at source, triages by potential, and gives you a monthly Pareto that tells you exactly where to spend your safety dollar next.

    Explore Health & Safety