Guardix Features
Security guard geofencing: the three places Guardix checks location
Security guard geofencing in Guardix: the site geofence for clock-in, GPS checkpoints with a radius, and optional geofences on NFC and QR checkpoints.

Security guard geofencing means drawing an area on the map and letting the app check whether the officer's phone is inside it. Guardix uses a geofence in three places: at clock-in, at GPS checkpoints on a guard tour, and as an optional extra check on NFC and QR checkpoints. This post explains each one, what the officer sees, and where the limits are.
Key points#
- By default, an officer outside the site's geofence cannot clock in; a company can relax this, and clock-ins from outside are then recorded and flagged.
- A GPS checkpoint has a radius of 25, 50 or 100 meters when added in the mobile app, and the officer taps to check in inside it.
- The app refuses a GPS check-in that is not precise enough, too old, marked as a mock location or outside the radius, and the server checks the distance again.
- An NFC or QR checkpoint can have an optional geofence, and the app blocks the scan when the phone is clearly outside the area.
- A GPS check-in needs a data connection and is weaker proof than an NFC tag, because a phone can still report false coordinates.
The problem it solves#
A guard company sells presence: an officer at the post, walking the patrol, at the right time. When a client asks "was someone actually here?", a paper log or a text message is only the officer's word. A geofence ties the record to a place, so the answer comes from the app and not from memory.
1. The site geofence at clock-in#
Every site has a geofence, the area set around it. By default, an officer outside that area cannot clock in. That keeps clock-ins from the parking lot down the street, or from home.
Some work does not fit a tidy boundary, such as a large property with several gates. A company can relax the rule for the whole company, one site or one officer. When it does, a clock-in from outside the geofence is still accepted, but it is recorded and flagged, so managers can see exactly which ones to look at.
Clock-in matters beyond the start of the shift. Managers are alerted when an officer is late to clock in, and officers file reports in the app while they are clocked in to their shift.
2. GPS checkpoints with a radius#
Patrol checkpoints in Guardix are NFC tags, QR codes or GPS points. A GPS checkpoint has no tag at all, which helps where a tag cannot be mounted.
Managers set up a GPS checkpoint in two ways:
- In the manager mobile app, they add a GPS checkpoint where they stand, with a radius of 25, 50 or 100 meters.
- In the web app, they can type a GPS checkpoint's coordinates and radius.
On the tour, the officer taps to check in at the GPS checkpoint. The check-in is not automatic. The app then takes a fresh location reading and refuses it when it is:
- not precise enough (worse than 50 meters);
- more than five minutes old;
- marked by the phone as a mock location; or
- outside the checkpoint's radius.
After the app accepts it, the server measures the distance again and records nothing if the check fails. A GPS check-in needs a data connection at that moment, so it does not work offline.
3. An optional geofence on NFC and QR checkpoints#
NFC tags and QR codes prove the officer's phone was at the tag. An NFC or QR checkpoint can also have an optional geofence: when the phone is clearly outside the area, the app blocks the scan. That adds a location check on top of the tag. A QR code that does not match the checkpoint is rejected as well.
Know the limits#
No checkpoint is impossible to fake. A phone can still report false coordinates, so a GPS check-in is weaker proof than an NFC tag, and NFC tags give the strongest proof. A practical approach is to use NFC tags where proof matters most, such as doors, alarm panels and high-risk areas, and GPS checkpoints in open lots or places where a tag would not survive.
What the client sees#
In the client portal, clients see tours and checkpoint logs for their own sites, along with clock-ins and a live map of on-duty officers, depending on what their client role allows. Clients can be notified when a tour is completed, or when a tour window passes without one.
Set it up on a new site#
- Check the site geofence. Make sure the area around the site matches where officers start their shift.
- Decide on exceptions. Relax the clock-in rule only where there is a reason, knowing those clock-ins stay flagged.
- Pick the checkpoint type for each spot. NFC tags for the strongest proof, QR codes where they suit, GPS points where no tag can go.
- Set a sensible radius. Choose 25, 50 or 100 meters in the mobile app, or type the radius in the web app.
- Walk the tour once. Run a test tour with the mobile app before the first real shift.
Frequently asked questions#
What is geofencing for security guards?#
It is an area drawn around a site or a checkpoint, used by the app to check whether the officer's phone is inside it. In Guardix, it is used at clock-in, at GPS checkpoints and, optionally, on NFC and QR checkpoints.
Can an officer clock in outside the site's geofence?#
Not by default. A company can relax the rule for the whole company, one site or one officer, and then clock-ins from outside the geofence are accepted but recorded and flagged for managers.
Does a GPS check-in need a data connection?#
Yes. A GPS check-in needs a data connection at that moment, because the server measures the distance again before recording it. Where signal is poor, an NFC tag or QR code can be the better choice.
Is a GPS check-in as strong as an NFC tag?#
No. A phone can still report false coordinates, so a GPS check-in is weaker proof than an NFC tag. NFC tags give the strongest proof.
- Geofencing
- Patrols
- Features