Security & guarding
Static posts, patrols, armed response and relief across every client site — rostered by AI against PSIRA grading and Sectoral Determination 6, with attendance captured however the site captures it and the margin on every contract visible before the month is out.
What it costs you today
A month across dozens of client sites is built in a spreadsheet by one person who understands it. When a guard resigns on the 12th, the whole thing has to be reasoned through again by hand.
Nobody sees the overtime forming until payroll runs. By then the hours are worked, the money is owed, and the site that caused it has already eaten the month’s margin.
Attendance comes back on paper from half the posts, off a biometric terminal at the rest, and by WhatsApp from the controllers. Somebody types all of it in, twice, under month-end pressure.
A client audits the site and finds an officer whose registration expired six weeks ago. The certificate was in a folder; nothing was watching the date.
You know what you invoice a client. What that contract actually cost you in wages, overtime and Sunday loading is a number the accountant produces months later.
The roster, the pay rules and the client’s peculiar requirements live in one head and one workbook. That is an operational risk, not a system.
What AutoRoster does about it
Define what each post needs — 24/7 static, day patrol, armed response, relief — and AutoRoster fills it with officers who are graded for it, rested under BCEA and available. Change one shift and it re-solves the rest.
Grade, registration number and expiry sit on the officer record. A post can demand a minimum grade, and a lapsed registration blocks deployment before it becomes a client’s finding.
Photograph the signed register and it is parsed into shifts against the right post and date. Biometric exports, mobile clock-ins and controller messages come through the same pipeline.
Ordinary hours, overtime thresholds, Sunday and public-holiday multipliers, night-shift allowance and short time — computed from what was actually worked, per employee, per period.
Wage cost against contract value on every site, projected to month end from actuals to date. The site that is bleeding shows up while the roster can still be changed.
A no-show is logged and replacements are proposed: graded for the post, rested, not already on shift, and costed so you know what the cover is going to add.
GPS-verified clock-in on an entry-level Android handset, queued while there is no signal, reconciled when the phone reconnects. Useful precisely where the terminals are not.
We import EasyRoster databases directly — employees, sites, shift patterns, pay rules and years of attendance — and reconcile the result against your own numbers before you depend on it.
Who changed which shift, when, and what the roster looked like on the day. Role-based access on every screen, and data hosted in South Africa.
Questions
Yes. Every officer carries their PSIRA grade, registration number and expiry date, and every post can require a minimum grade. The roster will not place an ungraded or lapsed officer on a post that demands one, and expiries are surfaced weeks ahead so renewals happen before deployment is affected.
Pay is calculated from actual worked shifts against the determination that applies to each employee, including ordinary hours, weekly and monthly overtime thresholds, Sunday and public-holiday multipliers, night-shift allowance and short time. The rules are configurable per company, because not every operator runs every employee under the same determination.
Yes — those are different post types with different coverage requirements, grade requirements and pay implications, and AutoRoster models them separately while rostering them as one problem. That is the point: a relief officer covering a patrol shift affects the static post they were going to cover.
No. Photograph the signed register and upload it; AutoRoster reads it and matches each line to the rostered shift for that post and date. Sites that have biometric terminals keep using them. You do not have to standardise every site before you can start.
We import your EasyRoster database directly, including employees, branches, sites, shift patterns, pay rules and the attendance history behind them. Nothing is truncated to fit, and we reconcile the imported figures with yours before go-live, so you are not running two systems in parallel for a year.
Hours and earnings export in the shape Sage, VIP, PaySpace, Pastel or your bureau expects, plus a generic CSV. AutoRoster produces the numbers; your payroll keeps paying people.
Bring one site and one month. We will build the roster, cost it, and tell you plainly whether AutoRoster is the right fit — including when it is not.
