An empty post is a client complaint: how it shows up in security agencies and what to do

Picture a housing-society gate at 6 am. The night-guard has signed the visitor-register and is eyeing the boom-barrier. The day-guard has not turned up. A resident phones the committee secretary, who phones the agency owner. By 6.20 the owner is ringing a supervisor who is still asleep. That is how an empty post turns into a complaint.

The client does not care why. The contract sold a manned post. An unwatched turnstile, a visitor-slip pad lying blank and a delivery rider lifting the barrier himself are visible proof that the agency failed. This article follows that morning backwards to its causes and forwards to a fix.

• The day-guard rings at 5.45 am because the village bus never came, and the night-man is told to stay on.
• A double-duty runs past twelve hours, so the night-guard dozes on the stool beside the keybox.
• A reliever is pulled off a warehouse gate to fill the society gate, and the warehouse is short by noon.
• The post-order-book is stale, so the new guard does not know which gate-pass the client suspended last week.
• The supervisor marks the post covered by phone, and nobody checks the occurrence-book against the roster.

Each of these looks small. Together they explain most of the 2 am calls an owner takes. Notice how few concern the guard's character. They concern how the roster, the reliever-pool and the supervisor's beat were built.

The first cause is a late roster. Many agencies finish tomorrow's duty-chart at night, after the field-officer has met every supervisor. A guard who wants a weekly-off asks on the day itself. The second cause is a thin bench. The same four relievers serve thirty posts. When two go home for a wedding, the cluster has nobody.

The third cause is billing. Clients pay per post per shift, so an uncovered shift is lost revenue and a disputed invoice. Owners then push guards into double-duty rather than carry another reliever on the muster. That works for a month. Then the tired guard resigns and takes his friend from the lodging with him. The fourth cause is distance. Guards who share a bunk-room far from the site depend on one first-bus from one bus-stop, and that service is the one that fails on festival-eves or in a waterlogged monsoon week.

The direct cost is the penalty clause and the credit note against the invoice. The indirect cost is larger. A facility head who has photographed one empty gate starts walking the others at dawn with a torch and a checklist. The field-officer spends the week answering emails instead of training supervisors.

A relief-guard sent from the lodging-area needs the gate-pass list, the keybox code and a walk-through with the sentry he replaces. Without those, the dawn-round supervisor finds a stranger at the boom-barrier and writes it in the occurrence-book as an unknown face.

Inside the agency, a guard held back for a second shift without notice stops trusting the roster. Next time the supervisor asks, he says no. So the bench shrinks again.

1. 1

   Count the posts and the bench

   List every post, its shift pattern and the guards it needs per day, weekly-offs included. Then count the relievers. Many agencies aim for one reliever per five or six posts in a cluster, but set your own after the next two steps.

2. 2

   Close the roster the evening before

   Fix a cut-off, say 7 pm, after which no leave or swap is taken for the next day. The field-officer signs the duty-chart by 8 pm. Late changes need the owner's call.

3. 3

   Name a reliever-pool by cluster

   Give each cluster two or three named relievers who live nearby. Note their phone numbers and the posts they already know. A guard who has worked the gate before settles faster than a stranger.

4. 4

   Make the hand-over a signed one

   The outgoing-guard leaves only after the incoming-guard signs the register. If relief is fifteen minutes late, the supervisor is rung, not the owner.

5. 5

   Log every late or open post

   Use a plain sheet with date, post, shift, minutes open, reason and who was sent. Never hide entries. The log is the only way to spot patterns.

Date and day:
Client and post:
Shift (day, evening, night):
Guard expected and his lodging area:
Minutes the post stood open:
Reason (no-show, bus failure, sick, leave not planned):
Reliever sent and the post he left:
Occurrence book entry made (yes or no):
Client told by (supervisor or office) and at what time:
Follow-up action and owner:

The supervisor fills one line per incident. The field-officer reviews the sheet each Monday with the owner. Watch for the same post, the same lodging or the same supervisor appearing three times in a month. That is not luck. It is a design fault.

A supervisor cannot cover more posts than he can reach in a shift. Ask how long his bicycle or pillion round takes, and count the stops. If the answer is longer than the shift, split the beat. Give him a fixed night-round time so each sentry knows when to expect him.

The field-officer owns the log, the reliever list and the weekly review. He should not also own recruitment, or he will fill gaps with whoever walks in. Link hiring to the vacancy list. The recruitment process consulting page for event security firms shows how batches are planned.

Start with the roster cut-off and the open-post log. Both cost nothing and show the truth within a month. Then build the reliever-pool. The security agencies hub lists the other pressures in this trade, and the attendance, shift and leave process page explains how to record weekly-offs and swaps. If a gap keeps coming back, bring it to a requirements discussion and we can look at the roster together.