NFC checkpoint scanning in TeamMap: a setup guide

A GPS fix says a guard was somewhere near the loading dock. An NFC checkpoint scan says the guard's phone touched the tag screwed to the dock wall. That is the difference between a patrol record a client accepts and one their lawyer picks apart.

Why use tags at all?

Because satellites cannot see through a roof.

GPS.gov puts smartphone accuracy at about a 4.9 meter radius under open sky, worsening near buildings, bridges and trees. NFC is a different physics problem entirely. The NFC Forum puts the technology at 13.56 MHz with a typical range of up to 2 cm, and a certified compliant range of 5 mm.

Two centimeters is not a range you can drive past.

Run both. GPS gives the dispatcher continuous awareness of where everyone is; NFC settles the specific question of whether a given checkpoint was reached. The full setup for the GPS half is in GPS patrol verification, and the operational case for tags is made in NFC checkpoints prove the patrol happened.

Which tags should you buy?

Match the tag to what will happen to it.

Vendors quote lifespans in years, and those figures assume the tag is not pressure-washed, scraped, sun-baked or picked at. Budget on your own replacement history rather than the datasheet. On an outdoor site, a tag or two a quarter is not a failure of the system, it is the running cost of it.

Where do the tags go?

Somewhere a guard has to physically stand, which is also the place an intruder would have to pass.

• Building entrances and exits
• Stairwells, one per floor
• Each parking structure level
• Loading docks
• Roof access points
• Emergency exits
• Server rooms, vaults, cash offices
• Perimeter fence gates
• The isolated corners nobody visits unless a checkpoint sends them

That last one is the whole point. A tag on the wall beside the guard desk verifies nothing, and a tag at the far end of the back lot at 0300 is the reason you bought the system. Which locations earn a tag is worked through in where to place patrol checkpoints.

Mounting

• Roughly 4 to 5 feet off the ground: reachable without crouching, not at eye level for a passerby
• Sheltered from weather where the geometry allows
• Out of the path of carts, forklifts and shoulders
• Away from motors, transformers and anything else radiating at close range
• Consistent from tag to tag, so a guard never has to hunt for it in the dark

Registering a tag

A tag is not an object in its own right. It belongs to a record you already have.

1. Open the site, route stop or task the tag will prove.
2. Scan the tag to attach its ID to that record.
3. Set NFC as the verification method. QR code, GPS, a photo and a report are the other options.
4. Save.

Because the tag hangs off the record, the site, the stop or the task carries the tag ID. There is no separate tag inventory to keep in step with the map, which is the thing that rots first in most systems.

How does a guard actually scan one?

1. Walk to the checkpoint.
2. Open TeamMap and go to the route or task you are working.
3. Choose to check in by NFC.
4. Hold the phone against the tag.
5. Wait for the confirmation.
6. Check the scan appeared on screen before you walk away.

Step six is the one guards skip and supervisors regret. A scan that did not register is indistinguishable, three weeks later, from a checkpoint that was never visited.

Where the antenna lives

It is not in the middle of the phone, and it is not in the same place on every phone.

• iPhone: top of the back, near the cameras
• Samsung: center of the back
• Google Pixel: upper back
• Most other Android: center or upper back

If a scan does not take, move the phone slowly across the tag rather than pressing harder. And take the case off if it is thick, metal-backed, or has a magnetic mount or card slots in it. Card slots are the single most common cause of a phone that "does not have NFC".

What else goes with the scan

The scan proves attendance. The observation is what makes the visit worth anything.

• Photos of anything unusual
• A note about what was found
• A report, where the checkpoint calls for one or the situation warrants it
• An incident, where someone else has to pick it up

Should the route run in order?

It depends who you are worried about.

A site with a real theft problem wants unpredictability. A site where the client mostly wants documented coverage wants sequence, because sequence is what makes a gap obvious. Most operations end up with timed windows over a loose order, which is covered in routes that repeat on schedule.

Watch the pace, not just the count

• Scans seconds apart. Nobody walks a building that fast. That pattern is somebody tapping tags they have collected, or a route whose checkpoints are three feet apart.
• Overdue checkpoints. A checkpoint unscanned past its window is worth a call before it is worth an investigation.
• Shift-bound windows. Some posts need a specific checkpoint hit during specific hours. Build the route around the requirement rather than trusting memory.

Night shifts are where all of this gets tested. Staying sharp on night patrol covers the human half of the problem, which no tag solves.

What goes wrong, and what fixes it?

Keeping tags alive

Tags people interfere with

• Mount them discreetly. A tag nobody notices is a tag nobody peels off.
• Use encased tags anywhere the public can reach.
• Put a cover over them where the mounting allows it.
• Watch for a checkpoint that suddenly stops being scanned. That is usually a missing tag, not a lazy guard, and treating it as the second one is how you lose a good officer.

What do guards need to be taught?

1. What NFC is and why the company uses it. Skipping this is why crews assume it is about mistrust.
2. How to turn NFC on for their own handset.
3. Where the antenna is on their own handset.
4. Every checkpoint location on their route, walked once with a supervisor.
5. What to do when a scan fails, including who to tell.
6. How to add a photo, a note, a report or an incident to a scan.
7. The timing the route expects.

Most failed scans come down to five things: the phone is not close enough, it is moved too fast, NFC is off, the case is in the way, or the guard scanned a different tag in a similar-looking spot. Cover all five in the first training session and the support calls mostly stop. The wider patrol standard this fits into is in the patrol procedures protocol.