Quick Answer
Build one induction matrix per worker, capture the certificate as evidence, set expiry alerts at 60/30/7 days, gate rostering on induction status, run a pre-mob compliance check 24 hours before travel, and report induction % on the client scorecard. Spreadsheets scale to about 30 workers — beyond that, use a purpose-built training matrix so nobody gets stood down at the gate.
Why site inductions are the #1 compliance failure point
Every Tier-1 mining client — BMA, BHP, Anglo, Rio, Glencore, Fortescue — controls access at the gate. A worker without a current site induction doesn't get past the boom, no matter how much you're paying them, no matter how far they've flown, no matter how urgent the shutdown is.
For contractors, that turns a paperwork miss into a very expensive operational miss: lost shift, wasted flight, wasted accommodation, a red mark on the client scorecard, and a phone call from procurement. Managing inductions well isn't admin — it's revenue protection.
The six inductions every mining contractor has to track
General site induction
Site rules, emergency procedures, exclusion zones, traffic management.
Area / department induction
Pit, workshop, wash-down bay, magazine, tailings — each with its own hazards.
Role or task induction
Isolation, working at heights, confined space, hot work — task-specific rules.
Client-specific HSE induction
BMA, Anglo, BHP, Rio, Glencore — each Tier-1 client has its own required course.
Contractor / SMP induction
Your own company induction covering EBA, timesheets, HR and code of conduct.
Visitor / short-term access
For OEMs, auditors, delivery drivers — usually escorted, time-boxed.
A 6-step framework that actually works
- 1
Build one induction matrix per worker
For every worker, list the inductions they need for every site and every scope they're rostered to. Not the sites they might go to — the sites they're actually contracted for. One row per worker, one column per induction, one cell per expiry date.
- 2
Capture proof, not just a tick
Store the certificate PDF, the completion date, the expiry date and the issuing body against the worker's profile. If a client auditor asks 'show me evidence Joe is inducted for BMA Goonyella', you should be able to open a single record and prove it.
- 3
Set expiry alerts at 60 / 30 / 7 days
Tier-1 site inductions are almost always 12 months. Alert the worker and the supervisor at 60 days (book the refresher), 30 days (confirmed booking) and 7 days (last chance). Never at 0 days — that's a stand-down at the gate.
- 4
Gate rostering on induction status
The scheduler should physically stop a worker being rostered to a site their induction has expired for. Manual eyeballing of spreadsheets is where expiries slip through — automated gating is where they stop.
- 5
Pre-mob check 24 hours before travel
Before any FIFO/DIDO flight or bus, run a pre-mob compliance check: inductions current, medical current, tickets current, PPE issued. Catch it the day before, not at the gate — travel and accommodation costs are already sunk by then.
- 6
Close the loop back to the client scorecard
Report induction compliance as a % on the monthly client scorecard, alongside TRIFR and near-miss stats. Tier-1 procurement teams score you on the number and reward it at the next contract cycle.
Spreadsheet vs standalone matrix vs SprintSuite
A quick capability check as your workforce grows past 30, 100 and 300+ people.
| Capability | Spreadsheet | Standalone matrix | SprintSuite |
|---|---|---|---|
| Single worker profile (inductions, tickets, medicals) | |||
| Certificate PDF storage against the worker | |||
| Automatic expiry alerts to worker + supervisor | |||
| Rostering gated by induction status | |||
| Pre-mob compliance check before travel | |||
| Client-facing induction scorecard pack | |||
| Linked to timesheets, payroll & progress claims |
Five mistakes that lead to stand-downs
Tracking inductions in a spreadsheet no one has open on mob day.
Storing certificates in a shared drive with no expiry logic.
Alerting only the office — not the worker or their supervisor.
Rostering off availability instead of compliance status.
Discovering the expiry at the gate instead of 60 days out.
How SprintSuite handles inductions end-to-end
Inductions don't live in a separate tool in SprintSuite — they live on the worker profile that also drives rostering, timesheets and progress claims. That's how gating actually works: the scheduler can't put an expired worker on a site, and the pre-mob check runs against the same record HR and payroll use.
Training matrix
Every worker, every induction, every ticket — with expiry logic and evidence attached.
Compliance gating
Rostering blocks expired workers automatically; supervisors see the gap before mob day.
Client scorecards
Induction % rolls into the monthly Tier-1 HSE pack alongside TRIFR and near-miss data.
Frequently asked questions
Keep reading
Stop workers being stood down at the gate
See how SprintSuite gates rostering on induction status, runs pre-mob checks and rolls compliance % into your Tier-1 client scorecards.
Compare SprintSuite
