Summary
Security rostering carries a constraint no other industry shares: an unlicensed guard on a shift is not a payroll error, it is an offence. Security licensing is state-based, licences expire, and in most jurisdictions both the individual and the employer carry obligations. A guard whose licence lapsed on Tuesday and who worked Wednesday exposes the business, the client and the guard.
Add shifts that cross midnight, 12-hour rosters, permanent night work and long periods alone on site, and you have an industry where the roster is a compliance instrument rather than a scheduling convenience.
This guide covers the Security Services Industry Award 2020 provisions that shape the roster, the midnight problem that quietly corrupts payroll, licence and fatigue management, and the lone worker duty.
The award provisions that shape a security roster
Read the current award, but these are the features that drive the cost model:
- Permanent night work. The award distinguishes ordinary shift work from permanent night work and loads them differently. Someone rostered exclusively to nights is not simply on the night penalty for each shift.
- Twelve-hour shifts, which the award permits under conditions — agreement, breaks, and limits on consecutive shifts. Twelve-hour rostering is normal here and it is not unconditional.
- Broken shifts, common where a site needs cover at opening and closing but not between.
- Minimum engagement, which makes short call-outs and relief shifts more expensive than their duration suggests.
- Allowances for specific duties — dog handling, cash-in-transit, first aid, and others depending on the work.
The midnight problem
This is the industry's most common silent payroll error, and it is worth being precise about.
A shift starting 10pm Saturday and finishing 6am Sunday spans two days, two dates, and — critically — two different penalty regimes. Saturday rates apply to the first two hours; Sunday rates to the remaining six. If the shift is recorded against a single date and paid at one rate, it is wrong in one direction or the other, every single weekend.
It compounds at public holidays. A shift running into a public holiday attracts the public holiday rate from midnight, not for the whole shift, and several jurisdictions declare part-day public holidays from early evening — so a Christmas Eve shift can carry three rates within one span. Our public holidays guide covers how those boundaries work.
The requirement is simple to state and awkward to satisfy with most systems: you need actual start and finish timestamps, not a shift assigned to a date, and the payroll calculation has to be able to split a single span across rate boundaries. A system that models a shift as "Saturday night" rather than as a start instant and an end instant cannot get this right, however carefully payroll is run.
Licences: the control that has to be on the roster
Every state and territory licenses security work, with different classes for different activities — unarmed guarding, crowd control, monitoring, cash-in-transit, armed work. Licences expire, classes are specific, and working outside a class is as much a breach as working without a licence.
The failure mode is entirely predictable: a licence expires quietly, the guard keeps appearing on the roster because nothing connects the two, and nobody discovers it until an incident or an audit. The control that works is equally simple — hold the expiry date against the person and check it before they are rostered, not annually.
Keep a copy of the licence, record its class and expiry, and treat an approaching expiry as a rostering blocker rather than an administrative reminder. If you operate across borders, hold the licence position for each jurisdiction separately, because they do not recognise each other automatically.
Fatigue is a legal duty, not a scheduling preference
Twelve-hour night shifts, consecutive nights and short turnarounds are standard in security, and fatigue is a recognised hazard under work health and safety law. The employer's duty is to manage the risk so far as is reasonably practicable — which means the roster itself is the primary control.
The things a regulator would look at are all roster properties: consecutive shifts worked, hours between the end of one shift and the start of the next, total hours in a rolling period, and how often someone is switching between day and night patterns. None of these are visible if you look at one week at a time, which is how most rosters are built.
Two practical measures. Set a minimum break between shifts and enforce it when rostering rather than reviewing it afterwards. And look at actual worked hours, not rostered hours — a guard covering a no-show at the end of their own 12-hour shift is the exact scenario fatigue rules exist to prevent, and it never appears on the published roster.
The lone worker duty
Most security work is solitary. Working alone is itself a hazard requiring specific controls under work health and safety law: a means of raising an alarm, a way of confirming the worker is safe, and a procedure for when contact is lost.
Clock-in and clock-out records serve a purpose here beyond payroll. A guard who has not clocked in for a shift that started twenty minutes ago is a welfare question before it is an attendance question — and on a lone night shift that distinction matters. Location-stamped clock events also establish where someone was at a given time, which is exactly what an incident investigation needs.
NestedClock records clock events with GPS location and can flag a late start, so an unstarted shift surfaces while it is still actionable. Our guide to late start alerts covers the mechanics.
Client billing and the reconciliation nobody does
Security is usually billed by rostered hours and paid by worked hours, and the two diverge constantly: a relief guard covers a late arrival, a patrol runs over, a shift is extended at the client's request without a purchase order.
Reconciling rostered against actual per site, per period, does two things. It finds unbilled work, which is money. And it finds hours worked that nobody authorised, which is a fatigue and licensing exposure sitting inside the same data.
A short checklist
- Record start and finish timestamps, never a shift-per-date, so midnight splits are computable.
- Confirm your payroll splits a span across day, weekend and public holiday boundaries.
- Hold licence class and expiry per person per jurisdiction, and block rostering on expiry.
- Set and enforce minimum turnaround between shifts, measured on actual hours.
- Review consecutive nights and rolling hours, not single weeks.
- Use clock-in as a welfare signal for lone workers.
- Reconcile rostered against worked hours per site every billing period.
Where to check the detail
The Security Services Industry Award 2020 is on the Fair Work Commission website. Security licensing is administered by the police or a fair trading regulator in each state and territory, and the classes and conditions differ. Fatigue and lone worker duties sit under your state or territory work health and safety legislation and its codes of practice.
This article is general information, not legal advice.