Compliance engine
The roster that says no.
Every shift is checked against the worker's competencies before it's booked. If the check fails, the booking is blocked. Not flagged for someone to catch later. Blocked.
Four checks on every booking.
The moment you assign a worker to a shift, Mustr runs the checks on the server, where nobody can click past them.
- Required competencies for the client and the role, current and verified
- Site induction current for that site
- No double-booking against any other shift
- The worker hasn't marked themselves unavailable
Pass all four and the booking is made. Fail one and it isn't, with the reason spelled out so you can fix the gap or pick someone else.
Requirements that match how sites actually work.
Per client
Each client site carries its own required competencies. Nobody gets rostered there without them, no matter who is doing the rostering.
Per role
A role can require its own tickets on top of the site's. The medic needs different paper to the operator, and Mustr knows the difference.
Per shift
A one-off job needs something extra? Add a requirement to the shift itself and the check picks it up like any other.
Expiries you see coming.
Certs that are about to lapse show on the dashboard up to 60 days out, with one-click reminder emails to the worker. One-off tickets that never expire and renewing certs with expiry dates are both handled, and the whole matrix is visible at a glance.
- 60-day expiry dashboard
- One-click reminder emails
- Verified, pending and expired states on every certificate
- An audit trail of who changed what, and when
Plenty of software will track an expiry and warn you. A warning still lets the shift go ahead. The block is the point. Read how the blocking works, step by step.
What this means in an audit
When a client asks you to prove the crew on their site were compliant, the answer is the system itself: requirements defined, certificates verified with dates, and a record showing non-compliant bookings never got made. No spreadsheet reconstruction, no box of photocopies.
Before the first shift
Compliance starts at onboarding, not at the roster.
A ticket check at booking time only works if the paperwork exists. Mustr runs the front half of that too, and you decide how strict it is.
Your steps, your rules
Personal details, headshot, induction, fit-for-work, competencies and availability are each optional or mandatory, and you can add your own steps: read and acknowledge a document, upload a file, confirm a statement, or complete a linked form.
A gate that can be closed
Turn the gate on and nobody gets into the rest of the app until the mandatory steps are done. Each step can allow a grace period first, so a medical declaration gets a realistic window instead of locking someone out the same morning.
Switch it on without a mutiny
Set the date you're counting from and existing crew get the full grace period from that day, rather than every one of them being locked out the morning the gate goes live.
Fit for work, and still on the books.
Fit-for-work declarations have their own due tracking: one month from a worker's first sign-in to get their signed declaration up, with the due date on the admin onboarding table and anyone overdue flagged. Inductions are versioned, so publishing a new version asks everyone to acknowledge it again and records each acknowledgement against the version they actually read.
Someone who shouldn't be rostered for a while doesn't have to be deleted. Set them inactive and they keep every certificate, shift and note, disappear from the crew pickers, and can't be assigned even by a direct request from a client. Expiry reminders stop chasing them, and their login is suspended until you switch them back on.
The clash you didn't know about.
Availability is only half the picture. Someone locked into another 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 can see the conflict before you try to book it.