What a route and a schedule actually are

Definition: A route is an ordered set of checkpoints a guard visits in one round. A patrol schedule is the rule that repeats that round across days and shifts. A guard tour system stores four things: routes, the guards assigned to them, the checkpoint locations, and the event codes a guard can record at each stop.

Most failed plans start as a map with dots on it. The dots are fine; the missing piece is the rule for when each round starts, how long one round takes, and what happens between rounds. Design the rule first, then attach the checkpoints.

The practical unit of design is the round: one guard, one route, one pass through every checkpoint, from the first stop back to the first stop. Everything else in the schedule is a repetition of that round.

Place checkpoints by risk, not by distance

A checkpoint is a proof-of-presence point, not a mileage marker. Put it where a missed visit would leave a real gap: an asset, a hazard, an entry point, or a place where a guard must make a decision.

Checkpoint typeWhat the visit provesContact or RFID
Perimeter gate or fence lineThe boundary was walked at the scheduled hourContact iButton (weatherproof)
Plant room or electrical panelEquipment area was checked, not just the corridorContact iButton
Fire exit and stairwellEscape route was clear and accessibleContact iButton
Stockroom or loading dockGoods area was visited and securedRFID for hands-free rounds
Roof access and basementRemote areas were not quietly skippedContact iButton

Start with five to ten high-risk points per route. Add more only when a report shows a blind spot. Checkpoints are passive and need no wiring, so moving one later is cheap.

Avoid placing two checkpoints within a few metres of each other. They add scanning time without adding proof.

Set the interval and the rest window

Definition: The interval is the time one complete round should take, from the first checkpoint back to the first checkpoint. The rest window is the break between the end of one round and the start of the next. The two are different settings and both belong in the plan.

Work the interval out from walking time: measure a real round with a stopwatch, add a few minutes for logging an exception, and round up. An interval shorter than the real walk forces guards to rush or to scan points out of order.

SettingWhat it controlsExample on a night shift
IntervalDuration of one full round90 minutes (22:00 to 23:30)
Rest windowBreak before the next round starts30 minutes (23:30 to 00:00)
Start timeWhen the first round begins22:00 every night
RepeatHow the plan continuesDaily, from start date onward, no end date

In a full-day pattern, an entry of 00:00 to 00:00 (next day) represents a whole day of rounds in a single line. It is the cleanest way to define continuous cover when the same rhythm applies every day.

One checkpoint can serve several routes, but time windows must not overlap

A single physical location often matters to more than one job. The main gate may be on the perimeter round and on the opening round. A guard tour system lets that checkpoint belong to several routes, so you install one button instead of three.

Definition: The no-overlap rule: when the same checkpoint appears in two routes, the time windows in which those routes run must not intersect. Otherwise one scan could satisfy two rounds at once, and the report can no longer prove that either round was really walked.
  • Assign the gate to the perimeter round at 22:00 and to the opening round at 06:00: no overlap, one button.
  • Do not put the same point on two routes that both run between 22:00 and 23:30.
  • If two shifts must check the same asset at the same hour, install a second checkpoint a few metres away and give each route its own.
  • When in doubt, check the schedule view: overlapping windows on a shared point are the most common cause of confusing reports.
Sharing points is a strength, not a shortcut. It keeps hardware counts low while each route still produces its own complete record.

Add rest days and let the plan repeat

Real patrol plans run from a start date onward and usually have no end date. Set the rhythm once and let the system generate each day. Then mark weekly rest days so the plan does not expect a round when the site is closed or the guard is off.

  • Set rest days by weekday, for example Sunday, and the plan skips that day automatically.
  • Rotate rest days among guards so coverage stays continuous.
  • If a holiday changes the pattern, create a separate plan for that date instead of deleting rounds from the normal one.
  • Keep the original plan intact; editing a repeating plan in place is how gaps appear.

Keep pass and fail simple

The scoring rule that survives contact with real shifts is simple: if the checkpoint was scanned, the visit counts as done. Strict sequence enforcement, tight late tolerances and complex grading produce plans that look rigorous on paper and fail in the field.

When guards know that one missed scan will not be treated the same as an honest exception, they record exceptions instead of working around the system. The data becomes more honest, not less.

Define an exception code for "could not reach this point" so a blocked checkpoint is reported rather than silently skipped.

Roll out, then tune with the first reports

  1. List the four building blocks: routes, guards, checkpoints and event codes.
  2. Walk each route once and time the full round with a stopwatch.
  3. Set the interval and rest window from that measured time; add rest days.
  4. Check that no two routes sharing a checkpoint have overlapping windows.
  5. Run one week, then read the report for missed rounds and repeated exception codes.
  6. Move or add checkpoints only where the report shows a blind spot.
A sealed, waterproof guard tour reader suited to outdoor perimeter and plant-room rounds.
A sealed, waterproof guard tour reader suited to outdoor perimeter and plant-room rounds.

FAQ

Start with five to ten high-risk points and time the round. If the walk takes longer than the interval you can realistically staff, split the route rather than adding pressure. Add points later only where reports show a gap.
Yes. Assign both guards to the route on different shifts and the system keeps their rounds separate in the report. What must not happen is two guards running overlapping rounds that use the same shared checkpoint.
The interval is how long one full round takes. The rest window is the break before the next round begins. Setting both prevents the back-to-back scheduling that causes rushed scans and missed points.