The guard tour software industry has a quiet recurrent problem: the wrong checkpoint technology gets installed for the environment. The result is a service that works in demo and slowly degrades over 18 months as tags fade, batteries die, and patrols start «forgetting» to scan because the hardware fails too often.
We have aggregated deployment data from 40+ sites across security companies in Europe and Latin America to build a decision matrix between the three current options for guard tour checkpoints in 2026. The objective is not to declare a winner. It is to match each technology to the environment where it actually performs.
The three technologies in one paragraph
QR codes are printed visual codes scanned by the phone camera. Cheap (cents per tag), easy to print and replace, but require visibility and decent lighting. NFC uses passive RFID tags scanned by phone proximity (less than 4 cm). Slightly more expensive (0.30 to 1.50 € per tag) but works in the dark, no camera needed, hard to fake by photo. Bluetooth beacons broadcast a unique ID on a configurable range (3-30 meters). Most expensive (15-40 € per beacon, requires battery replacement), but the scan is automatic when the patrol walks within range.
Decision matrix by environment
| Environment | QR | NFC | Bluetooth | Recommendation | |---|---|---|---|---| | Office building, indoor, well-lit | ✓ | ✓ | △ | QR (cheap, easy) | | Industrial plant, outdoor with sun exposure | △ | ✓ | ✓ | NFC (QR fades) | | Cold storage, freezer, below -10°C | ✗ | △ | △ | NFC with cold-resistant tags | | Hospital, sterile zone | △ | ✓ | △ | NFC (no photo of QR allowed in some zones) | | Ferry / ship below deck | ✗ | ✓ | ✓ | NFC primary, Bluetooth secondary | | Hotel corridors with low light | △ | ✓ | ✓ | NFC | | Outdoor perimeter with weather exposure | △ | ✓ | △ | NFC with industrial tags | | Stadium / large venue | △ | △ | ✓ | Bluetooth (cover large areas) | | Construction site | △ | △ | △ | QR for rapid setup, NFC for permanent | | Data center (RF restrictions) | ✓ | △ | ✗ | QR (RF policies vary) | | Underground parking | △ | ✓ | ✓ | NFC (no GPS, no camera light issues) | | Pharma cleanroom | △ | ✓ | ✗ | NFC with chemical-resistant encapsulation |
✓ = recommended ; △ = workable with caveats ; ✗ = not recommended.
The real costs over 18 months
Hardware cost is a fraction of total cost. The breakdown for a typical site with 50 checkpoints over 18 months:
| Item | QR | NFC | Bluetooth | |---|---:|---:|---:| | Initial hardware (50 checkpoints) | 25-75 € | 30-75 € | 750-2 000 € | | Tag replacement rate (per year) | 15-30% | 2-8% | 5-15% (battery) | | Replacement cost over 18 months | 60-200 € | 20-60 € | 100-450 € | | Installation labor (initial) | low | low | medium | | Maintenance labor (per quarter) | medium-high | low | medium | | Total 18-month TCO (estimated) | 200-500 € | 80-180 € | 1 000-3 000 € |
NFC has the lowest 18-month TCO for typical guard tour deployments. QR seems cheaper upfront but the replacement rate kills the budget. Bluetooth costs significantly more upfront but offers automatic scanning (no patrol officer interaction needed for the scan itself).
QR — when it makes sense
The right environments for QR:
- Office buildings with stable lighting and predictable patrol patterns
- Sites where you need to deploy quickly (a printable label takes 5 minutes)
- Sites where you need to change frequently (renovations, temporary events)
- Budget-constrained pilots where you want to prove value before investing in NFC
The risks of QR:
- Fading under UV exposure: outdoor QR labels degrade in 6-12 months. Indoor near windows: 12-18 months.
- Easy to photograph and replay: requires strict geofencing to prevent fraud (a photo of the QR scanned from the office is otherwise indistinguishable from an in-place scan).
- Camera-dependent: requires functional camera, decent ambient light, and patrol officer who can find the tag visually.
QR is fine for the pilot phase or for sites with low fraud risk and stable conditions. It is not the right choice for mission-critical permanent deployments.
NFC — the default for permanent deployments
The right environments for NFC:
- Permanent installations expected to operate 3+ years
- Outdoor or harsh conditions (rain, sun, cold, chemicals)
- Areas where light is unreliable (corridors, basements, night patrols)
- Sites where you need physical proximity verification (the tag has to be touched, not photographed)
NFC technical notes for 2026:
- NTAG215 (504 bytes memory) is the workhorse for guard tour. Compatible with all modern smartphones with NFC. Cost: 0.30-0.80 € depending on volume.
- NTAG216 (888 bytes memory) for sites that store additional metadata (zone, asset ID, criticality). Cost: 0.50-1.20 €.
- Industrial encapsulation (epoxy, ABS housing, PVC sticker over) extends life from 12 months to 5+ years in harsh environments. Adds 0.50-2 € per tag.
- iPhone NFC limitation: iOS requires the user to actively trigger NFC reading (cannot be 100% background). Confirm your guard tour app handles this gracefully on mixed iOS/Android fleets.
Bluetooth beacons — when automatic scan justifies the cost
The right environments for Bluetooth:
- Large open spaces where covering checkpoints with discrete tags is impractical (stadiums, fairgrounds, large industrial yards)
- Sites with high-value patrols where you want continuous evidence of presence (not just point-in-time scans)
- Environments where the patrol officer carries multiple devices and adding manual scan is friction (drone-assisted patrols, robot patrols)
Bluetooth technical notes:
- Coin battery beacons (CR2477 typical) last 18-36 months at standard advertising interval. Reduce interval and life drops to 6-12 months.
- Mains-powered beacons exist for high-traffic checkpoints (entrance, lobby). Add complexity but eliminate battery management.
- RSSI variability is the dark side: signal strength varies with humidity, body proximity, metal interference. Geofencing within a building based on RSSI requires careful calibration site by site.
The hybrid approach used by the most mature deployments
After 18 months of operation, the mature security operations we have observed all converged to hybrid deployments:
- NFC for the majority of checkpoints (60-80%): permanent, low-maintenance, reliable.
- QR for temporary checkpoints (10-20%): construction zones, special events, pop-up patrol routes.
- Bluetooth for high-traffic or open-area checkpoints (5-15%): main entrances, large yards, areas where the patrol officer should not have to stop to scan.
The trap to avoid: deploying one technology for ideology. We met a head of security who insisted on «100% Bluetooth because it is the future». 18 months later he had spent 4× the budget of an NFC equivalent and was managing 200 beacon batteries quarterly.
Decision checklist for your next site
Before ordering hardware for a new site:
- Walk the patrol route physically at the time of day patrols actually happen.
- Check ambient light at each checkpoint (smartphone light meter app suffices).
- Test smartphone GPS signal at each location (apps like GPS Test on Android).
- Estimate replacement labor cost (who will replace tags? what is their hourly cost? how often per year?).
- Cross-check the environment against the matrix in this post.
- Buy a small batch (10 units) of the chosen technology, deploy 5 checkpoints, run patrols for 30 days.
- Adjust hardware specifications based on actual wear and reliability before placing the full order.
The 30-day pilot saves 60-80% of the mistakes that show up at month 9-12 in deployments that went straight from sales pitch to full rollout.
When the vendor pushes one technology over others
If a guard tour software vendor recommends one technology for every environment, you are talking to a sales pitch, not to security engineering. Mature vendors will ask about your sites before recommending hardware, and will admit when a technology is the wrong fit.
The right vendor for your maritime port and your office building is the one that recommends different hardware for each, configures the software to handle both transparently in the same patrol log, and offers documentation per environment.