Guard Patrols

For each site, you create checkpoints with a name and type, either QR or NFC. The Cockpit prints the QR labels as a PDF, two per row, and can write directly to NFC tags in the browser.

Writing to NFC tags from the Cockpit only works in Chrome on Android. This is a limitation of the browser interface.

A checkpoint has no coordinates of its own and no secret. The tag only contains its identifier.

From the shift details, the checked-in security officer opens "Patrol / Check". It includes a full-screen scanner that remains open for multiple scans and a button for manual capture at each checkpoint. Progress appears as "x of y".

An accidental duplicate scan is detected. One tap produces exactly one entry.

The server always determines the assignment itself: the security officer's own assignment, status checked in, and a site matching the checkpoint's site. A checkpoint from another site is rejected. Entries can only be created, not changed or deleted. Every scan is included in the audit log.

Platform: QR and manual capture on iPhone and Android. NFC only on the iPhone.

This is the most important part of this chapter, so it is stated explicitly: a patrol scan is evidence of presence and process, not a tamper-proof seal. It proves that a security officer checked in at this site captured the checkpoint, including the order and times in which this happened.

Protection comes from binding the scan to the assignment: the security officer must be checked in at this exact site at the time of the scan. A checkpoint from another site is rejected. Every scan remains unchanged in the report, and entries cannot be changed or deleted.

In practice, this means: If you use the patrol as evidence of a contractually agreed service, combine it with time tracking and spot-check supervisory patrols. Reading more into the scan alone overestimates it.

One plan per site contains an ordered list of checkpoints and, optionally, a repeat interval in minutes and fixed times. Both can be combined. A patrol becomes due as soon as either condition applies.

The interval is at least 5 minutes. A patrol is never due immediately, only at the first full interval. A due patrol is reported promptly, not at the exact minute.

New plans are active, but the interval and fixed times are empty, so initially there are no reminders. There is no tolerance or grace period.

For each site, a traffic light shows the status. Behind it, each assignment displays "scanned of planned" with the time window and missing checkpoints.

The target includes all checkpoints from active plans that existed before the shift started. A plan created later therefore does not make old assignments look incomplete retroactively. Missing checkpoints are only shown after the shift is completed.

After the shift ends, a background process checks every worked assignment. If checkpoints are missing, the scheduling team receives the "Patrol missed" notification exactly once per assignment.

The mobile manager view for this is currently only available on the iPhone.

For each site, you can allow the customer to view the patrol report and create checkpoints. This is off by default.

Enabling access alone is not enough. The customer must also be linked to the site through an order or directly. Changing and deleting checkpoints and the QR PDF remain with the security company.