Night security is a route, walked
Every society believes it has night patrols; the log usually shows a signature at handover and hope in between. Real night security is a designed route, walked at known frequencies, with proof at the points that matter and a review that notices drift. This is the setup, end to end.
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.
Designing the route from the 2 am walk
Routes designed in the committee room protect the committee room. Walk the premises after midnight with the supervisor and the senior guard, and let the walk write the route: the perimeter stretch the streetlights miss, the basement corner behind the water pumps, the terrace doors, the generator yard, the compound wall the neighbouring plot's scaffolding now overlooks. Order the points into a walkable loop, twenty to forty minutes for most societies, and time it honestly with the actual guard walking at watch pace, not a committee member striding. A route that cannot be walked comfortably in its window will be completed on paper instead.
Frequency, and the myth of the hourly round
Hourly rounds sound rigorous and mostly produce exhausted guards and rubber-stamp scans. Risk is not uniform across the night: the burglary hours cluster after 1 am, deliveries and residents thin out after 11, and the vulnerable points are static. A common honest pattern is a full perimeter round every two hours from 11 pm, with critical points, pumps, terrace, gates, touched more often via a short inner loop, and randomised offsets so the schedule cannot be clocked from outside the fence. Fewer, real rounds beat frequent fictional ones, and the checkpoint log is what makes the difference visible.
Step by step
-
1
Walk the premises after midnight
Let the 2 am walk, not the site map, choose the vulnerable points the route must cover.
-
2
Fix the route and time it honestly
A loop the actual guard completes at watch pace within its window; shorten the route before shortening the walking.
-
3
Place checkpoints at the points that matter
QR at ordinary points, NFC at critical ones; every point earns its place by what it watches, not by convenience.
-
4
Set frequencies by risk, not ritual
Full loop every two hours from 11 pm, critical inner loop more often, minutes randomised within windows.
-
5
Wire the escalations
A missed scan nudges the guard, a missed round wakes the supervisor, a pattern reaches the weekly review — in that order.
-
6
Review weekly, visit occasionally
Five minutes on misses by point and shift; one unannounced night visit a month keeps the timeline honest.
The handover, where night security leaks
Most night incidents trace to the seams: the 8 pm and 8 am handovers where nobody owns the premises for twenty minutes, and the meal break nobody rostered. Write the handover as a checklist, keys counted, duty phone charged and passed, exceptions from the outgoing shift read aloud, first round started within fifteen minutes, and make the first scan of the incoming shift part of the log. Roster the meal break explicitly with the gate covered. None of this needs software; all of it shows up in the checkpoint timeline when it slips, which is why the timeline is the supervisor's first morning read.
What the committee should ask for monthly
One page: rounds scheduled versus completed, misses by point with the repeat offenders named as points rather than people, exceptions logged and what was done about them, and any route or roster change proposed with a reason. A committee that reviews that page monthly gets guards who walk, an agency that rosters honestly, and, the quiet benefit, a defensible record if an incident ever reaches an insurer or a police complaint. Societies rarely regret the system on the night something happens; they regret the years of signatures that proved nothing.
How EstateDeck applies this
EstateDeck runs the machinery under this guide: checkpoint scans with geofencing, scheduled windows with randomised tolerance, missed-scan escalation and the one-page weekly review, wired to the same system that runs the gate and the visitors.
Go deeper: Patrol monitoring · ANPR gates
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
What should the guard actually do on finding something wrong?
Observe, report, and hold position unless safety requires otherwise — the round is a tripwire, not a response team. The escalation ladder should be printed and drilled: supervisor first, the committee's duty contact second, police for anything criminal in progress. A guard who knows exactly whom to call at 2 am acts in seconds; one who has to decide hierarchy in the moment loses the minutes that mattered.
How many guards does a night roster need?
Premises decide: one guard can cover a small society with a gate and a short loop; a multi-tower campus needs the gate held while a second guard walks. The failure mode is a roster that assigns the round and the gate to the same person simultaneously, which guarantees one of them is fiction.
Should rounds be at fixed times or randomised?
Fixed windows, randomised minutes. The supervisor needs predictability to verify; an observer outside should not be able to set a watch by the guard. Checkpoint systems with scheduled-window tolerance give exactly this shape.
What belongs in the guard's night log besides scans?
Exceptions: the parked car that does not belong, the tube light out on tower C, the terrace door found unlatched, the drunk visitor argument at 1am. One line each, against time. The scan proves the walk; the notes carry the information, and the morning review reads both together.
How do we verify rounds without standing there at 2 am?
That is precisely what checkpoint proof of presence is for: the scan timeline is the verification. Pair it with a weekly five-minute review of misses by point and shift, and an occasional unannounced night visit by the supervisor, monthly is plenty, so the system knows someone occasionally looks with eyes.
Do CCTV cameras make patrol rounds unnecessary?
Cameras record; patrols deter and respond. A camera watching the pump room produces excellent footage of the theft for the insurance file; a guard walking past it at randomised intervals changes whether the theft is attempted. The two work as a pair — rounds cover the blind spots and the response, cameras cover the record — and the patrol log plus footage together are what an investigation actually uses.
What if the agency resists the system?
Good agencies embrace provable rounds, they are also the guard's alibi when something goes missing. Resistance usually means the current roster cannot actually deliver the rounds being billed, which is exactly the information the society needed. Renegotiate the roster to what is walkable, then hold it.
Rounds that happened, provably.
Applied on every payslip, files generated for upload — per employee, per month.
Start free