Skip to main content

Set up patrols: routes, tags and patrollers

A patrol is a route of checkpoints (tags) walked with a patrol device (patroller). Setting up patrols means declaring the devices, registering the tags, composing the routes — and using the learning mode to capture a route by simply walking it.

Declare the patrollers

  1. Open Hamilton Security and click Administration in the left menu.

  2. In the Patrols section, click "Patrollers management": declare each patrol device (reader) used on the site.

Register the tags

  1. In the Patrols section, click "Patrol tags management".

  2. Register each checkpoint tag with its identifier, site and type. Tags are the physical badges or beacons fixed along the routes.

"Patrol keywords management" maintains the keywords that can be scanned during rounds to qualify observations.

Compose a patrol route

  1. In the Patrols section, click "Patrols management" and open or add a route — "Edition of a patrol":

    • Site (mandatory), Patrol name (mandatory).

    • Number (mandatory and unique — "The number is already used" otherwise).

    • Tags: filter the available tags by site and type, then move them into "Selected choices" and order them — the expected scan sequence.

  2. Validate.

Capture a route with the learning mode

Instead of composing manually, record a real walk:

  1. In the Patrols section, click "Learning mode". The warning reminds you: "Make sure all patrols in progress are finished".

  2. Select the Base and the Patroller, then walk the route scanning each tag in order.

  3. Back at the station, download the patroller's data with the device button, review the captured checkpoints, and Validate to turn them into the patrol route. The Delete action clears wrong captures.

Verify

Have an agent walk the patrol: the patrol appears in the Patrols screen with its checkpoints, timing and any missed tags — see "Review patrol activity" in the user guides.

Good to know

  • The "Clear patrol checkpoints in progress" right (rights groups) controls who may purge a device mid-round.

  • Patrol counts and average durations feed the statistics dashboards.

Did this answer your question?