July 2026: Proof of Presence - More flexible patrol completion in DeadZone Android

What it is and why it matters

This update introduces two improvements designed to make patrol completion more flexible in Proof of Presence.

The first is Manual Patrol Completion, which allows Android users to complete a patrol without scanning every tag when operational circumstances prevent the patrol from being finished in full.

The second is a new Snap Patrol Tag option, which gives guards a third choice when scanning a tag that belongs to a scheduled patrol while they are already carrying out an active Snap Patrol. They can now add that swipe to the current Snap Patrol without having to start the scheduled patrol or record the swipe outside of any patrol.

Together, these updates help guards deal with real-world exceptions more effectively. They reduce the risk of patrols being left stuck in progress, make it easier to record ad-hoc activity accurately, and help preserve a more complete audit trail of what was actually done on site.

When to use this in Proof of Presence

These updates are useful when patrol routes cannot be completed exactly as planned, or when guards need more flexibility in how patrol activity is recorded.

They are particularly relevant if you:

• need a way to close patrols when some tags cannot be accessed or scanned

• want to avoid partially completed patrols remaining open indefinitely

• run Snap Patrols alongside scheduled patrol routes

• need guards to record ad-hoc tag scans without interrupting an active Snap Patrol

• want patrol records to reflect what happened operationally, even when the original route could not be followed in full

For example, Manual Patrol Completion is useful when a guard cannot access the remaining tags on a patrol but still needs to close the patrol with a record of what was completed. The Snap Patrol option is useful when a guard is already on a Snap Patrol and scans a tag that also belongs to a scheduled patrol, but only wants to log that swipe against the current Snap Patrol.

How it works at a high level

For Manual Patrol Completion, administrators can enable the setting in POP Patrol Settings. Once enabled, Android users can complete a patrol directly from the app without needing to scan every remaining tag. The patrol is then logged against the patrol record as normal, even though it was not completed through full tag scanning.

For the Snap Patrol Tag option, when a guard on an active Snap Patrol scans a tag that belongs to a scheduled patrol, they are now shown three choices:

• start the scheduled patrol

• record the swipe with no patrol association

• add the swipe to the current Snap Patrol only

Choosing “Add to Snap Patrol only” logs the swipe against the open Snap Patrol without triggering the scheduled patrol.

Together, these options give patrol teams more practical ways to manage incomplete routes and unexpected tag scans, while keeping patrol activity properly recorded within the app.

Best practice tips

To get the most value from these updates, we recommend the following:

Enable manual completion selectively
Only enable Manual Patrol Completion for roles where it is genuinely operationally appropriate, so flexibility does not undermine required patrol standards.

Capture reasons for incomplete patrols
Where possible, pair Manual Patrol Completion with a notes or reason field so there is a clear audit trail explaining why the patrol could not be finished through full scanning.

Train guards on the new Snap Patrol option
Make sure guard teams understand the difference between starting a scheduled patrol, recording an isolated swipe, and adding a swipe to an active Snap Patrol so they can choose the correct option in the moment.

Use Snap Patrols for ad-hoc coverage
The “Add to Snap Patrol only” option is best suited to ad-hoc checks and flexible coverage activity. Where compliance requires a full scheduled route, guards should still start the scheduled patrol formally.

Review patrol policy alongside rollout
Before enabling these features more broadly, check that your internal patrol procedures and audit expectations reflect how incomplete patrols and ad-hoc scans should be handled.