QR Code Patrol Checkpoints: Set Up a Guard Route in One Hour
QR code patrol checkpoints are printed QR labels fixed at the points a guard must visit, and the patrol is recorded from the guard's phone: a timestamp, a GPS position and a photo of the label and the object behind it, checked by AI against a reference image. No reader wand, no RFID tags, no docking station.
The reason a small security firm looks at this is usually very practical: a new client site starts on Monday, the contract says "hourly patrols with a log", and there is no budget or time to install tags and hand out readers. In the comparison of guard tour software and hardware checkpoints we covered why phone-based patrols win for firms with several ordinary sites. This article is the practical part: how to set up a QR code patrol route for one site in about an hour, what to put at each point, and how to make sure a missed point is noticed while the shift is still running.
How a QR code patrol works without a reader
A QR code is just a printed pattern that is cheap to make, easy to see in a photo and hard to confuse with another one. In a hardware system the code would be scanned by a dedicated device. In a phone-based system the code plays a simpler role: it is a visible, unique marker that the guard photographs together with what they are supposed to check. The proof of the visit is the record the phone creates at that moment.
In CosaNostra each checkpoint is a task with a location attached and, if you want proof of state, a reference photo. The guard opens the task at the point, the app records the GPS position and the time, the guard takes a photo, and AI compares the photo with the reference: the QR label in the frame confirms which point it is, and the object in the frame (a closed gate, a padlock, a fire exit) confirms its state. A score below the threshold you set flags the task, and the supervisor gets a notification the same minute.
This is why the label matters even without a scanner. A photo of "some corridor" can be argued about. A photo with the label "Checkpoint 07 — East fire exit" in the corner cannot.
What the guard actually does at each point
The routine has to be short enough to survive a cold night shift. Reach the point, open the task in the calendar, take one photo that includes the label and the object, tap done. Three actions, under thirty seconds. If the guard needs to report something at the point, they dictate it: "padlock on the side gate is missing, photo attached", and the voice assistant turns that into a task with time, location and the photo.
Set up a QR code patrol route in one hour
The plan below is written for one site with 10–20 checkpoints. It assumes a supervisor with a phone, a printer and a roll of clear tape. Before you start, read how AI photo verification proves a patrol checkpoint was actually visited, because the reference photos you take in step 3 are what the AI will compare against.
Walk the route with the client (15 minutes). Agree on the points the client actually cares about: gates, loading doors, server room door, fuel storage, the corner where the previous incident happened. Ten to twenty points is normal. More than that and guards start skipping.
Print and fix the labels (10 minutes). Generate one QR code per point with a short readable name under it ("CP 03 — Loading dock"). Print on plain paper, laminate or cover with tape, and fix it at eye level, one metre from the object it refers to, where it is lit at night. Do not put labels where they will be painted over or hidden by a parked truck.
Take the reference photos (15 minutes). Stand where the guard will stand and photograph the label and the object in its correct state: gate closed, lock on, lights off. This is the reference image for the checkpoint. Add a one-line description of what the AI should see ("chain and padlock on the gate").
Create the route in the app (15 minutes). One recurring task per checkpoint, with the location, the reference photo, the description, the threshold and the interval the contract requires: every hour, every two hours, twice a night. Assign the tasks to the shift, not to a named guard, so whoever is on duty tonight, including a replacement, gets the same route.
Do a test lap yourself (5 minutes). Complete each task once from the guard's position. Any point where the AI flags a correct photo needs a better angle or a clearer description before the first real shift.
That is the whole setup. Adding the next site is the same hour again, without a site visit by an installer.
Patrol intervals and missed checkpoints
The part clients pay for is not the photo, it is the guarantee that the round happens on time. Two settings do most of the work here.
Interval as a recurring schedule
Set each checkpoint as a task that repeats at the agreed interval inside the shift window. A round every two hours between 22:00 and 06:00 is four occurrences of every checkpoint per night. The guard sees them in the day view as a list that empties as the night goes on; the supervisor sees the same list from home.
What happens when a point is skipped
An occurrence that is not completed by its time becomes overdue. Overdue is visible: on the supervisor's calendar, in the notification on their phone, and later in the history of the site. There is no "the reader was not docked" gap. If the guard completed the task but the photo did not match the reference, the task is flagged and you have both the photo and the score to look at. Both cases are caught during the shift, which is the only time a skipped patrol can still be fixed.
Common mistakes with QR code patrol checkpoints
Labels in the dark. A code that is unreadable in the photo defeats the purpose. Put it where there is light, or move the light.
Too many points. Twenty-five checkpoints every hour is not a patrol, it is a treadmill. Ask the client which points are for security and which are habit.
Reference photos taken in daylight for a night route. The AI compares what it sees with what it was shown. Take the reference in the conditions the guard will work in.
Assigning routes to people instead of shifts. When the named guard swaps a shift, the route stays with him and nobody on site sees it. Assign to the shift.
Nobody reviews the flags. The first week produces false flags while angles settle. Someone has to look at them each morning and adjust, otherwise guards learn that flags do not matter.
What the client receives
Instead of a printout of scanned tag IDs, the client gets a history of the site: each checkpoint, each occurrence, time, position, photo and result. A disputed night is answered by opening that night. A month is answered by exporting the history for the period. And because the same app holds the shift schedule and incident reports, the patrol record sits next to who was on duty and what they reported, not in a separate system that only the office can open.
For a small firm this is the practical meaning of a QR code patrol: a printer, an hour on site, and a route that any guard on tonight's shift can walk with proof at every point. CosaNostra is built for exactly this kind of field team: patrol routes as recurring tasks, GPS check-ins, AI photo checks against a reference, instant alerts on missed points, and shifts and incidents in the same calendar. See how the full setup works for security companies on the CosaNostra guard tour system page.
Frequently asked questions
What is a QR code patrol?
A QR code patrol is a guard round where each checkpoint is marked with a printed QR label and the visit is recorded from the guard's phone: time, GPS position and a photo of the label and the object. In CosaNostra the photo is compared by AI with a reference image, so the record proves both presence and the state of the point.
Do the guards need a scanner or a special reader?
No. The label is photographed as part of the checkpoint photo, and the phone records the location and time. There is no reader to buy, dock or lose.
How do I know a checkpoint was missed during the shift?
Each checkpoint occurrence has a due time. If it is not completed by then, it becomes overdue on the supervisor's calendar and a notification is sent, while the shift is still running. A completed task whose photo does not match the reference is flagged with the photo and the score attached.
How long does it take to set up a new site?
About an hour for 10–20 checkpoints: agree the points with the client, print and fix the labels, take reference photos, create the recurring tasks assigned to the shift, and walk one test lap. No installer visit is needed.
