InnerWeb
Skip to main content

Security patrol routes: checkpoints on the plant map

A security manager who wants to move patrols from paper into the system should know what the patrol module defines today and what is still a stage under development. Below are implementation notes: how to plan checkpoints and checklists before a route pilot, and what not to promise to the agency or to management.

4
stages of route preparation before a pilot
Source: implementation notes summary
100 m
approximate beacon spacing on plant roads
Source: InnerWeb facts

What the patrol module defines today

In the patrol module the plant defines checkpoints on the map, each with its own checklist, and puts them together into routes assigned to a department. This is a good foundation for organizing patrols that today live in a guard's paper logbook or in the head of the longest-serving employee on shift.

A checkpoint may be linked to a beacon, and a checklist item may require a signature, a location confirmation, a parameter or evidence in the form of a photo, video, audio or a file. For the guard this means it is possible to plan what to do and document at each checkpoint, for example a photo of a closed technical gate or a temperature reading from a thermometer.

What not to promise yet

The documentation describes defining checkpoints and patrol routes, while carrying out a patrol in the system, meaning the course of the route and enforcing the evidence, is an unfinished stage. We therefore do not describe patrols as a finished process. In implementation notes this is the key information: the plant can build the definitions and check them on the map, but should not assume that the system will already track the execution of each patrol shift after shift.

We recommend that in talks with the security agency and management you use phrases such as: we define routes, we prepare checklists, we plan a pilot. Avoid phrases that suggest the system holds the guard accountable for the patrol.

Scope of the patrol module: what exists and what is in progress (number of elements)

Scope of the patrol module: what exists and what is in progress (number of elements)Summary: three definition elements available, patrol execution still in progress0123elementsCheckpoints, lists, routes: 3 elements3Checkpoints, lists, routesPatrol execution: 0 elements0Patrol execution
Source: Patrol module function card: definitions available, patrol execution as an unfinished stage

Stages of preparation before a route pilot

A route pilot should be preceded by four stages, each ending with a document.

Stage 1: inventory of checkpoints

The security manager, together with the department manager, selects the checkpoints from the existing paper patrol. Each checkpoint receives a name, a place on the map and a responsible person on the plant side. Checkpoints that nobody can justify are dropped from the route.

Stage 2: checklist for each checkpoint

For each checkpoint the plant defines the checklist items: what to check, what answer to accept and whether evidence is required. A checkpoint can be shared between routes, and a checklist copied from another checkpoint becomes an independent copy, so a change to one does not change the other. This is useful, but it is easy to create an unintended difference: after copying a list, a fix in one checkpoint does not reach the other.

Stage 3: linking with beacons

A checkpoint may be linked to a beacon. The employee's position is calculated from the signals of several beacons and averaged on the map, so inside buildings about one beacon per 100 to 200 m2 is planned, and along plant roads about one every 100 m. Before linking a checkpoint to a beacon, check whether the plant has coverage at that place.

Stage 4: route for a department

The route is assigned to a department. The plant builds one route for one patrol and checks the order of checkpoints with the guard on the real route. The result of the check is a protocol with remarks, not an entry in the system as a completed patrol.

Pitfalls and notes for the security agency

The first pitfall is evidence: requiring a photo at every checkpoint lengthens the patrol. We recommend evidence only where it follows from risk, for example at checkpoints with locked technical doors. The second is too many checkpoints: a list of a dozen checkpoints in a patrol meant to last 30 minutes will not be completed. The third is diluted responsibility: a route assigned to a department does not say who from the agency performs it, so the split must be written down separately.

How to assess a route pilot

A pilot is assessed with three measures: the time of the patrol with the list compared with the paper patrol, the number of checkpoints where the list turned out to be unnecessary, and the number of checkpoints the guard could not find on the map. The result decides whether to shorten the route or keep it in its current form until full patrol execution is available.

Video

Frequently asked questions

Does the system check whether the guard completed the patrol?

Today we do not describe this as a finished process. Definitions of checkpoints, checklists and routes are available, and patrol execution is a stage in progress.

Does a checkpoint need a beacon?

No. It may be linked to a beacon, but it does not have to be.

Does changing a list in one checkpoint change it in another?

No. A list copied from another checkpoint is an independent copy.

Planning patrol routes?

We will show how to define checkpoints and lists on your plant map. Let's arrange a call before the pilot.

Let's talk