Every post covered, provably

Yes. Each client site is its own area with its own posts and coverage requirements. You see the whole operation on one roster, filter by site, and prove to any client exactly who was rostered where and when.

Geofenced GPS clock-in only works inside the radius around each site, and every punch carries a timestamp and location stamp. When a client asks for evidence of coverage, the record is a query — not a reconstruction.

Yes. State security licences, first aid certificates and any site-specific inductions are recorded per guard with expiry dates and automatic reminders — and position approvals keep guards with lapsed licences from being rostered onto posts that require them.

Day, evening and overnight posts sit on one grid, shifts across midnight are handled as single shifts and split correctly for payroll, and coverage gaps are visible before publish. Rotations live in reusable templates so the pattern rebuilds itself.

Filter licensed, available guards and push the open shift to their phones — the first to accept takes the post. Managers get late clock-in alerts within minutes of a missed start, so an unmanned post is discovered by the system, not by the client.

Yes. Incident reports and patrol checklists run as digital forms completed on the guard's phone, timestamped and stored against their record — ready for the client report in the morning.

Hours are recorded exactly as worked, with weekends identifiable and public holidays split against your state's calendar, then exported payroll-ready for Xero, MYOB, KeyPay (Employment Hero Payroll) or Employment Hero. Your payroll applies the loadings your award or agreement — commonly the Security Services Industry Award — requires.

Yes. Role-based permissions let each supervisor run their own portfolio of sites while operations management keeps full visibility across every post and every guard.