Traffic management
Ticketed controllers, on the right work zone.
Mustr matches your traffic controllers to each client's work zones, checks their tickets are current before they are rostered, and blocks anyone who is not cleared. One roster across every job and every crew.
The right ticket for the work zone.
A principal contractor needs a crew on a night shift this week. Mustr shows you which controllers hold the tickets that job needs, who is available, and who is not already on another site, so the roster is right before it goes out.
- Traffic control and traffic management tickets, current and verified
- Available, and not double-booked on another job
- Site or client induction current
- Day and night work zones on the one roster
Roster them and it is done. If a ticket has lapsed, the booking is blocked before the controller is standing on the road, not after.
Built for the way traffic jobs run.
Per client and per job
Each client and each job can require its own tickets. The check picks up a one-off requirement on a single shift the same way it handles the standing ones.
Nights, days and short notice
Work zones run at all hours. Day and night shifts sit on the one roster, and an open shift can go out to qualified, available controllers when a job lands late.
A casual pool that turns over
Controllers come and go between jobs. Set someone inactive and they keep every ticket and record, drop out of the pickers, and cannot be booked until you switch them back on.
The ticket that lapses mid-job.
A controller's ticket can expire in the middle of a run of night shifts. Mustr flags it up to 60 days out on the dashboard, with one-click reminders, so it is renewed before it stops them being rostered.
- 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 shift go ahead. Mustr blocks the booking instead, so an uncleared controller is never scheduled onto a work zone.
What this means when the principal asks
When the principal contractor asks you to prove every controller on their job was ticketed, the answer is the system itself: the tickets each job required, verified with dates, and a record showing non-compliant bookings were never made. No paperwork reconstruction.
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.
Nothing waiting in a portal to be noticed.
When a client raises a request or changes a shift themselves, your team is told straight away by email and in the app. The request lands in a queue that keeps a done-pile of what you have already crewed this week, so a covered shift does not just vanish and an open one does not get missed.