Everything in the SafeBeats patrolling application
SafeBeats is a beat patrolling application and guard tour system for security teams. Guards patrol with an Android phone; supervisors watch the same patrol live on the web and receive the report by email when the shift ends.
Checkpoints and proof of presence
QR checkpoint scanning
Every beat point gets a printable QR tag. The guard scans it on arrival, which records who was there and exactly when. Tags can be regenerated if one is damaged or tampered with, without rebuilding the route.
Geo-fenced check-ins
Each checkpoint carries a GPS boundary. A check-in only counts when the phone is physically inside it, so a patrol cannot be completed from the guard room or the car park.
Indoor positioning without GPS
GPS is unreliable inside basements, stairwells and multi-floor buildings. SafeBeats can learn the WiFi signature of an indoor checkpoint and use it to confirm the guard's position where satellite signal does not reach.
Guard face verification
Optional face verification confirms that the guard assigned to the beat is the one actually walking it, rather than a colleague carrying two phones.
Offline beat recording
Patrols continue through dead zones. Check-ins, photos and notes are stored on the device and sync automatically once the phone is back on a network, with the original timestamps intact.
Device-independent routes
Routes belong to the site, not to a handset. A guard can pick up any authorised device and the correct beat is waiting, which matters when shifts rotate or a phone goes flat.
Running the shift
Flexible beat schedules
Define how often a beat runs, on which days, and within what time window. Night rounds, weekend-only rounds and hourly rounds are all configured the same way, and a schedule can be copied to a similar site instead of rebuilt.
Checkpoint checklists
Attach questions to a checkpoint so the round produces answers, not just a timestamp: is the fire door shut, is the pump running, is the gate locked. Answers land in the same report as the check-in.
Live patrol tracking
Supervisors see the round in progress on a map — which checkpoints are done, which are pending, and where the guard is now — instead of waiting for the morning report.
Incident and anomaly reporting
Guards log an incident from the checkpoint with photos and notes, tagged by type. Each type can have its own mailing list, so a fire hazard reaches the safety officer and a broken light reaches maintenance.
Emergency SOS
A guard in trouble raises an SOS from the phone. The alert reaches the control room with the guard's location immediately, and stays open on the dashboard until someone marks it resolved.
Missed checkpoint alerts
A round that is skipped, cut short or started late raises an alert while the shift is still running, which is when it can still be corrected.
Audits, assets and reporting
Apparatus audits
Fire extinguishers, hydrants, alarms and other safety equipment get their own QR tags and inspection schedules. SafeBeats tracks when each item was last checked and raises the ones that are overdue.
Automated report emails
Patrol, SOS, incident and audit reports go out on a schedule you set, to the people who need them. Nobody has to log in and export a spreadsheet to find out how last night went.
Branches, departments, supervisors
Multi-site operations are organised by branch and department, with supervisors scoped to what they are responsible for. A regional manager sees every site; a site supervisor sees theirs.
On-premise deployment
Where patrol data cannot leave the site — defence, certain plants, some campuses — SafeBeats runs on a server inside your own network instead of our cloud.
Configurable data retention
Patrol history and incident media are kept for the period you specify and then removed automatically, so retention matches your own policy rather than ours.
Exportable patrol reports
Download patrol history, check-in logs, SOS records and audit results for a date range when a client review, an insurance query or a compliance audit asks for evidence.
How a SafeBeats patrol actually runs
A site is built once: you add the beat points, print the QR tags, mark the geo-fence for each point and set the schedule the beat should follow. From then on the round is the same every night.
The guard opens the app at the start of the shift and sees the beat due now. At each checkpoint they scan the tag; the app confirms they are inside the geo-fence, records the time, and asks any checklist questions attached to that point. If something is wrong, they photograph it and log it as an incident before moving on. If the phone has no signal, nothing changes — the round is stored locally and uploaded later.
Meanwhile the supervisor watches the round fill in on the dashboard. A missed or late checkpoint shows up immediately rather than the next morning. When the shift ends, the report is generated and emailed to whoever is on the distribution list — typically the site manager, and for client sites, the client.
That is the whole loop, and it is the difference between a patrol you believe happened and a patrol you can prove happened. If you want to see it against one of your own sites, request a demo and we will set up a sample route before the call.
See the patrolling application on your own site
Book a walkthrough and we will map one of your existing patrol routes into SafeBeats so you can see the reports it would have produced.