Before you start
Your facility must have the patrol module enabled, and your GateOps user must have the guard or security role. The patrol navigation item is limited to those roles, and it is omitted from the quick actions entirely when the facility’s patrol module is disabled.Open the Patrol screen
The Patrol screen lists the scheduled patrols assigned to you. Each card shows the route name, the scheduled date and time, and a Checkpoints count showing how many checkpoints are completed out of the total. The list refreshes every 30 seconds and supports pull-to-refresh. When no patrol is due, the screen shows No patrols due right now. A due patrol shows one of three actions depending on its state:- Start patrol when it is within its usable window and not yet started
- Continue patrol when it is already in progress
- Waiting for start window when it is outside its usable window
Start a patrol
Tap Start patrol on the due patrol you want to run. The button shows Starting… while the app requests the server to begin it. Starting is only allowed inside the patrol’s start and miss window. Before the window opens, the app reports that the route is not due yet and when you can start it. After the window expires, it reports that the patrol start window has expired. Starting within the allowed period puts the patrol in progress; starting after the scheduled time can mark it late.Scan checkpoints in order
On the Active Patrol screen, the primary action is Scan for the next pending checkpoint, named for that checkpoint. It opens the native QR scanner. Checkpoints must be scanned in order. Scanning the right checkpoint records it, shown as Checkpoint scanned or Recorded successfully. While a scan is being recorded the app shows Recording checkpoint… or Recording…, and the scan and evidence controls are disabled until it finishes. The Active Patrol screen shows the route name, checkpoint progress, elapsed time, expected duration, and start time, plus each checkpoint’s name, status, scan time, an outside-geofence indicator, and a photo indicator. It polls every 15 seconds and has a manual Refresh. If a scan fails, the app explains why: Invalid checkpoint QR code, Scan checkpoints in order (naming the next checkpoint to scan), All checkpoints already completed, Patrol is not in progress, or Patrol is assigned to another guard.Geofencing is a warning, not a block
Location is soft-checked rather than enforced. The app attempts to capture your location, but a scan can continue without coordinates when permission or location acquisition fails. A scan from outside the checkpoint’s radius is still accepted and returned with a warning titled Location check: the app reports the distance and allowed radius and confirms the QR is accepted, asking you to verify you are at the correct location. When no positive checkpoint radius is configured, the default radius is 75 meters.Add an evidence photo
Use Add evidence photo to attach a photo to a scan. The native chooser offers Take photo, Choose from gallery, and Cancel; a selected photo can be removed with Remove photo. The mobile screen permits one photo per scan. Permission and upload problems surface as messages:- Camera permission required / Enable camera access in Settings.
- Photo library permission required / Enable photo access in Settings.
- File exceeds maximum upload size of 10MB
- Session expired. Sign in again and retry.
- Upload service unavailable. Update the API and try again.
- Could not reach the upload service. Check your network connection and API URL.
- Photo upload failed. Try again.
Complete the patrol
Complete patrol appears only after every checkpoint is no longer pending. Tap it and confirm with Complete patrol (or Keep going to stay on the active patrol). While the request is submitting, the button shows Completing…. Completing marks the patrol as finished and records the compliance result for this shift. The server rejects a patrol that still has pending checkpoints with Complete all checkpoints before finishing the patrol. When it succeeds, the patrol’s final status is late if it exceeded the expected duration or any scan was late, and completed otherwise. The success screen shows Patrol complete with the status and duration, or the status with done.Scan a patrol QR from the general scanner
Patrol QR codes can also be recognized from the general scan screen. That path requires connectivity, since the scan must be logged for the shift. The result is Checkpoint recorded.What’s next
- See Create a patrol route for how admins configure routes and checkpoints.
- See Review patrol logs for how admins review scan evidence and compliance.