How the compliance blocking works
Everything else in Mustr exists to make this one moment reliable: the moment someone books a worker onto a shift. Here's exactly what happens in that moment.
The four checks
- Competencies. The client site carries required competencies, the role can carry more, and the shift itself can add extras. The worker must hold all of them, current and verified.
- Induction. If the site requires an induction, the worker's must be current.
- Double-booking. The worker can't already be on another shift that clashes.
- Availability. If the worker has marked themselves unavailable, the booking doesn't proceed.
Where the check runs
On the server, not in the browser. That's a deliberate design decision: it means the check can't be clicked past, bypassed by an old open tab, or skipped by someone in a hurry. Whoever does the rostering, the same rules apply.
What a block looks like
The assignment simply doesn't go through, and the screen tells you why: which competency is missing or expired, or where the clash is. From there the fix paths are all short. Choose someone else, update the certificate if it's genuinely current and just wasn't recorded, or sort the availability question with the worker directly.
Warnings versus blocks
Mustr uses both, deliberately. A cert that's expiring soon but still current gets a warning: the booking proceeds, and the expiry dashboard chases the renewal with time to spare. A cert that has already expired is a block: no new bookings on shifts that require it until it's renewed. Warnings are for things you can still fix in time. Blocks are for things that would put a non-compliant worker on site.
That difference is the reason Mustr exists. Software that only warns still lets the shift go ahead, and the gap gets discovered at the gate or in an audit. The compliance page covers what this means for your client relationships, or book a demo and we'll show you a booking getting blocked live.