Skip to content
14-day free trial, no card9 languages176 business types · 50 apps
EN· USD
Try a live demoStart free trial

Guarding: sites, posts & checkpoints: how it works

«Guarding» holds the client sites your security company protects: each site is a field-service customer site with the contract rate per guard-hour, the standing orders, its guard posts (how many guards, which hours, which days) and its patrol checkpoints with a QR label each.

Lesson 1 of 9 · How it works

  • about 3 min
  • Field service → Guarding

How it works

  1. Add a site from an existing customer site (Field service → Sites) or create a new one with the customer, address, site contact and the rate per Guard-hour One guard on duty for one hour — the unit the contract rate is charged in. More words in the glossary.

  2. Each post says how many guards it needs and when: an end time before the start runs past midnight, the same time means 24 hours; a post may have its own rate.

  3. Checkpoints get a random 192-bit QR token; «QR labels» prints a label sheet to fix at the points. «New QR» replaces a lost or copied label (the old one stops working).

  4. A patrol route lists the checkpoints in walking order with a round every N minutes inside the patrol hours and the minutes one round may take.

  5. The list shows per site the posts, checkpoints, open incidents and today's patrol completion.

Where to find it

Settings that change it

Checklist

Before you move on, check that you can:

  • Open Field service → Guarding
  • Add a site from an existing customer site (Field service → Sites) or create a new one with the customer,…
  • Each post says how many guards it needs and when: an end time before the start runs past midnight, the same…
  • Checkpoints get a random 192-bit QR token; QR labels prints a label sheet to fix at the points.
  • A patrol route lists the checkpoints in walking order with a round every N minutes inside the patrol hours…

Tips and common mistakes

  • Give each checkpoint a clear name (Rear fence, Loading bay): it is what the guard sees after the scan.
  • Removing a checkpoint or post that has history switches it off instead, so old reports stay complete.