Field notes › Industries

Rostering guards across sites without a lapsed licence slipping through

In most labour hire, an expired ticket is a compliance problem. In security it is closer to the heart of the job, because the licence is what allows the guard to do the work at all. A guard standing on a client's site with a lapsed licence is not a paperwork gap the client can overlook until next week. It can put the guard, your firm and possibly the client in front of the regulator.

The difficulty is that security rosters change more often and at shorter notice than most, and that pace is exactly when licence checks get skipped.

Licences are issued by the state, and so are the rules

Security licensing in Australia runs state by state. Each state and territory has its own licensing body and its own licence classes, and they do not all draw the line between activities in the same place. A guard licensed for one kind of work may not be licensed for another, and a licence from one state does not automatically let someone work in the next. If you place guards across a border, check with the licensing body in that state before you roster anyone, and don't rely on what a guard says their licence covers.

So the licence is more than a tick on a worker's file. You want the licence number, what it covers, the state that issued it and the expiry date, and you want it checked against the regulator's public register where one exists, rather than trusting a photo of a card.

Static, patrol and event work need different crews

Overnight static guarding on a construction site is a different job from mobile patrols across several premises, and crowd control at a weekend event differs again. The licence activities can differ, and clients layer their own requirements over the top. First aid is the most common addition. Plenty of clients want every guard to hold a current first aid or CPR certificate, some sites have their own induction, and venues where young people attend may want a working with children check.

Bulk importworkers.csvWorkforce loaded✓Profiles created✓Logins invited by email✓Certificates recordedDownload the template, fill one row per person, upload.Emails in the sheet create logins and send invites in the same step.12
A workforce loads in by CSV, with logins invited in the same step.

That means "licensed guard" is not a role you can safely roster against. The role has to say what the job requires, and the requirement has to sit where the booking is made. In Mustr, requirements can be set per client site, per role and per individual shift, so an event shift can ask for more than the same client's static post without setting the client up twice. Roles are defined by the competencies they need, and a worker automatically earns the highest role whose competencies they hold.

Short-notice cover is where checks get skipped

A guard calls in sick at five in the afternoon for a six o'clock start. The site can't be left empty, and whoever is on the phone is working down a list of names they know will answer. Nobody opens the licence register in that moment. The first person who says yes gets the shift.

Build your process around that evening. Know ahead of time who is licensed and current for each type of post, so the list you ring from is already a qualified list. Then make the check happen whether anyone remembers it or not. Mustr checks every booking on the server at the moment a worker is assigned: required competencies for the client, role and shift must be current and verified, the site induction must be current, the worker can't be double-booked, and they can't have marked themselves unavailable. A failed check blocks the booking with the reason shown, so an expired licence can't be clicked past in a hurry. If you post the shift as open instead, the guards who apply are listed on it and can be assigned in one tap, and the same check still runs.

Chase renewals before they turn into gaps

A security licence, a first aid certificate and a CPR certificate rarely renew on the same date, so a guard's file doesn't lapse all at once. It lapses one piece at a time, which is why each one needs its own expiry date rather than a single "compliant" flag. Start chasing well before the date, because a renewal can take time to process and the guard can't work the gap.

Mustr shows certificates expiring up to 60 days out on the dashboard with one-click reminder emails, and admins set how many days before expiry the chasing starts. Guards can photograph a renewed licence or certificate on their phone and upload it, and it sits in a list for the office to verify before it counts.

When the client or the regulator asks for proof

Clients with real security exposure will ask you to show that everyone on their site is licensed, and a regulator following up an incident will want more than your word. The harder question tends to come later: was this guard licensed on the night, and how did you know? A record that the licence was verified before the booking was made is what answers it. Mustr keeps an audit trail of who changed what and when, which matters most when the question turns up months after the shift.

There is more on how this works for security firms on the security rostering page, and you can try it with sample data in the meantime.

Bring one roster to the demo. We'll show you Mustr running it.

Book a 20-minute demo