Every patrol, verified. Keep every patrol in view.

Connect checkpoints, patrol routes, and guard records so supervisors can review what happened at each site.

Attlock · Guard Tour System
Attlock Patrols

Evening exterior patrol · Harbour Centre · 18:00–18:47

3 of 4 scanned · 41m active · 6m paused

  1. Loading bay

    Dock 2 · 18:04

    First scan
  2. Main entrance

    Lobby · 18:12 · +8m

    On time
  3. Service door

    East side · 18:39 · +27m

    Late
  4. Parking exit

    Level P1 · No scan recorded

    Missed
  • On time
  • Late
  • Missed

Joins checkpoints in route order. Not a GPS trace.

Start with the site. Set the checkpoints, expected order, and instructions that make a route clear before a guard starts.

Site
Harbour Centre
Route
Evening exterior patrol
Checkpoints
Loading bay · Main entrance · Service door · Parking exit

Keep proof with the exception. Review missed scans, timing, and route context together instead of rebuilding the story from calls and notes.

Record
Checkpoint scan history
Exception
Missed checkpoint stays visible
Next step
Supervisor review

Time every round. Each tour runs as its own session with pauses tracked, so supervisors see active time rather than just a start and a finish.

A completed patrol round whose active time is below the configured minimum, flagged for supervisor review.
Attlock Guard Tour

Evening exterior patrol

Round 2 · Jordan Lee · Harbour Centre

Flagged

Bar: active time on a 0–40 min scale. Line: the 25 min minimum.

Active time
19 min
Paused
4 min
Expected round
40 min
Minimum round
25 min
Under the minimum4 of 4 scanned

Supervisors are alerted when a round finishes under its minimum, runs well over its expected time, or leaves stops unscanned. A flag prompts review; it does not prove a stop was missed.

Check where the scan happened. Where a checkpoint has coordinates, a scan from outside its radius is declined with the distance, and the guard moves closer and tries again.

Two scan attempts at the Loading bay checkpoint: one declined outside the allowed radius and one recorded inside it.
Attlock Guard Tour

Loading bay

QR code · Allowed radius 100 m

Radius check on
  1. 142 m away

    Declined

    18:03 · Too far from the checkpoint. Move closer and try again.

  2. 38 m away

    Recorded

    18:04 · Scan added to the round with its location.

Bars use a 0–150 m scale; the line marks the radius. The check applies where the checkpoint has coordinates and the device shares its location, and accuracy depends on the device and signal.

Ask the right questions at the stop. Attach a short form to a stop with choices, numbers, notes, photos, documents, or a signature, plus follow-up questions that appear when an answer calls for them.

A completed checkpoint form submitted with a scan at the Service door, including a follow-up question shown after a No answer.
Attlock Guard Tour

Door and lock check

Service door · Submitted with the 18:39 scan

Submitted
Is the door secured?Yes / No · Required
No
Describe the issueShown after “No”
Latch does not catch.
Lock conditionChoice
Worn
PhotoRequired
1 photo attached
Guard signatureSignature
Signed

Forms can also ask for numbers, notes, and documents. Availability depends on the form attached to the checkpoint and the enabled mobile workflow.

Record why a stop was skipped. A skipped checkpoint needs a reason and alerts supervisors, and a round with unscanned stops cannot close without an explanation.

A skipped Parking exit checkpoint with its recorded reason, followed by a round closed with an explanatory note.
Attlock Guard Tour

Parking exit

NFC tag · Evening exterior patrol

Skipped
  1. Stop skipped18:44

    Reason: vehicle gate blocked by a delivery truck.

    Supervisors notified.

  2. Round closed with a note18:46

    3 of 4 stops scanned. An explanation is required to close a round with unscanned stops.

A skipped stop stays on the record with its reason. It is not counted as a completed scan.

Catch a missed stop while the round runs. Set a scan window and grace period for the site. Guards get a due-soon reminder and a missed alert, and supervisors can be alerted when the site is set to escalate.

The reminder and missed-checkpoint alerts for the Parking exit checkpoint during a running round.
Attlock Guard Tour

Parking exit

Scan window closes 18:45

Auto alert on
Grace period
10 min
Alert check
Every 5 min
  1. Due-soon reminder18:40

    Guard notified: scan Parking exit by 18:45.

  2. Scan window closed18:45

    No scan recorded. The grace period begins.

  3. Missed-checkpoint alert18:55

    Guard notified. Supervisors are alerted when the site is set to escalate missed checkpoints.

Alerts need a scan window on the checkpoint and automatic alerts enabled for the site. Delivery depends on account, device, and connection settings.

Review rounds across the site. Compare scan compliance by guard, see the QR and NFC mix, and export session records to CSV or PDF.

Illustrative scan compliance by guard, the QR and NFC scan mix, and the available session exports.
Attlock Guard Tour

Scan compliance

Last 7 days · All sites

Illustrative values
  • Alex Morgan96%
  • Sam Rivera88%
  • Jordan Lee81%

Scan method

QR code · 58%NFC · 42%
Export sessionsCSV · PDF

Checkpoint scans support patrol review. They do not guarantee a guard's identity, prevent every missed scan, or replace company supervision.

Continue the workflow.

Move from this overview into the connected workflow where ownership, permissions, and review remain explicit.

Explore Post Orders

Questions about Guard Tour System.

What to know about getting started, supporting your team, and running your sites.

Talk to our team

A scan adds checkpoint and time context to a patrol record. It does not independently establish identity or prevent every false scan.

Run your security team in one place.

Schedule shifts, track patrols, and share reports.