What a route and a schedule actually are
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 type | What the visit proves | Contact or RFID |
|---|---|---|
| Perimeter gate or fence line | The boundary was walked at the scheduled hour | Contact iButton (weatherproof) |
| Plant room or electrical panel | Equipment area was checked, not just the corridor | Contact iButton |
| Fire exit and stairwell | Escape route was clear and accessible | Contact iButton |
| Stockroom or loading dock | Goods area was visited and secured | RFID for hands-free rounds |
| Roof access and basement | Remote areas were not quietly skipped | Contact 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.
Set the interval and the rest window
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.
| Setting | What it controls | Example on a night shift |
|---|---|---|
| Interval | Duration of one full round | 90 minutes (22:00 to 23:30) |
| Rest window | Break before the next round starts | 30 minutes (23:30 to 00:00) |
| Start time | When the first round begins | 22:00 every night |
| Repeat | How the plan continues | Daily, 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.
- 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.
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.
Roll out, then tune with the first reports
- List the four building blocks: routes, guards, checkpoints and event codes.
- Walk each route once and time the full round with a stopwatch.
- Set the interval and rest window from that measured time; add rest days.
- Check that no two routes sharing a checkpoint have overlapping windows.
- Run one week, then read the report for missed rounds and repeated exception codes.
- Move or add checkpoints only where the report shows a blind spot.