How to Reduce Missed Security Patrols: A Practical Guide for Supervisors

Missed patrols do not always mean that a guard has ignored a duty. A route may be unrealistic, a checkpoint may be badly placed, a device may not be available, or a control-room procedure may not make it clear what should happen next. The most useful response is to make the patrol easier to perform, easier to verify and easier to review.

For South African security company owners, control-room operators and supervisors, reducing missed patrols starts with practical planning: give the team a clear duty, a reliable record and a fair follow-up process.

Why can a security patrol be missed?

Patrols can be missed for ordinary operational reasons. A guard may be dealing with an incident, assisting a resident or customer, covering an urgent post, waiting for access, or working a route that takes longer than expected. Weather, poor lighting, construction work, a damaged checkpoint or an unavailable device can also affect the record.

Treat a missed checkpoint as an exception to investigate, not automatic proof of misconduct. Compare the patrol record with the guard's duties, control-room notes, communication history and other relevant information before deciding what happened.

Start with a clear schedule and sensible checkpoints

A patrol schedule should describe work that can realistically be completed during the shift. Set the route, expected sequence and timing around the site itself. A large industrial property, residential estate or shopping centre may need different routes for different posts or risk areas. Avoid schedules that leave no time for access delays, handovers or reasonable response work.

Checkpoint placement matters just as much. Place checkpoints where a guard is expected to pass as part of the patrol, not in a position that requires an unnecessary detour. Name them consistently so that the control room and supervisor understand the same location. Review points after site changes, because a gate, storeroom, plant room or public area may no longer be safe or practical to visit.

The Patrol Management Software South Africa guide explains how route planning, checkpoints, communication and reporting can fit together. It is a useful starting point when reviewing a patrol process rather than only the device used to record it.

Use NFC or RFID records for the job they can prove

Checkpoint technology is most useful when its evidence is understood correctly. The OG-66 Patrol Radio can scan NFC checkpoints on a configured patrol route. A scan can record the device, checkpoint, date and time, giving the team a specific patrol-point record to review.

The established MKIII patrol system uses RFID patrol points for structured guard-tour operations. It is a separate, established RFID-based system, not Onguard's newest flagship device. Both approaches can support patrol verification, but the devices, checkpoint technology and configured workflows should not be described as interchangeable.

An NFC or RFID record is evidence that the relevant device scanned the relevant point at a recorded time. It does not, by itself, describe everything that happened during the shift or prove that every part of a site was inspected. Keep that distinction clear when training guards and when explaining reports to clients.

What to do when a scheduled checkpoint is not recorded

When a scheduled checkpoint is missing, the control room should first record the exception and check the available context. Was the guard responding to an incident? Was the route blocked? Was the checkpoint damaged, moved or difficult to reach? Was the device allocated to the correct guard and operating as expected?

Follow the site's procedure: contact the guard or supervisor through the approved method, ask for a concise status update and record the explanation. If the point needs to be revisited, base that decision on the risk and circumstances rather than applying an automatic rule.

Avoid promising a guaranteed notification or response time unless the configured system and service arrangement actually support that claim. A record is valuable when it leads to a consistent, documented operational decision.

Keep guard-to-control-room communication reliable

Patrol verification and communication solve different problems. A checkpoint scan records a patrol event; communication lets a guard, supervisor and control room exchange information about what is happening. Make sure guards know which channel or method to use for routine updates, access problems, emergencies and handovers.

The OG-66 is the current main patrol radio for Onguard's connected patrol workflows, including cellular push-to-talk where supported network connectivity is available. It should not be presented as a replacement for every site procedure. Check coverage, charging, allocation, training and backup arrangements before relying on connected communication during a shift.

GPS context is different from checkpoint verification

GPS can provide wider movement and location context for a device. It may help a controller understand the general location associated with an event or investigate the sequence of activity. A checkpoint scan provides stronger evidence that the device reached and scanned a specific configured patrol point.

These records answer different questions. GPS context may help explain where a device was; an NFC or RFID scan may help verify that a named checkpoint was reached. Neither should be treated as a complete account of a guard's performance without the surrounding operational information.

Use Stay Awake acknowledgements as part of an alertness procedure

Stay Awake supports scheduled prompts, guard acknowledgement and missed-response alerts for alertness-monitoring procedures. The function is also available on the OG-66. Acknowledgement shows that a response was recorded to a configured prompt; it does not prove that a guard remained awake or attentive throughout an entire shift.

Supervisors should define when prompts are appropriate, who reviews a missed acknowledgement and how the result is recorded. Stay Awake is separate from patrol checkpoint verification and separate from cellular push-to-talk communication. Keeping those functions distinct helps the control room interpret each record correctly.

Review exception reports and improve the procedure

Look for patterns rather than isolated blame. Repeated misses at one point may indicate poor placement, access restrictions or a naming problem. Misses at the same time may reveal an unrealistic schedule or recurring handover. Exceptions associated with one device may justify a charging or maintenance check.

Review a sample of completed patrols as well as missed ones. Ask whether the route was completed in a sensible order, whether records were understandable to the client and whether supervisors had enough context to make a fair decision. Update the schedule, checkpoint layout, training or control-room instructions when the evidence points to a process problem.

Supervisor checklist

Before a patrol programme goes live, confirm:

• Each route has a clear purpose, realistic timing and named checkpoints.
• Checkpoints are safe, accessible and placed on the expected route.
• The correct device is allocated, charged and understood by the guard.
• The control room knows how to record and follow up a missing scan.
• Guards know the approved communication method for routine and urgent issues.
• GPS context is explained separately from NFC or RFID checkpoint evidence.
• Stay Awake prompts, where used, have an agreed acknowledgement procedure.
• Supervisors review exception patterns and adjust the process when needed.
• Client reports explain what the records show without overstating them.

Common questions

Does a missed checkpoint prove that a guard skipped a patrol?

No. It identifies an exception that should be checked against the route, site conditions, communication and other available records.

Is GPS enough to verify a patrol?

GPS provides wider location context. A configured NFC or RFID checkpoint scan is more specific evidence that a named point was reached and scanned.

Is the MKIII the same as the OG-66?

No. MKIII is an established RFID-based patrol system. The OG-66 is the current main patrol radio and uses NFC for its patrol-point workflows.

Does Stay Awake replace patrol monitoring?

No. It supports scheduled alertness acknowledgements and missed-response follow-up. It does not replace route planning, checkpoint verification or communication procedures.

What should a supervisor do first after a missed scan?

Record the exception, check the available context, contact the relevant guard or supervisor through the approved method and follow the site's documented procedure.

Reducing missed security patrols is a process-improvement task. Clear routes, well-placed checkpoints, reliable communication and fair exception reviews give supervisors better information and give guards a more workable duty to perform.