Proof of presence, not proof on paper
A patrol register signed at 6 am proves one thing: someone signed a register at some point. Checkpoint systems replace that with proof of presence, a scan that says this guard, this point, this minute. This guide explains the three technologies, the deployment decisions and the reading of logs.
Operator guide, written August 2026. Security practice varies with premises and state rules; treat this as method, and your society's bye-laws and local police guidance as the authority.
What a checkpoint system actually is
Strip the vendor language and every guard patrol system is the same machine: fixed points around the premises, a way for the guard to register presence at each point, and software that turns those registrations into a timeline. The differences that matter are how presence is registered, a QR sticker scanned by phone, an NFC tag tapped, or GPS position logged passively, and what happens when a point is missed. Everything else, dashboards, reports, escalations, is presentation over that timeline. Judge systems by the honesty of the timeline: can a scan be faked from the guard room, can a missed round hide, and can the committee read last night in one minute.
QR versus NFC versus GPS
QR stickers are the cheapest and fastest to deploy: print, laminate, stick, scan with any phone. Their weakness is photographability, a guard can photograph the code once and scan the photo from a chair, which is why serious deployments pair QR with geofencing or rotate codes. NFC tags cost more and need the phone physically at the tag, within centimetres, which kills the photograph trick; they survive weather well and suit high-stakes points like pump rooms and transformer yards. GPS logging removes fixed points entirely and traces the walked route, at the price of battery drain, indoor blind spots in basements and stilt parking, and less precise proof at any single point. Most societies do well with QR at ordinary points, NFC at critical ones, and GPS only where routes cross open ground.
Placing checkpoints so they mean something
Checkpoint placement is route design in disguise. Points belong where presence has value: the dark stretch of perimeter behind the generator, the basement lift lobby, the terrace door that should be locked, the pump room whose motor walks away in half the burglaries in the city. Points do not belong wherever is convenient to stick a code. Walk the premises at 2 am once, with the security supervisor, before finalising anything; the places that feel wrong at 2 am are the checkpoint map. Then sequence them so the natural walking route alternates unpredictably, two fixed routes walked alternately beat one route walked identically, because predictability is what an observer outside the fence is measuring.
Reading the logs without drowning
The log's job is answering three questions fast: did the rounds happen, where do misses cluster, and is the pattern drifting. A committee member should read a one-screen summary weekly, rounds completed against scheduled, misses by point and by shift, and spend attention only where the numbers cluster. Guard-wise league tables mostly poison the guard room; point-wise and shift-wise views find the actual problems, a route that is too long to complete honestly, a shift that is understaffed, a point whose tag has weathered into unreadability. The log is a management instrument, not a disciplinary archive, and societies that use it as the former get better security from the same guards.
Rolling it out without a mutiny
Guards experience checkpoint systems as surveillance, because that is what they are. The rollout that works is candid about it and pairs the ask with fixes guards have wanted for years: routes shortened to walkable, torches and raincoats that work, a duty phone that holds charge. Train on the device in daylight, run two weeks where misses trigger conversations rather than consequences, and publish the same summary to the committee that the supervisor sees, so the system reads as the society taking night security seriously rather than management catching guards out. The agencies that staff your gates have seen these systems before; the good ones prefer societies that run them, because provable rounds are also the guard's defence when something goes missing.
How EstateDeck applies this
EstateDeck's patrol monitoring runs exactly this machine: QR and NFC checkpoints, geofenced scans, missed-scan alerts to the supervisor, and a weekly summary the committee reads in a minute.
Go deeper: Patrol monitoring · Visitor management
Written by Databus Technology Solutions, the makers of EstateDeck. These guides describe how housing societies and property operations run in practice; they are not legal advice. Cooperative and apartment law varies by state and changes on its own schedule, so verify specifics against your state's act and your society's bye-laws before acting.
Frequently asked questions
Can guards fake QR scans by photographing the codes?
A bare QR system, yes. The standard counters are geofenced scanning, the scan only counts if the phone's location matches the checkpoint, rotating codes, or NFC at points where it matters. Ask any vendor which of these they implement before believing a demo.
How many checkpoints does a typical society need?
Enough that walking them covers what actually needs eyes: perimeter corners, tower lobbies, basements, pump and meter rooms, terrace doors, and the gates themselves. Mid-size societies commonly land between 15 and 30 points; fewer means blind stretches, many more means scan theatre that guards learn to resent.
What should happen when a scan is missed?
A single miss wakes the supervisor, not the committee: a nudge to the guard, a check-in call. A pattern of misses on the same point or shift is a roster or route problem and belongs in the weekly review. Systems that alert nobody make missed rounds normal; systems that alert everyone train people to ignore alerts.
Do checkpoint systems work for a single guard on night duty?
They work best there. One guard, one route, one timeline; the log shows the round happened at 1 am and 3 am or shows it did not, and the morning conversation is specific either way. The system is the night supervisor a single-guard society cannot afford to employ.
What does a checkpoint system cost a society?
Printing figures here would mislead, because the spread is wide and moves. What drives cost is knowable: tag hardware (QR nearly free, NFC per tag), a duty phone or wand, and the software subscription, usually priced per premises or per guard. The comparison that matters is against one month of the security agency bill; checkpoint systems typically live well under it, which is why the decision is usually about will, not budget.
Phone-based scanning or dedicated devices?
Phones win on cost and familiarity and lose on battery discipline and breakage disputes. A society-owned duty phone that hands over between shifts, charged at the guard room, is the common middle path; dedicated patrol wands survive abuse better but add cost and a second thing to maintain.
Make last night readable.
Applied on every payslip, files generated for upload — per employee, per month.
Start free