Prove It or Pause: Fix Your Safety Evidence This Week
Small mine operators and contractors can’t afford audits that stall over missing proof. Turn a near miss and document confusion into a sharper Safety Management System (SMS) that satisfies inspectors, insurers, and clients—this week.
1) The near miss that exposed your system
A supervisor reached for the “current” SOP and found three versions—two online, one in the crib room. The incident form lacked reportable fields. Close-out actions were buried in emails with no owner. Result: days lost, insurer queries, uneasy client.
Hard truth: “Document your business or get out.” If you can’t prove it, regulators assume it didn’t happen.
Why it matters
- Audits pause or fail without traceable evidence.
- Insurers question cover and reserves.
- Clients doubt your control of high-risk work.
2) What this really is: an emerging compliance and evidence risk
Inspectors are now testing the quality of your SMS and incident evidence. WA’s MSMS Code of Practice and WHS mines regulations expect traceability, version control, and proof of training to the correct procedure.
Situation type
- Emerging regulatory focus on SMS quality and evidence integrity.
- New/clarified compliance expectations for incident reporting and document control.
Business implications
- Notices, fines, or stop-work if notifiable/reportable events are mishandled.
- Contract risk: failure to demonstrate compliance weakens bid positions.
- Financial drag: rework, downtime, and premium pressure from poor evidence.
3) Lesson 1: One procedure, one owner, one location
Set your single source of truth (SSOT)
- Central register: Store current controlled documents in one place with version history (e.g., SOP-012 v3.2, owner, approval date, next review).
- Ownership: Assign an accountable custodian for each high-risk SOP.
- Watermark and withdraw: Watermark controlled PDFs “Current” with version/date; stamp superseded copies “Obsolete” and remove old prints from site.
- Access for remote crews: Provide QR codes on equipment/crib rooms that link to the current SOP; keep an offline pack that syncs when reconnected.
Fast check
If two places say two different things, you don’t have control. Consolidate by end of week.
4) Lesson 2: Align incident reporting to your jurisdiction
Ensure your template captures what regulators require for notifiable and reportable events—and that the escalation path is crystal clear.
Minimum fields to include
- Classification (notifiable/reportable/near miss) and regulatory trigger met.
- Time/date of incident and time/date of regulator notification.
- Location, equipment, persons involved, immediate actions, controls applied.
- Injury/illness details, environmental impacts, photographs, witness statements.
- Responsible person for close-out, target date, verification of effectiveness.
Process clarity
- Embed a “Call-now” step for notifiable events and link to the relevant regulator guidance.
- Preload regulator contact details and after-hours numbers in the template.
5) Lesson 3: Run the 30-minute evidence sweep on five high-risk tasks
Pick your top-five risk tasks (e.g., isolation, confined space, lifting, work at height, mobile plant).
Follow this mini-audit
- Confirm the source: Verify one approved SOP per task in the SSOT with owner and review date.
- Purge duplicates: Remove old crib-room prints; photograph removal and file the evidence.
- Training match: Check that worker records show training on the current version.
- Permit/LOTO evidence: Attach last two permits/checklists to the task record.
- Incident template: Ensure the correct form is at point-of-use and mirrors your jurisdiction’s requirements.
- Register it: Store all artifacts (docs, photos, sign-offs) in a single register with version history.
6) Lesson 4: Prove competence to the right version
Inspectors look for training that maps to the exact procedure version in use at the time of work.
Make it airtight
- Training matrix: Link roles to SOP versions and expiry dates; trigger refreshers on revision.
- Point-of-work acknowledgment: Digital sign-off or scan confirming the version viewed before starting the task.
- Remote/fly-in crews: Send micro-briefs on changes, require confirmation before mobilisation.
- Change control: Every SOP update includes impact assessment, comms plan, and retraining requirements.
7) Strategic insight: Treat your SMS like a product, not paperwork
Products have owners, roadmaps, release notes, and telemetry. Your SMS should too.
Operational dividends
- Continuity: Faster recoveries after incidents with clean evidence trails.
- Commercial: Stronger prequals and client confidence when you can “show, not tell.”
- Insurance: Better positioning at renewal with demonstrable controls and response quality.
Simple telemetry to track
- Percentage of high-risk SOPs with named owner and next review date.
- Median time from incident to regulator notification and to action close-out.
- Training-to-version match rate for high-risk tasks.
8) Outro: Your next 7 days
Day 1–2: Stand up your SSOT and assign owners. Day 3: Replace the incident template and embed escalation. Day 4: Run the 30-minute evidence sweep on five high-risk tasks. Day 5–6: Fix gaps (old prints, missing fields, training mismatches). Day 7: Review outcomes with supervisors; lock in a monthly mini-audit.
If you can’t prove it, you can’t defend it—in audits, investigations, or tenders. Start this week.