NFC Checkpoint Scanning Procedures: TeamMap Guard Tour Guide

NFC (Near Field Communication) checkpoint scanning provides the gold standard in patrol verification. Unlike GPS, which proves approximate location, NFC requires physical presence within centimeters of the tag—making it virtually impossible to fake patrol completion.

Why NFC Checkpoints?

GPS vs. NFC Verification

Best practice: Use both together. GPS provides continuous location awareness; NFC confirms specific checkpoint visits.

Setting Up NFC Checkpoints

Tag Selection

Choose NFC tags appropriate for your environment:

Tag Placement Guidelines

Strategic Locations

• Building entrances/exits
• Stairwells (each floor)
• Parking structure levels
• Loading docks
• Roof access points
• Emergency exits
• High-value areas (server rooms, vaults)
• Perimeter fence gates
• Remote/isolated areas

Placement Best Practices

• Height: 4-5 feet from ground (accessible, not obvious)
• Protected from weather when possible
• Away from high-traffic areas where tags might be damaged
• Not near strong electromagnetic interference
• Consistent placement (guards know where to scan)

Registering Tags in TeamMap

1. Open TeamMap app on admin device
2. Navigate to Checkpoints section
3. Tap "Add Checkpoint"
4. Scan the NFC tag
5. Enter checkpoint name and description
6. Set location on map (for reference)
7. Assign to patrol routes
8. Save checkpoint

Scanning Procedures

Standard Scan Procedure

1. Approach checkpoint location
2. Open TeamMap app (if not already running)
3. Navigate to Patrol or Checkpoints screen
4. Hold phone near NFC tag (within 4cm)
5. Wait for confirmation vibration/sound
6. Verify scan recorded on screen
7. Proceed to next checkpoint

Phone Positioning

NFC antenna location varies by device:

• iPhone: Top back of phone
• Samsung: Center back of phone
• Google Pixel: Upper back of phone
• Most Android: Center or upper back

Recording Observations

After scanning, guards can add observations:

• Photos of unusual conditions
• Notes about issues observed
• Incident reports if needed
• Maintenance requests

Patrol Route Management

Sequential vs. Random Routes

Timing Requirements

Configure checkpoints with timing rules:

• Minimum time between scans: Prevents rapid-fire scanning without actual patrol
• Maximum time between scans: Alerts if checkpoint is overdue
• Required scan windows: Checkpoint must be scanned during specific time ranges

Troubleshooting

Scan Won't Register

Tag Maintenance

• Inspect tags monthly for damage
• Replace tags showing wear or read failures
• Keep spare tags on hand
• Document tag locations with photos
• Test all tags after extreme weather events

Vandalism Prevention

• Use discrete placement (not obviously visible)
• Use rugged/encased tags in vulnerable areas
• Place tags behind secure covers if possible
• Monitor for unusual scan patterns (could indicate tag removed)

Training Guards

Initial Training Topics

1. What NFC is and why it's used
2. How to enable NFC on their device
3. Proper scanning technique
4. All checkpoint locations on their route
5. What to do if scan fails
6. Adding observations after scans
7. Route timing requirements

Common Mistakes

• Phone not close enough to tag
• Moving phone too quickly
• NFC disabled in settings
• Metal phone case blocking signal
• Scanning wrong tag (similar locations)