# Geofenced attendance without tracking employees all day

Published 3 October 2026 by The PayLoom team. https://payloom.in/blog/geofenced-attendance-without-tracking

> Privacy-respecting geofenced attendance reads location only at the moment of a clock in or out, stores the distance from the site boundary, and flags out-of-boundary punches instead of blocking them.

Geofencing answers a narrow question: was this person at the site when they clocked in? It does not need to answer where they were for the rest of the day. Keeping it to that narrow question makes attendance data more defensible and makes the system far easier for employees to accept.

## Read location at the punch, and only then

The simplest privacy rule is also the most useful one: read the device's location at the moment of a clock in or clock out, and at no other time. There is no background tracking, no trail of movements, and nothing to explain about why the company knows where someone was at lunch.

What gets stored can be narrower still. Instead of keeping raw coordinates, store the distance from the site boundary. That is enough to show whether a punch was inside the geofence, and by how much it was outside if it was not.

## Flag, do not block

A geofence that refuses a clock in creates a worse problem than the one it solves. Location readings drift, sites have car parks and side entrances, and field staff work at client premises. If the punch is refused, the person either cannot record their hours or records them some other way that leaves no trace.

The better design accepts every punch, stamps it with its distance from the boundary, and flags the ones outside it for a supervisor. Nobody is blocked from recording time, and nothing outside the boundary is silently accepted either.

## Setting the boundary

- Give each site its own centre and radius. A single radius for every site will be too tight for some and too loose for others.
- Size the radius to the real site, including car parks and entrances people actually use, plus a margin for location accuracy.
- Review the flagged punches for the first few weeks. A cluster of near-misses at one site usually means the radius is wrong, not that people are.
- Decide in advance who can approve an out-of-boundary punch and what reason they must record.

## Tell people what is collected

State plainly what the system records and when: location at clock in and clock out, stored as distance from the site, visible to their supervisor when a punch is flagged. Employees who know exactly what is collected are far less likely to assume the worst.

Note: Data protection rules on employee location differ by country. Check the requirements where you operate before switching geofencing on.

## How PayLoom does it

PayLoom's Attendance module gives each site a boundary and a radius. A clock in outside it is accepted, stamped with the distance and flagged, so field staff are never blocked and nothing is silently allowed. Location is read at the punch only, not tracked through the day.