Attendance That Only Counts Inside the Boundary
Draw a boundary around each office, branch or site. Check-ins inside it are accepted; check-ins outside it are flagged or blocked, by your rule.
GPS attendance tells you where a punch happened. Geofencing decides whether that location is acceptable — and that is the difference between recording data and enforcing a policy. For any business running more than one location, geofencing is what makes attendance comparable: each site carries its own boundary, every employee is assigned to the sites they legitimately work from, and a check-in that falls outside becomes an exception with a name and a timestamp rather than a number that quietly enters the payroll run.
Why location data alone is not enough
Recorded but never enforced
Capturing coordinates that nobody reviews changes nothing. Without a boundary to check against, location data is an archive, not a control.
"I was just outside" is unanswerable
Without a defined radius per site, every marginal case becomes a judgement call, and judgement calls made repeatedly become precedent.
Sites need different tolerances
A single office needs a tight boundary; a factory campus or construction site legitimately needs a wide one. One global radius is wrong for at least one of them.
Exceptions are found too late
Out-of-boundary punches discovered during month-end reconciliation cannot be investigated meaningfully weeks after the fact.
How geofence attendance works
- 1
Define a boundary per site
Each office, branch, warehouse or project site gets its own centre point and radius, sized to what that location actually needs.
- 2
Assign employees to their sites
Staff are mapped to the locations they legitimately work from, including multiple sites for people who rotate between them.
- 3
Check-ins are validated on the spot
At punch time the coordinates are tested against the assigned geofence and the result is recorded with the punch.
- 4
Your policy decides the outcome
Out-of-boundary punches can be blocked outright, or accepted and flagged for approval — appropriate when field staff legitimately start work elsewhere.
What you get
Per-site radius
Each location carries its own boundary size, so a compact office and a sprawling plant are both configured correctly.
Multi-site employee assignment
Staff who rotate between branches are validated against any of their assigned sites rather than a single fixed one.
Flag or block policy
Choose enforcement per your operational reality. Blocking suits fixed-site staff; flagging suits field teams where exceptions are normal and need review, not prevention.
Exception reporting
Out-of-boundary punches surface as a reviewable queue while the day is still fresh, rather than as a month-end discovery.
Works with every capture method
Geofence validation applies to mobile app punches and to WhatsApp check-ins that carry a shared location.
Full audit trail
Each punch retains its coordinates and its geofence result, so an approval decision can be reviewed later on the evidence it was made from.
Who this is for
See geofence attendance on your own data
Start free for 7 days — no credit card. Or book a walkthrough with our team.
Frequently asked questions
What radius should we set for a geofence?⌄
It should match the site. A single-floor office is usually well served by a tight radius, while a factory campus or construction site needs a wide one to avoid flagging staff who enter from a different gate. Setting one global radius across dissimilar sites is the most common configuration mistake and produces either false flags or a boundary too loose to mean anything.
Should out-of-boundary punches be blocked or flagged?⌄
For fixed-site staff, blocking is usually right — there is no legitimate reason to start work elsewhere. For field staff, flagging is almost always right, because starting from a client site is normal and blocking would simply stop them recording attendance at all. The setting exists because the correct answer differs by team.
Can one employee be assigned to multiple sites?⌄
Yes. Staff who rotate between branches are validated against any of their assigned locations, so a legitimate punch at a second branch is accepted without an exception being raised.
Does geofencing work with WhatsApp attendance?⌄
Yes. A WhatsApp check-in that includes a shared location is validated against the assigned geofence in the same way as a mobile app punch.
What if GPS accuracy is poor at a particular site?⌄
Location accuracy is assessed before a punch is validated, so a low-confidence reading is not treated as a definitive in-or-out result. At sites with consistently poor GPS — basements, dense industrial areas — a kiosk or biometric device at the entry point is the more dependable primary method.