Security guard SOPs for the gate and the CCTV control room

By Gankya · 4 October 2026 · 5 min read

Good CCTV is mostly good habits. The best cameras on the market do little if nobody notices that one has been facing a wall for a week, or if footage of residents ends up on a guard's phone.

Below are practical standard operating procedures (SOPs) for the main gate and the control room at a large township, industrial park or campus. Adapt them to your site, translate them into the language your team reads best, and put them on the wall.

1. Shift handover

Most mistakes happen at handover. Make it a fixed ten-minute routine, done face to face, with both guards signing the register.

• Open incidents: what happened, what is pending, who has been informed.
• Vehicles still inside that should have left, such as contractor trucks or visitor cars past their expected time.
• Cameras that are down, blurry or blocked, and whether the vendor has been called.
• Any instructions from the supervisor or management for this shift.
• Keys, radios, registers and the control-room login handed over. Each guard logs out of their own account and the new guard logs in with theirs. Never share one login across shifts.

2. Camera health check

Do a quick check at the start of every shift, and a full check once a day, ideally once in daylight and once after dark.

• Live: every camera shows a picture, not a black or "no signal" tile.
• Recording: play back the last few minutes on a sample of cameras to confirm they are actually recording.
• View: nothing is blocking the lens, such as a tree branch, a new signboard, a spider web or a parked vehicle. The camera still points where it should.
• Clarity: the image is not foggy, dirty or out of focus. Number plates at the gate can be read.
• Night: after dark, the infrared light works and headlight glare does not wash out the gate cameras.
• Time: the time shown on the recorder matches a phone's clock to within a minute.

Write every problem in the camera log with time, camera name and what is wrong. A camera that is broken for a week without a log entry is a management problem, not just a technical one.

3. Visitor vehicles at the gate

A clear routine protects residents and also protects the guard from blame.

1. Stop the vehicle at the barrier, not inside the gate.
2. Note the number plate exactly as shown. Read it twice. Watch for look-alike characters such as 0 and O, 1 and I, 8 and B.
3. Confirm the visit with the resident, tenant or host through the intercom or app before opening.
4. Record: number, vehicle type and colour, driver name, host flat or unit, purpose, number of people, time in.
5. Give parking directions and, where your site uses them, a visitor pass to be returned at exit.
6. At exit, record the time out and collect the pass. A missing exit time is the first clue in many incidents.

Collect only what you need. Asking for and noting an ID may be your site's policy; photographing every visitor's ID card on a personal phone should not be.

4. Handling alerts

Whether alerts come from a recorder, a software system or a phone call, handle them the same way:

1. Acknowledge the alert so others know someone is on it.
2. Look: check the live camera and the last few minutes of recording.
3. Decide: is this real, a false alarm, or unclear?
4. Act: send a guard to check, call the supervisor, or close it with a reason.
5. Record: write what you saw and what you did, with times.

An alert closed with "checked, OK" and nothing else is not useful later. Write one plain line, for example: "Gate 2 camera showed delivery van waiting for return pass; spoke to driver; left at 14:20."

5. Escalation

Every guard should know, without searching, whom to call and when. Keep a printed escalation chart at each post.

Fill in real names and numbers for your site. Update the chart whenever staff change.

6. Privacy do's and don'ts

Guards see a lot. Residents trust the security team only if that trust is respected. India's Digital Personal Data Protection Act, 2023 also expects organisations to control access to personal data, which includes CCTV footage.

Do

• Use your own login, and log out when you leave the desk.
• Look at footage only for a security reason, and note the reason.
• Keep control-room screens out of view of visitors and passers-by.
• Export footage only when a supervisor approves, and record who took it.
• Report any leak or misuse you notice, even by a colleague.

Don't

• Don't film the monitor with your phone or forward clips on WhatsApp.
• Don't look up residents, staff or visitors out of curiosity.
• Don't share footage with a resident directly. Send requests to the supervisor or management.
• Don't discuss what you saw on camera with other residents or staff.
• Don't move or tilt cameras to look into homes, windows or private spaces.

7. Training and review

• Walk new guards through these SOPs on their first day, at the gate and in the control room.
• Run a short refresher every month using a real (or practice) incident.
• Supervisors check the registers and camera log weekly and sign them.
• Management reviews footage access once a month: who viewed what, and why.

Gankya supports several of these habits directly: personal logins with roles for guards, investigators and admins; idle screens that sign themselves out, with a gate screen that stays on for the guard's shift; camera-offline alerts; alerts that explain why they fired, on screen and, if the site chooses, by e-mail; a Hindi mode for guard screens; and a reason for every search, recorded in a tamper-evident audit log. To try it at your site, ask about a 30-day pilot.