How to choose a guard tour system (without wasting a month)

Buying guide Published 12 January 2026 · 8 min read

Every guard tour system does the same three things on the brochure: scans checkpoints, shows a map, produces reports. Compare on features and you will conclude they are interchangeable, pick on price or on whoever called you back first, and discover the differences in week six.

Here is a shorter route. Six questions, asked of every vendor, in the same week.

1. Ask to see the guard app, not the dashboard

This is the single most useful thing you can do, and most buyers skip it. The manager dashboard will be used by two people in an office with a big screen and no time pressure. The app will be used by forty officers, at night, in the rain, some of whom are not confident with phones.

On the demo, ask them to walk through scanning a checkpoint. Count the taps. Anything over two or three and you have an adoption problem coming. Then ask them to file an incident with a photo. If it takes more than about ninety seconds, your officers will do it at the end of shift from memory — which defeats the point.

2. Ask what happens with no signal

Ask it directly, in those words, and listen carefully to the answer. A good answer describes queuing scans on the device and syncing automatically with the original timestamp preserved. A vague answer — "you'd normally have coverage" — means you will silently lose records in basements, plant rooms and rural sites, and you will not know which ones.

3. Get the twelve-month total, in writing, at your headcount

Not the per-guard rate. The total. Include the setup fee, any per-site charge, extra admin users, the scheduling module if it is separate, training, and support if it is not included.

Then ask what that number becomes if you win a contract and add twenty officers. Per-guard pricing quietly penalises growth, and it is worth knowing the shape of that curve before you are on it. We wrote up how the real cost breaks down here.

4. Ask for a real client report as a PDF

Not a screenshot in a slide deck — an actual exported report from a real site. This is what your customer will see, and as far as they are concerned it is the product.

Look at it as if you were the client. Is it obvious what happened? Would you be comfortable forwarding it without editing? Could a facilities manager understand it without a phone call? If you would need to explain it, you will be explaining it every week for the next three years.

5. Ask about the tags

Some vendors sell proprietary checkpoint tags you can only buy from them. That changes the economics considerably — a hundred checkpoints across your sites at a marked-up price is a real number, and it recurs as tags are lost, vandalised or fitted at new sites.

Standard NFC tags cost pennies from any supplier. Ask specifically whether theirs are standard, and whether tags from another vendor can be reused if you migrate. More on choosing between NFC and QR here.

6. Ask how you would leave

Nobody asks this on a demo call, and it tells you more about a vendor than almost anything else. Can you export every patrol record, incident report, timesheet and invoice? In what format? Is there a charge? What is the notice period?

A supplier who answers that comfortably is confident you will not want to leave. A supplier who gets uneasy has told you something important.

A sensible process

1. Write down your three real problems. Not a feature list — the three things that cost you time or money every week.
2. Shortlist three vendors. More than that and the comparisons blur.
3. Book all three demos in one week so you can actually compare them.
4. Ask all six questions above of every one, and write the answers down.
5. Trial the leader on one site with one supervisor and two officers, for a fortnight.
6. Ask those officers whether it is fine. Their answer is the decision.

The one thing worth over-weighting

If we could only give you one piece of advice: weight the guard-side experience far more heavily than you think you should. Guard tour rollouts do not fail because the reporting was insufficiently detailed. They fail because officers found the app irritating, started skipping scans, and within three months the data was too patchy to send a client.

A slightly plainer system that everybody uses beats a sophisticated one that half the workforce works around.