VisitsTracker › Guard tours
A guard tour system with nothing to scan
Every other guard tour system puts NFC tags or QR codes at the checkpoints and asks the officer to scan them. A scan proves a phone touched a sticker. Time inside the boundary proves the officer stayed.
No card needed. Set up in an afternoon.
What you get
Patrol proof that does not depend on a sticker
No tags, no codes, no wands
Nothing to install at a site and nothing to replace when it is painted over, prised off or lost. You draw the boundaries or import them, and the patrol records itself from then on.
Time on site is the proof, not a tap
Ten minutes inside a boundary becomes a visit with the time in and the time out. A scan tells you a phone was briefly near a wall. A dwell tells you the officer was there, and for how long.
Faked positions are flagged and kept
A phone can be made to report a position it is not at. Those readings are spotted and marked, and never count toward a patrol, an hours total or a mileage claim. They stay visible, including in whatever you send the client.
Missed patrol windows surface live
Give a patrol a slot. If it has not started by the time the window closes you are told, rather than finding out when the client asks on Monday.
Gone-quiet alerts on a lone officer
If an officer has clocked in and their phone then stops reporting for around three quarters of an hour, you get an alert, once for that shift. A phone that is not reporting is not protecting anybody.
An SOS that reaches everyone who can see them
Held behind a confirm step in the app. It emails every owner, admin and manager above that officer immediately, raises the alert in the console, and posts it to any webhook you have set up, carrying a link a responder can open without an account.
The client gets their own page
A standing link showing that site’s last 90 days of patrols and photos with your logo on it, plus expiring links when somebody asks about one particular night.
The night is sealed
Each day gets a fingerprint. Change a reading afterwards and that day stops matching, so you can show the log was not edited rather than asking to be believed.
Where a tag still wins
A QR or NFC tag proves an officer reached one exact point inside a large building, which a single site boundary cannot tell apart. If your contract specifies interior checkpoints on separate floors, a scanning system answers something we do not. For perimeter patrols, mobile rounds and multi-site work, time on site is the stronger record and there is nothing to maintain.
Straight answers
Questions people ask
Do we have to install anything at the sites?
No. There are no tags, QR codes, beacons or wands to buy, fit or replace. You draw each site’s boundary on a map, or import boundaries you already hold, and the officer’s phone does the rest.
How is a patrol proven without a scan?
By time spent inside the boundary, built only from readings we trust, with arrival and departure recorded. A reading flagged as faked never counts toward it.
What stops an officer faking their location?
Readings from mock-location tools are detected and marked. They do not count toward a patrol, hours or mileage, but they stay in the record and in anything you send out, so the gap is visible rather than quietly dropped.
Can the client see the patrols themselves?
Yes. Each client gets a standing link to their last 90 days with your branding, and you can send an expiring link covering a single night or a single visit.
Is this a monitored alarm service?
No. SOS and gone-quiet alerts go to your own managers by email, in the console and on your webhooks. There is no manned response centre behind it and no push banner on a manager’s lock screen, so treat it as an alert somebody reads. If your risk assessment needs a monitored service or a certified device, you need one of those as well.
Also part of VisitsTracker
The rest of the product
Try it on one van for a week.
Put it on one phone, run a normal week, and see what comes out the other end.