What a guard tour report actually shows

Definition: A guard tour report is a structured set of scan records showing which checkpoints were read, by which guard, and at what time. A raw log tells you a reader was used; a report tells you what the patrol proved.

Each time a guard touches an iButton checkpoint or reads an RFID tag, the reader stores the checkpoint ID, the guard ID and a timestamp. On its own that is one line of data. Grouped into a report, those lines become evidence of a complete or incomplete round.

The useful question is never how many scans were recorded, but which expected visits did not happen. A system with thousands of scans and no way to flag a missing one is collecting data, not producing a report.

A checkpoint is proof that a specific risk was checked, not a distance marker. A report is useful only when each point stands for something worth verifying.

The report types worth running

One set of scan data can produce several reports. Run the one that answers the question in front of you instead of printing everything.

ReportQuestion it answersWho uses it
Round-by-round timelineWas every checkpoint on the route visited, in order and on time?Shift supervisors
Missed checkpoint reportWhich expected visits did not happen?Managers coaching guards
Exception reportWhat faults or blocked exits were logged, and were they cleared?Site managers
Per-guard shift summaryWhich guard worked which round, and what did they record?Operations teams
Audit exportCan an outside auditor reconstruct a month of patrols?Clients and auditors

Most teams start with the timeline and the missed-point report. Add the others only when someone asks a question those two cannot answer.

Do not confuse an exception with a missed point. A missed point means the guard never reached the checkpoint; an exception means the guard reached it and logged a problem there.

How to spot a missed round in the data

A missed round is rarely obvious in a long log. Use the same short check every time so nobody has to read thousands of lines.

Definition: A missed checkpoint is a planned visit with no matching scan in the reporting window. A late visit has a scan, but outside the expected time window.
  1. Set the reporting period to one week and look at one route at a time.
  2. Open the missed checkpoint report and sort by checkpoint, not by guard.
  3. Mark any checkpoint missed more than twice — that is a pattern, not a one-off.
  4. Compare those points with the planned round times to see whether the round was rushed or started late.
  5. Check the timeline for that date to confirm whether the guard was present but skipped the point, or never ran the round at all.
  6. Write one sentence describing the cause before changing anything in the software.
A guard who scans every point twenty minutes late has completed a late round, not a missed one. Keep the two separate or the report will overstate the problem.

Read the pattern before you blame the person

When the same point keeps appearing in the missed report, the cause is usually in the setup. Guards skip points they cannot reach comfortably or do not recognise as checkpoints.

  • Same checkpoint across all guards: the point is probably hard to reach, hidden, or mounted somewhere awkward.
  • Same guard across many checkpoints: a training issue, or a guard who has not understood the round.
  • Same hour every night: the round is scheduled at a time that collides with a shift change or a locked area.
  • Same point only in wet weather: the checkpoint may be exposed and unreliable to read.

Fix the physical cause first. Moving one checkpoint or adjusting a round time usually clears a pattern that no amount of reminders will.

Give each reader the report they need

A manager, a client and an auditor look for different things in the same data. Sending everyone the full export helps nobody.

  • Shift supervisor: today's missed points and exceptions, as a short daily list.
  • Operations manager: patterns across guards, routes and weeks, as a weekly summary with trends.
  • Client or tenant: proof that their area was covered, filtered to their zone only.
  • Auditor or insurer: a complete, dated record with guard IDs and timestamps that can be reconstructed.

Filter by zone before you send. A tenant only needs the rounds that touch their premises; giving them the whole site report raises questions you do not need to answer.

A 20-minute weekly review routine

  1. Pull the missed checkpoint report for the past seven days.
  2. Circle any point that appears three or more times.
  3. Ask the guard on that route what happens at that point — reach, light, access, or reading.
  4. Decide one change: move a point, adjust a round time, or coach a guard. Do not change everything at once.
  5. Note the change so next week shows whether it worked.
  6. Send a filtered zone report to clients who ask for proof, not the full log.

Would you like our product datasheet and price list?

A guard tour reader carried on patrol — the source of the scan data behind every report.
A guard tour reader carried on patrol — the source of the scan data behind every report.

FAQ

At minimum: the checkpoint ID and location, the guard ID, the timestamp, and a flag for any expected visit that did not happen. A report without a missed-visit flag makes you read every line manually.
A missed checkpoint has no scan in the reporting window. A late checkpoint has a scan, but outside the expected time window. Keep them in separate columns — mixing them exaggerates the problem and hides real gaps.
Once a week is enough for most sites, plus a same-day look at missed points after an incident. Review with the guards rather than only after a complaint; the first two weeks usually reveal every setup problem.