Checkpoint verification
Identify checkpoints from the tag's hardware UID and combine it with time and location evidence for stronger field verification.
Patrol Guard helps security teams plan rounds, prove checkpoint visits with NFC and location evidence, work through poor connectivity, and turn field activity into an auditable operational record.
Give guards a focused field workflow and give operations teams a clear, shared view of what actually happened.
Identify checkpoints from the tag's hardware UID and combine it with time and location evidence for stronger field verification.
Keep recording patrol activity when connectivity drops. The mobile outbox queues events and synchronizes them when the network returns.
Create recurring or one-time patrols, assign guards and supervisors, and classify rounds as upcoming, on time, late, overdue, or missed.
Record incidents from the field, manage their lifecycle, and escalate unacknowledged emergencies through configured operational channels.
Review patrol progress, validation results, synchronization health, incident activity, and exportable operational reports.
Each organization can connect and control its own Google Sheet. Guards and other organizations cannot manage that connection.
An organization administrator defines sites, zones, NFC checkpoints, patrol templates, schedules, users, and assignments.
The guard starts an assigned round, scans checkpoints, captures location, and records incidents-even when the device is offline.
Supervisors monitor progress, investigate exceptions, acknowledge incidents, and use the audit trail and reports for follow-up.
Role-based access keeps each person focused on the information and actions they need.
Patrol Guard separates organizations at the application and storage layers. Google Sheets access is routed through the backend so provider credentials are never placed in the Android or web client.
Read the Privacy PolicyEach organization can authorize a different spreadsheet through its own administrator.
Google refresh tokens are designed to remain encrypted in the backend control plane.
Administrative, supervisory, guard, and audit capabilities are separated by access policy.
Patrol scans and security audit events use append-only records and server-side validation.
No. The intended production model is one spreadsheet per organization. An authorized organization administrator connects the organization's Google account, and its users share that organization's data according to their roles.
No. Connection management is restricted to an organization administrator or an authorized platform super administrator. Guards, supervisors, and auditors cannot manage provider credentials.
Yes. The mobile workflow is designed to record eligible patrol events locally and place them in a synchronization outbox. Server validation remains authoritative after the connection returns.
The primary identifier is the NFC tag hardware UID. A patrol event can also include timestamp, device sequence, location evidence, checkpoint policy results, and synchronization metadata.
No. NFC and field location capture are intended for the Android and iOS guard applications. The web interface is focused on administration, monitoring, reporting, and configuration.