Skip to content

Running app-based patrols and checkpoint scanning

Run guard patrols in the ShiftTracker app: NFC, QR, GPS and photo checkpoints, deployed to your sites, reviewed by managers and shown to clients.

TW
Travis Wright

Content Lead

Published

10 Nov 2026

Updated

20 Nov 2026

Read

4 min

Empty corridor with polished floor and closed doors, lit by golden sunset light from a large window at the endIndustry Insights

Key takeaway

ShiftTracker runs patrols as forms in its app. Add a ready-made patrol form or build your own with NFC, QR, GPS, photo and timer checkpoints, deploy it to sites after each shift or on a schedule, and review every patrol with its times, locations and integrity flags before it reaches the client's scorecard.

ShiftTracker runs patrols as forms in its mobile app. You add a patrol form from the Template Library or build your own with checkpoint fields (NFC tag, QR code or barcode, GPS location, photo and timer), deploy it to the sites that need it, and officers complete it on their phone as they walk the route. Each scan and photo is saved with its time and, where switched on, its location. Every finished patrol goes to a manager for review, and patrols sent with a due time count towards the client's scorecard as patrols completed. This guide covers choosing a form, setting up checkpoints, deploying it, what the officer does, reviewing the evidence and reporting it to clients.

How do patrols work in ShiftTracker?

A patrol is a form with one checkpoint field for each point on the route. The same builder, deploy panel and review queue handle patrols, incident reports and site checks, so each client gets patrol evidence in the format its assignment instructions ask for, and your team learns one tool rather than several.

You do not have to start from a blank page. The Template Library includes a Security Patrol Log with barcode checkpoints and a Waking Watch Patrol Log with NFC checkpoints, plus a Keyholding Visit Report, a Vacant Property Inspection and a Lone Worker Check-In. Add & deploy makes a library form live at every site straight away, and Customise first copies it in as a draft so you can adapt it before anyone sees it.

Which checkpoint fields can a patrol form use?

  • NFC: the officer taps the phone on an NFC tag fixed at the checkpoint.

  • QR code and barcode: the camera reads a QR code or a common barcode, such as EAN, UPC, Code 39 or Code 93.

  • GPS location: records where the officer stood when the field was filled.

  • Photo, video and audio: evidence of the condition of each point.

  • Timer: records how long a task took.

Every field also has Geo Location and Time Stamp switches, so any answer can carry a position and a time. Field rules show follow-up questions only when they apply, for example asking for a photo and a description when an officer reports a fault, and scoring can flag a patrol that falls below a threshold. The form builder guide lists every field type.

How do you deploy a patrol to your sites?

Open the deploy panel from the library or from Templates. Under Where, choose All sites, which includes sites you add later, or pick sites one by one. Under When, choose Always available, After a shift (sent at the start or end of each shift, with an optional Due within in minutes), or On a schedule at set times each day.

Use After a shift or On a schedule for patrols that must happen, because those send the form to whoever is on shift with a due time. A patrol that is not returned in time shows under Overdue Tasks on Form Reports, and both the officer and the person who sent it are notified. The deploy forms guide covers each option.

What does the officer do on the phone?

The officer opens the patrol from Forms in the ShiftTracker app, scans each checkpoint and adds photos or notes where asked. A patrol can be completed with no signal: the app keeps it on the device and sends it when the phone reconnects, marked as completed on device, and an officer's offline report is accepted for up to seven days.

Patrols run alongside check calls rather than replacing them. Check calls confirm at set intervals that the officer is safe, a missed call alerts your control room until someone acknowledges it, and the press-and-hold Emergency button raises an alarm at once with no PIN. The check-call windows and escalation guide explains the timings.

How are patrol records reviewed?

Each submission arrives in the review queue with its site, officer, times and locations. A manager presses Start review, then Approve or Reject, and a note is needed to reject. Edit files a corrected version and keeps the original, so the history stays intact.

ShiftTracker also checks every submission for signs that the evidence is not what it seems: a mocked or missing GPS position, a position outside the site's geofence, a photo chosen from the gallery, a form filled too fast or one submitted off shift. Each submission is marked Clear, Needs review or Suspect, and a reviewer can dismiss or confirm each flag. Flags never reject a patrol on their own. The review form submissions guide explains each one.

How do clients see patrol evidence?

The client portal scorecard counts patrols completed: patrol forms sent and returned, against those that fell due. Approved reports appear in the client's portal, and a workflow rule can email the client a copy of each approved patrol. Submissions also export to CSV or Excel, up to 5,000 at a time, or as PDF files. The client portal scorecard guide shows what the client sees.

How do you set up your first patrol?

  1. Add the Security Patrol Log or Waking Watch Patrol Log from the Template Library, or build your own form.

  2. Fix an NFC tag or QR code at each checkpoint and give each one its own field.

  3. Deploy the form to the site After a shift or On a schedule, with a due time.

  4. Walk one patrol on site with an officer, then review the submission and its flags.

  5. Add a workflow rule to send approved patrols to the client.

Frequently asked questions

Does ShiftTracker support NFC checkpoints?
Yes. A patrol form can include an NFC field for each checkpoint, so the officer taps the phone on a tag fixed at that point. The scan is saved with its time, and with the officer's location where Geo Location is switched on. The Template Library's Waking Watch Patrol Log already uses NFC checkpoints.
Can officers scan QR codes instead of NFC tags?
Yes. The barcode field reads QR codes and common barcodes such as EAN, UPC, Code 39 and Code 93 with the phone's camera. The Template Library's Security Patrol Log uses barcode checkpoints.
Do patrols work without a mobile signal?
Yes. The app keeps a patrol on the device when there is no signal and sends it when the phone reconnects, marked as completed on device. An officer's offline report is accepted for up to seven days. Book-on and check calls need a connection.
What happens if a patrol is not completed on time?
A patrol sent after a shift or on a schedule has a due time. If it is not returned by then, it shows under Overdue Tasks on Form Reports, and both the officer and the person who sent it are notified. It also counts against patrols completed on the client's scorecard.
Can clients see patrol records?
Yes. Approved reports appear in the client's portal, the scorecard shows patrols completed against those due, and a workflow rule can email the client a copy of each approved patrol.

Sources

  1. ShiftTracker pricing
  2. Build a form (ShiftTracker docs)
  3. Review form submissions (ShiftTracker docs)
  4. Export reports and payroll files (ShiftTracker docs)
  5. Check-call windows and escalation (ShiftTracker docs)
TagsSecurityGuards
ShareLinkedInX (Twitter)

Stop managing shifts. Start covering them.

See ShiftTracker on your own rota — a 30-minute demo, no slide deck, just the product.