What Geofenced Clock-In Actually Does

Geofenced attendance is a simple idea with a narrow margin. Understanding the mechanism is most of understanding the failure modes.

The mechanism

A boundary is drawn around the workplace, usually a circle with a radius.

The worker opens an app and taps to clock in.

The phone estimates its position from satellites, mobile masts and nearby wifi.

The app compares the estimate against the boundary.

Inside: the punch is accepted. Outside: refused, or accepted with a flag.

Five steps. The strain is entirely in step three.

Why the margin is narrow

A workplace is small. A shop, a ward, a restaurant, a unit on an industrial estate — tens of metres across.

Position error in built-up areas is also tens of metres, and worse indoors.

Which means the boundary and the error are the same size, and that is a fundamentally different situation from tracking a van across a city.

Fleet geofencing works because the sites are far apart. Attendance geofencing works because the alternative is worse, and it works within a tolerance that has to be designed deliberately.

What it is trying to prevent

Punching in from home, or from the car park down the road.

Buddy punching: one person clocking in for another.

Disputes about arrival time.

These are real, and they are also smaller problems than most vendors imply. Worth sizing your own before designing around them.

What it costs when it fails

A refused punch means someone is at work and not clocked in.

They either work unpaid until it is fixed, or they stop working to sort it out.

Both are worse than the problem the system was addressing, and the first is a wage claim.

This asymmetry runs through everything in these notes: a false acceptance costs a few minutes of somebody's pay; a false rejection costs a shift's goodwill and possibly a tribunal.

The alternatives that exist

A wifi network name the phone can see.

A bluetooth beacon at the entrance.

An NFC tag on the wall.

A code displayed on a screen inside.

Each proves presence at the site more reliably than satellite position does indoors, and several collect less. They have their own note, and they are the comparison worth making before buying anything.

What this collection covers

How the position estimate actually behaves at building scale.

Sizing a boundary, and what the size costs in each direction.

Spoofing, and what is worth doing about it.

Personal phones, batteries and permissions.

The legal position, which is stricter than most deployments assume.

And what to do when a punch is refused, which is the part most often left undesigned.

Who this is for

Three audiences with different reasons to be here.

Whoever has been asked to deploy something and needs to know whether it can work at their sites.

Whoever will run it afterwards, which is usually payroll and usually not consulted.

And the people clocking in, whose cooperation determines whether the record describes anything, and whose interests are treated here as a design input rather than an obstacle.

Turn the principle into a test

For an example that can make this requirement testable, consult time tracking software. Treat the page as a starting point rather than proof and reproduce the workflow with real roles and failures.