What a Guard Tour Patrol System Does
A guard tour patrol system proves that a guard physically visited a set of locations in a set order within a set time. It does this by placing a checkpoint at each location, giving the guard a device that reads the checkpoint, and recording each read with a timestamp. The output is a report that shows, for each round, which checkpoints were visited, when, by whom, and which were missed.
The problem it solves is old. A guard on a night shift at a warehouse is supposed to walk the perimeter every hour. Without a patrol system, the only evidence is the guard's own DOB entry, 'patrol round 3 completed, 02:00'. With one, the evidence is a scan at the north fence at 01:52, the loading dock at 01:58, the generator room at 02:04 and the main gate at 02:09. One is a claim; the other is a record.
The guard tour glossary entry and the patrol checkpoint entry define the terms. This article explains how the systems work, how to configure them, and how to choose between the two dominant models.
- Checkpoints fixed at locations the guard must visit
- A reader carried by the guard records each visit with time
- Rounds defined with sequence and time windows
- Reports show completed, late and missed checkpoints per round
- Turns 'patrol completed' from a claim into a timestamped record
Wand and RFID Tags vs Smartphone With NFC and QR
The traditional system is a rugged handheld wand and passive RFID tags screwed to walls at each checkpoint. The guard touches the wand to each tag; the wand stores the reads; at the end of the shift the wand is docked to a computer and the data downloaded. Wands are robust, need no network and no phone, and the tags are almost indestructible. Their limits are equally clear: data arrives after the shift, not during it, so a missed checkpoint is discovered in the morning; each wand and each dock is a piece of hardware to buy, maintain and replace; and the wand knows nothing about who is holding it.
The smartphone model replaces the wand with the guard's own phone or a shared site phone, and the tags with NFC stickers or printed QR codes. The guard taps the NFC tag or scans the QR code in the app; the read is timestamped, GPS-located and uploaded immediately over mobile data, or queued offline and synced when the network returns. Because the phone is also the attendance device, the system knows who the guard is (face or selfie verification at shift start), whether he is on shift, and where he is. A missed checkpoint triggers an alert to the supervisor in real time.
The trade-offs are practical. Phones need charging and can be dropped; NFC tags cost more than QR codes but cannot be photographed and scanned from elsewhere; QR codes are cheap and printable but should be combined with GPS verification so a photocopy in the guard room does not count as a patrol. For most agencies the smartphone model wins on cost and on real-time visibility, and the wand model survives at sites with no mobile coverage or a client policy against phones on post.
- Wand + RFID: rugged, offline, data downloaded after shift; hardware per site; no identity check
- Smartphone + NFC: real-time upload, GPS stamp, tied to attendance identity; tags cannot be copied
- Smartphone + QR: cheapest checkpoints; combine with GPS check to defeat photocopied codes
- Offline queueing in the app covers network gaps at basements and remote sites
- Wands remain useful where phones are prohibited or there is no coverage
Setting Up a Patrol Round
A round is a named set of checkpoints in a defined sequence with a time window and a tolerance. 'Night Perimeter' at a warehouse might be eight checkpoints starting at the main gate, running clockwise around the fence, through the loading dock and generator room, and back to the gate, to be completed every two hours between 20:00 and 08:00, with each checkpoint scanned within 15 minutes of its expected time.
Sequence matters because it prevents a guard from scanning three nearby checkpoints in a minute and skipping the far corner. Time windows matter because a round completed at 21:00 and 06:00 with nothing in between is not hourly patrolling. Tolerance matters because a guard delayed by a genuine visitor at the gate should not generate a false alarm; 10 to 20 minutes is typical. Randomised rounds, where the system varies the sequence or start time, defeat the predictability that an observer outside the fence would otherwise exploit.
Place checkpoints where the guard's presence has value: at the points of vulnerability (fence corners, rear gates, fire exits, cash rooms, server rooms, pump rooms) rather than at convenient places along the guard's path. A checkpoint should also require the guard to look at something: a tag placed on the fire exit door forces a check that the door is closed; a tag on the corridor wall opposite it does not.
- Define each round: name, checkpoints, sequence, frequency, time window, tolerance
- Enforce sequence to prevent clustering scans
- Set frequency to the client's requirement (hourly, two-hourly) and window to the shift
- Randomise where the site is observable from outside
- Put checkpoints at vulnerabilities, on the object to be checked
Proof-of-Patrol Reports and Missed-Checkpoint Alerts
The proof-of-patrol report is the deliverable to the client. Per site, per day, per round it shows each expected checkpoint, the scheduled window, the actual scan time, the guard who scanned it, and the status (on time, late, missed). Summaries show completion percentage per round and per guard, and trends across the month. Most clients want this weekly or monthly as a PDF; some want a live dashboard.
Missed-checkpoint alerts are what turn the system from record-keeping into supervision. When the window for a checkpoint passes without a scan, the supervisor receives a notification and can call the guard or the post. The most common causes are benign (guard held at gate, phone battery dead, network outage in a basement) but the alert forces a response, and a pattern of misses at the same checkpoint on the same shift is exactly what a supervisor's surprise visit should follow up.
Reports also protect the guard. A theft discovered in the morning at a loading dock that shows scans at 23:58, 02:01 and 04:03 narrows the window and demonstrates the guard did his rounds. Without the record, the guard is the first suspect by default.
- Per round: expected checkpoints, window, actual time, guard, status
- Per site and per guard: completion rate and trends
- Alerts on missed windows to the supervisor in real time
- Follow up patterns of misses with site visits
- Records protect diligent guards as much as they expose negligent ones
Integrating Patrols With Attendance and Incidents
A patrol scan is only meaningful if the person scanning is the guard who is supposed to be on that shift at that site. Standalone patrol systems cannot check this; they record that a device touched a tag. When the patrol module runs inside the same app as attendance, the system knows the guard marked in with a verified selfie at 19:55 at the site geofence, is rostered on the Night Perimeter round, and is therefore the person whose scans count. A scan by a guard who is not on shift, or at a site he is not deployed to, is flagged.
Integration also connects patrols to incidents. A guard who finds a fire exit propped open at checkpoint 5 should be able to raise the incident from the same screen, with the checkpoint, time and photograph attached, rather than finish the round and remember to write it up. Attend Mitra's security guard patrol monitoring software runs guard tour and patrol monitoring with NFC and QR checkpoints alongside guard attendance with GPS and selfie, GPS live tracking, incident reporting and SOS alerts, so the patrol record, the attendance record and the incident record are one record per shift.
The guide on verifying guards are on site covers the attendance side of this; the patrol system is the layer that verifies the guard was not only on site but moving through it.
- Only scans by the rostered, verified, on-shift guard count
- Scans at sites the guard is not deployed to are flagged
- Incidents raised from the checkpoint screen carry location, time and photo
- SOS from the same app during a round reaches the supervisor immediately
- One record per shift: attendance, patrols, incidents, duty report
Cost Comparison and Choosing Checkpoints by Site Type
A wand system has a fixed hardware cost per site (wand, dock, tags, software licence) plus replacement wands over time, and a labour cost for downloading and compiling reports. A smartphone system has a per-user software cost, the cost of NFC tags or printed QR codes, and either the guard's own phone or a shared site phone. For an agency running many small sites, the smartphone model is usually cheaper because it avoids hardware at each site; for a single large site with no coverage, a wand may still make sense. Prices vary by vendor and volume, so compare total cost over three years rather than the sticker price.
Checkpoint placement depends on the site. In a residential society: each block entrance, the basement parking levels, the generator and pump rooms, the terrace access doors, the rear or service gate, and the children's play area at night. In a warehouse: fence corners, every dock door, the cage or high-value store, the generator, the transformer yard, and the gate. In a mall: fire exits on each floor, the service corridors, the loading bay, the cash room area, escalator landings after hours, and the rooftop plant room. In a factory: the boundary at fixed intervals, the scrap yard, the DG set and the fuel store, the raw material store, the canteen after hours, and the main and worker gates.
The guiding principle is that each checkpoint should be at a place where a guard's visit changes the risk. If a tag could be removed and nobody would notice a security difference, it is in the wrong place.
- Compare three-year total cost: hardware, replacement, licence, tags, phones, reporting labour
- Societies: block entrances, basements, plant rooms, terrace doors, service gate
- Warehouses: fence corners, dock doors, high-value cage, generator, transformer, gate
- Malls: fire exits per floor, service corridors, loading bay, cash room, plant room
- Factories: boundary intervals, scrap yard, DG and fuel store, stores, canteen, gates
Buyer Checklist
Before choosing a guard tour system, test it on one site for a month with your least technical guards. The list below is what to confirm during that trial. The guide to choosing attendance software for a security agency covers the wider selection process, and the security guards industry page summarises how the pieces fit together for an agency.
- Does a scan work offline in a basement and sync later without loss?
- Is each scan GPS-stamped, and can a photocopied QR code scanned elsewhere be detected?
- Can rounds enforce sequence, frequency, time windows and tolerance, and be randomised?
- Does a missed checkpoint alert the supervisor within minutes, not the next morning?
- Is the scanning guard verified against the attendance record and roster?
- Can an incident with photo be raised from the checkpoint screen?
- Are proof-of-patrol reports available per site, per round and per guard, as PDF and export?
- Can the client be given read-only access to their own site's reports?
- What is the tag replacement process and cost, and who does it?
- How does the system handle a guard whose phone dies mid-round?