Mining and FIFO
Swing rosters and site inductions, checked.
Mustr builds FIFO and swing rosters across your mine sites, checks every worker's inductions and tickets are current before a shift is booked, and blocks the ones that are not. Built and proven on remote sites.
Every roster runs the same compliance check.
You are rostering a swing across a remote site. Mustr checks each worker's site induction, tickets and availability before the shift exists, so a non-compliant booking never reaches the site in the first place.
- Site induction current for that site
- Required tickets and medicals current and verified
- Available for the swing, and not double-booked
- Flights and accommodation recorded against the shift
Build the swing and it holds. If an induction or a medical has lapsed, the booking is blocked before anyone flies out.
Made for remote, swing-based crews.
Swings, days and nights
Day and night shifts and swing patterns sit on the one roster, and the crew picker shows who is already committed to another site that week before you try to book them.
Logistics on the shift
Flights and accommodation are recorded against the shift itself, with the logistics detail in one place instead of a separate spreadsheet chased by phone.
Inductions that get reissued
Publish a new induction version and everyone is asked to acknowledge it again, with each acknowledgement recorded against the version they actually read.
Medicals and tickets that expire mid-swing.
A medical or a ticket can fall due while a worker is rostered weeks out. Mustr shows it up to 60 days ahead with one-click reminders, so it is renewed before it stops them being flown to site.
- 60-day expiry dashboard on the certificate matrix
- One-click reminder emails to the worker
- Verified, pending and expired states on every certificate
- An audit trail of who changed what, and when
A warning still lets the booking through. Mustr blocks it, so nobody non-compliant is ever rostered onto a swing.
What this means in an audit
When a client or an auditor asks you to prove the crew on their site were inducted and ticketed, the answer is the system itself: the requirements each site set, verified with dates, and a record showing non-compliant bookings were never made.
The clash you did not know about.
Availability is only half the picture. Someone locked into another client's site the same week used to look free right up until the save failed. The crew picker now shows them greyed out with the clashing site and dates on the card, so you see the conflict before you try to book it.
Inductions everyone has actually read.
Inductions are versioned. Publishing a new version asks every worker to acknowledge it again, and records each acknowledgement against the version they read, so a reissued site induction is not just an email nobody opened.