NFC checkpoints prove the patrol happened
Paper logs and wands are out. An NFC checkpoint tap stamps the time and the spot, and the guard tour report writes itself for the client.
A client wants to know the stairwell got walked at 2am. A guard wants to walk it without paperwork. An NFC checkpoint tag settles both: the officer taps a phone to it, and the record says which checkpoint, when, and by whom.
NFC checkpoints replace paper tour sheets and proprietary wands with a tap from the phone the officer already carries. The tag has no battery, works indoors where GPS goes to pieces, and costs a fraction of a wand button. It is not unfalsifiable, but it is far harder to fake than a signature at the end of a shift, and the report writes itself.
What is wrong with what you have now?
Paper tour sheets
They can be completed in the guard shack at 5:55am. Everyone in this industry knows it, including the client. Even the honest ones are hard to read, impossible to total up across a month, and tell a supervisor nothing while the shift is still running.
Proprietary wand systems
The wand is one more thing to carry, break and lose, and it comes with its own software that does not talk to anything else you run. The worst part is the dock: nothing is known until the wand comes back to the office, so a missed checkpoint at midnight surfaces the next morning.
GPS on its own
Continuous location tracking eats the battery, and an officer whose phone dies at hour six stops using the app. Accuracy collapses indoors, which is where a lot of checkpoints live. And a GPS fix taken from the parking lot looks a lot like a GPS fix taken in the stairwell. There is more on doing location tracking without wrecking trust in rolling out GPS without losing trust.
How does the tap actually work?
NFC is the contactless payment technology. The NFC Forum puts it at a 13.56 MHz base frequency with a typical range of up to 2 cm, and a certified compliant connection range of 5 mm.
That number is the whole security argument. Two centimeters means the phone was physically at the tag. Not near the building, not in the vehicle at the curb, at the tag.
The tags themselves are commodity parts. An NXP NTAG213 carries 144 bytes of user memory, complies with NFC Forum Type 2 Tag and ISO/IEC 14443 Type A, holds its data for a stated 10 years, and ships with a 7-byte factory serial number plus 32-bit password protection and field-programmable read-only locking. It has no battery and nothing to service.
Is it really tamper-proof?
No, and you should not sell it that way.
A tag is a physical object screwed to a wall. Someone determined enough can pry it off and carry it to the break room, and then the tap says the checkpoint was reached when it was not. What NFC removes is the easy fraud: filling in a sheet, or clicking "done" in an app from the car. It raises the effort from zero to deliberate. That is a real improvement and it is a smaller claim than tamper-proof.
Two things narrow the gap. Lock the tag read-only after you write it, so nobody reprograms one in place. And read the tap against the rest of the record: a scan at a checkpoint with a GPS fix a mile away is a flag, and so is a route where four checkpoints arrive within nine seconds of each other.
Where do the tags go?
Placement is the part that decides whether the whole thing is worth anything. Cover entry points, high-value areas, the isolated corners that need someone to look at them, and fire equipment and emergency systems. Then order them into a route that walks in one direction rather than making an officer cross the site twice.
The full reasoning about which locations earn a checkpoint is in where to place patrol checkpoints, and the route mechanics are in routes that repeat on schedule.
What can you show a client?
Four things a paper sheet cannot produce at all.
- Completion percentage by shift, week or month, with the trend visible.
- Time between checkpoints, which shows whether a route is being walked or run.
- Which checkpoints get missed, and at which hour. That pattern usually names a specific problem: a locked door on the night shift, a route that is twenty minutes too long for the time allowed.
- Whether the tasks raised at a checkpoint were ever closed out.
The reports come out of the same data with no additional entry, which is covered in proof your patrols happened. How to frame it for the person signing the renewal is in client reports that win renewals.
How do you get started?
The scanning itself takes an officer about one demonstration to learn. The hard part is never the technology. It is choosing checkpoints that cover what matters without turning a 40-minute patrol into an hour. TeamMap's NFC checkpoints record the scan against the officer, the checkpoint and the route it belongs to. The step-by-step setup is in NFC checkpoint scanning in TeamMap.
Key Takeaways
- NFC reads at about 2 cm, which is what proves the phone was at the tag.
- NTAG213 tags are passive, need no maintenance, and can be locked read-only after writing.
- Do not call it tamper-proof. It removes the easy fraud. Read taps against GPS and timing to catch the rest.
- Placement decides the value. Walk the site with a map before you mount anything.
- The reporting is the payoff: completion trends, time between checkpoints, and the pattern behind repeated misses.
Continue Reading
NFC checkpoint scanning in TeamMap: a setup guide
NFC checkpoint scanning in TeamMap: which tags to buy, where to mount them, how a guard scans one, and how to keep tags reading for years.
Where to place guard tour patrol checkpoints
Guard tour checkpoint placement decides what a scan proves: corner points, interior rooms, NFC versus QR versus GPS, and timing the route honestly.
Patrol route planning with checkpoints and proof
Patrol route planning: ordered stops, NFC or QR proof at each one, repeat schedules, and an alert the moment a round runs late.