How to Handle Missed Security Guard Patrols: A Supervisor's Checklist

The short answer

When a security guard patrol or checkpoint is missed, treat it as an exception to investigate, not a conclusion. Review the timeline, check for incidents or legitimate interruptions, rule out connectivity and device problems, talk to the guard, document what you found, and then decide on follow-up that matches the cause.

A missed checkpoint does not automatically mean a guard failed to do their job. The cause may be an incident response, an operational interruption, an unclear procedure, a connectivity problem, a device issue, or an actual missed patrol. The supervisor's task is to work out which one it was.

What counts as a missed patrol or checkpoint

Definitions vary by contract and post orders, so write yours down. Many electronic patrol systems track each checkpoint against a patrol interval, such as every 60 minutes, rather than against fixed rounds. In that model, exceptions usually look like this:

• Overdue checkpoint: the interval has passed since the checkpoint was last logged, or it has not been visited yet this shift. It may still be logged late.
• Late check-in: the checkpoint was logged, but after its interval had passed.
• Long gap: the guard is on shift, but nothing has been logged for well over one interval.
• Missed checkpoint: an active checkpoint was never logged during the shift.
• Missed patrol: patrol was required, but the shift has no checkpoint check-ins at all.

Missed patrol vs. missing electronic record

Two different situations can look identical on a report:

• A missed patrol: the guard did not walk the round or did not reach the checkpoint.
• A missing record: the guard was there, but no check-in was captured. The tag was damaged, a beacon battery died, the phone was off or out of power, or the check-in had not yet synced.

The reverse is also true. A recorded check-in shows that a device registered at a checkpoint at a certain time. It does not describe everything the guard did or observed during the round.

The supervisor's checklist

1. Confirm what was required. Check the post orders: which checkpoints, what interval, and whether that round applied to this shift.
2. Review the timeline. Look at the check-ins before and after the gap, and at the guard's shift check-in and check-out.
3. Check for incidents and interruptions. Look for incident reports, calls, or instructions during the gap.
4. Rule out technical and connectivity issues. Consider signal, device, and checkpoint hardware.
5. Talk to the guard. Ask what happened before drawing a conclusion.
6. Document the patrol exception. Record the facts, the cause, and the evidence.
7. Decide appropriate follow-up. Match the response to the cause.
8. Look for recurring patterns. Compare this exception against earlier ones.

Review the timeline

Start with the facts on record. Was the guard checked in for the shift? Were the checkpoints before and after the gap logged on time? Did the guard attach patrol photos or notes during the gap? One missing stop in an otherwise complete round suggests something specific to that location. A long silence across every checkpoint suggests something happened to the guard, the device, or the shift itself.

Check for incidents or legitimate operational interruptions

Guards are on site to respond, and responding takes them off the route. Look for an incident report, an alarm, a medical call, a client request, an escort, a delivery, or a supervisor's instruction during the gap. Also check for access problems: a locked area, construction, weather, or a safety concern. A patrol delayed for a good reason should be recorded as exactly that.

Rule out technical and connectivity issues

• Connectivity: garages, basements, and stairwells often have no signal. Some systems store check-ins on the phone and send the patrol report later. Before calling a checkpoint missed, confirm that the report for that shift has actually arrived.
• Device: a dead battery, Bluetooth or NFC switched off, missing app permissions, or an outdated app.
• Checkpoint hardware: a beacon with a flat battery, a tag that was removed or painted over, a QR code that is torn or faded.

A quick test is to check when that checkpoint was last detected by any guard, and its battery reading if it is a beacon. If it has gone quiet for everyone, look at the hardware first.

Document the patrol exception

Write a short, factual record: site, checkpoint, date and time, guard on duty, what was required, what was recorded, the cause you found, the evidence you reviewed, and the action taken. Keep it neutral. "Checkpoint 4 not logged for the 02:00 round; guard was handling a reported break-in, incident report filed" is more useful than a judgment.

Decide appropriate follow-up

Follow-up should fit the cause:

• Incident or legitimate interruption: note it, and confirm the guard knows how to record a delayed round.
• Unclear procedure: fix the post orders and retrain.
• Technical problem: repair or replace the hardware, or sort out the device.
• Actual missed patrol: have a direct conversation, coach, and follow your company's performance policy.

If the contract requires it, tell the client what happened and what you did about it.

Identify recurring patterns

One exception is an event. Several point to a cause. Look for the same checkpoint failing for different guards, the same time of night, the same site, or the same guard across different sites. Each pattern suggests a different fix.

Three practical examples

Incident response. A guard misses the 01:00 round at an apartment complex. The timeline shows on-time rounds before and after, and an incident report filed at 01:10 for a vehicle break-in. Outcome: documented as an interruption, no performance action.

Hardware fault. The basement checkpoint at an office building is missed by three different guards over one week, while every other checkpoint is logged. It was last detected days ago and shows no battery reading. Outcome: the supervisor replaces the beacon battery, runs a test scan, and records the cause on each exception.

Actual missed patrol. A guard is checked in for the shift, but no checkpoints are logged for three hours, with no incident, no instruction, and no connectivity explanation. The guard confirms the rounds were not walked. Outcome: documented, and handled through coaching under company policy.

Improving patrol routes and procedures

Repeated exceptions often say more about the route than the guard. Review whether:

• the interval is realistic given the walking distance and the guard's other duties
• checkpoints are placed where guards can reach them safely at all hours
• post orders say what to do when a round is interrupted, and how to note it
• the check-in method suits each location
• new guards are walked through the route during site training

Electronic checkpoint verification: BLE, NFC, and QR

Electronic verification adds a timestamped record tied to a physical point on the site, which makes gaps visible sooner and reviews faster. The three common methods work differently:

• BLE beacons: the guard taps Check In near a small Bluetooth beacon, and the phone listens for it for a few seconds. The signal has to meet the checkpoint's sensitivity setting, but range still varies with placement and walls, so a detection means the phone was near the beacon, not at an exact spot. Beacons need battery checks.
• NFC tags: the guard taps the phone against a tag. This requires very close contact, needs no battery, and depends on the phone supporting NFC and the tag staying in place and undamaged.
• QR codes: the guard scans a printed code with the camera. Codes are inexpensive and easy to replace, but they can fade or tear, and a printed code can be copied, so placement and supporting controls matter.

All three record that a device registered a checkpoint at a certain time. None of them, alone, records what the guard checked or saw there. Systems that allow one check-in per checkpoint per interval show that the checkpoint was covered in that window, not how many times the guard passed it. They improve visibility, and they work best alongside incident reports, supervisor spot checks, and clear post orders.

How Secureburg fits

Secureburg is security guard management software built to scale with your business. Patrol checkpoints can use Bluetooth beacons, NFC tags, or printed QR codes, and each site has its own patrol interval. During a shift, guards see which checkpoints are due or overdue, and every check-in is timestamped. Patrols keep working without signal and sync once the phone reconnects. At the end of the shift, the patrol summary shows which checkpoints were covered and which were missed, and guards can attach photos with notes.

That gives a supervisor the timeline this checklist depends on. The judgment about why a checkpoint was missed still belongs to the supervisor. See the details on the Guard Patrol & Checkpoint Software page, browse all features, or contact us with questions about your sites.

Frequently asked questions