How to run night patrol rounds in your society
Night patrols are the shift that matters most and the one nobody watches. This is how to design rounds that get walked, supervise them without being awake, and handle what the guard finds.
Effective night patrols need a route timed at walking pace, a frequency the guard can actually sustain, checkpoints placed where incidents occur rather than where it is convenient to walk, and exception alerting so a missed round reaches a supervisor during the shift rather than in the morning report.
Why night patrols quietly fail
Almost every society pays for night patrolling and almost none can say whether it happens. The shift runs from around ten at night to six in the morning, there is no supervisor present, no residents are watching, and the only record is a register signed at some point before handover. The conditions for the work not being done are close to perfect, and no reasonable person should be surprised when it is not.
The failure is usually not laziness. It is design. A round of forty minutes scheduled every thirty minutes cannot be walked as specified, so the guard adapts by shortening it — and once a route is being improvised, coverage becomes whatever is convenient. A guard who is also expected to handle the gate, take deliveries and answer the intercom has a patrol that is by definition interruptible, and it gets interrupted.
Fixing this starts with accepting the constraint. One guard cannot simultaneously man a gate and patrol a property. Either the round is scheduled around gate duty with realistic timings, or a second person is on shift. Deciding that honestly is worth more than any amount of monitoring technology.
- Impossible schedules train corner-cutting. A forty-minute route on a thirty-minute cycle guarantees improvisation.
- Gate duty interrupts patrolling. One guard cannot do both; the schedule has to acknowledge that.
- Nobody is watching at 3am. Which is exactly why exception alerting matters more at night than by day.
Designing effective night rounds
Three decisions — where, how often, and which points — and they interact.
Route planning
Walk the route yourself at guard pace, at night, with a stopwatch. Almost every committee that does this discovers the route they specified takes half as long again as they assumed, particularly once stairwells and basement levels are included. The measured time is the input to the frequency decision; the assumed time is how bad schedules get made.
Design the route to end near the gate, so a guard returning from a round is back where they need to be. A route that ends at the far boundary produces a walk back that gets skipped, which quietly removes the last section from coverage.
Frequency and timing
Two to three rounds per night is realistic for a single guard who is also covering the gate. Four is achievable with two guards on shift. More than that on a single guard means either a very small property or a fictional schedule.
Vary the start times rather than the route. Rounds at fixed hours create predictable gaps that anyone observing the property for a few nights can identify. Randomising the timing within windows — one round between eleven and midnight, one between one and two, one between three and four — preserves coverage while removing predictability.
Checkpoint placement
Place checkpoints where incidents actually occur. In Indian residential properties that means basement and stilt parking first, then terrace and roof access, the rear boundary and any service gate, pump and electrical rooms, and ground-floor windows facing common areas.
Twelve to twenty checkpoints covers most residential properties. Fewer leaves gaps a guard can exploit without missing a scan; many more turns the round into a scanning exercise where the guard is looking for tags rather than at the property.
Supervising without staying up all night
Nobody should be awake supervising a night shift, and nobody will be. Supervision at night therefore has to be by exception: the system watches, and it wakes somebody only when a round does not happen.
That means a missed checkpoint raises an alert during the shift rather than appearing in a morning report. Who it reaches should escalate — first the security supervisor, and only if unacknowledged after a set period the committee member holding the security portfolio. A committee member woken at 3am for the first missed scan will stop taking the alerts within a fortnight.
The morning review is the other half. Someone should look at the previous night’s exceptions each day — it takes two minutes — and the monthly compliance figure should be a standing item at committee meetings. A patrol system whose reports nobody reads reverts to a signature register with extra steps within a quarter.
- Alert during the shift, not after it. A missed round at 2am is actionable; the same fact at 9am is a statistic.
- Escalate in tiers. Supervisor first, committee only if unacknowledged.
- Two minutes each morning. Someone named reviews last night’s exceptions.
- Monthly compliance at committee. Coverage percentage per shift, as a standing agenda item.
Handling incidents during night rounds
A guard who finds something at night faces a decision most training does not cover: deal with it, report it, or continue the round. Getting this wrong in either direction is costly — a guard who investigates a noise alone can be hurt, and a guard who continues past a propped fire door has rendered the patrol pointless.
The rule worth writing down is that a guard observes and reports but does not confront. An unfamiliar person in the basement is a call to the supervisor and the police if warranted, not an approach by a single unarmed guard at three in the morning. A society that expects otherwise is taking on a liability it has not thought about.
Everything found should be recorded at the time with a photograph, whether it is a security matter or a maintenance one. In practice most night findings are maintenance — a leaking pipe, a failed corridor light, a lift door not closing — and those are worth as much as the security value. A fault reported at midnight and fixed by ten in the morning is a complaint that never happened.
- Observe and report, never confront. And say so explicitly in the guard instructions.
- Photograph everything found. Location and time come with it if capture is in-app.
- Escalate by category. Security to the supervisor and police; maintenance to the morning queue.
- Most findings are maintenance. Which is where much of the night round’s value actually comes from.
A sample night patrol schedule
This assumes one guard covering both the gate and the rounds — the common arrangement. With two on shift, four rounds becomes realistic.
| Time | Activity | Checkpoints | Notes |
|---|---|---|---|
| 22:00 | Shift handover | Gate | Read previous shift notes; confirm phone charged and torch working |
| 23:00 – 00:00 | Round 1 | All 14 points | Start time varied within the window |
| 00:00 – 01:00 | Gate duty | Gate | Late arrivals, deliveries, intercom |
| 01:00 – 02:00 | Round 2 | All 14 points | Basement levels checked first while attention is fresh |
| 02:00 – 03:00 | Gate duty | Gate | Quietest window; log any vehicle movement |
| 03:00 – 04:00 | Round 3 | All 14 points | Historically the highest-incidence window |
| 04:00 – 06:00 | Gate duty and early movement | Gate | Early departures, milk and newspaper entry |
| 06:00 | Handover | Gate | Exceptions and findings passed to the day supervisor |