When you need to be sure guards actually reach specific locations, GPS alone isn’t always enough.
With NFC tags, guards physically scan a tag at each checkpoint. Each scan triggers an NFC Event in Connecteam, giving you a clear, reliable record of where they’ve been and when.
This makes it easy to track patrol routes, confirm completion, and spot anything that was missed.
Before You Start
Set yourself up for success with a quick bit of prep:
Place an NFC tag at every checkpoint (for example: Main Gate, Loading Dock, Server Room).
Decide where scan data should go:
A webhook tool (like Zapier)
Your own internal system or endpoint
Follow this link to purchase the NFC Tag through Connecteam!
Step 1: Plan Your Patrol Route
Start by mapping out the route your guards will follow.
List each checkpoint in order
(Example: Main Gate → Lobby → Stairwell → Server Room → Loading Dock)Assign one NFC tag to each location
Label each tag clearly so it matches the name you’ll use in Connecteam
This keeps everything consistent and easy to track later.
Step 2: Open NFC Event Settings in Connecteam
To set things up:
Click your admin icon (top-right)
Go to General Settings
Select NFC Events from the left menu
Click Add NFC Event
Step 3: Create an NFC Event for Each Checkpoint
Each checkpoint needs its own NFC Event so scans can be tracked individually.
For every checkpoint:
Enter the NFC ID
(Must match the tag exactly—this is case-sensitive)Add a clear Name
(Example: “Server Room Checkpoint”)Enter your Endpoint URL
(Where scan data will be sent—like a webhook or internal system)(Optional) Add a Secret token if your endpoint requires it
Keep scan confirmation popup enabled so guards know it worked
Click Save, then repeat for all checkpoints.
Step 4: Test the Route Before Going Live
Before sending guards out, test everything end-to-end.
Scan each NFC tag using a mobile device
Make sure the success message appears
Check that your system (or automation tool) receives the scan
This step helps you catch issues early.
Step 5: Monitor Patrol Activity
Once everything is running, you’ll be able to track patrols based on where your scan data is sent.
If you’re using an automation tool (like Zapier):
You can log scans into a spreadsheet or database and see:
Which checkpoint was scanned
When it happened
Which user scanned it
If you’re using your own system:
Use your internal reporting to confirm that every checkpoint was visited during each shift.
Frequently Asked Questions
Why use NFC instead of just GPS?
GPS shows general location, but NFC confirms a guard physically reached a specific point. This is especially useful for fixed checkpoints like entrances or secure rooms.
Do I need one NFC Event or multiple?
You’ll need one NFC Event per checkpoint. This keeps each location clearly identifiable.
Related Articles
Need more guidance? 🙋 Our LIVE support team (at the bottom right corner of your screen) replies to ANY question.