Geofenced Time Clock: How GPS Attendance Works

Quick definition: A geofenced time clock is a mobile attendance app that only allows a check-in when the employee's phone is inside a defined area around a work location. The area is the geofence: a centre point and a radius. Step outside it and the punch is blocked or flagged.

The appeal is obvious. If somebody has to be at the site to clock in, the oldest attendance problem in the world goes away. The reality is more textured, because GPS is less precise than the marketing implies, buildings interfere with it, and a badly configured radius generates a support queue instead of clean data.

This covers how it actually works, the four failure modes to design around, where it is the right tool, and how to introduce it without your team concluding that you are following them home.

How it works, step by step

You define locations. Each site gets a centre point (from a map pin or an address) and a radius, commonly between 50 and 200 metres.
The employee opens the app to punch. The phone resolves its position using satellites, nearby wifi networks and mobile cell towers together. Wifi and cell data are what make it work indoors at all.
The app compares position to the fence. Inside, the punch proceeds. Outside, it is refused or recorded with a flag, depending on how you configure it.
The record stores a coordinate pair and an accuracy value. That accuracy number matters more than the coordinates, and most systems hide it. It is the radius of uncertainty the phone itself reports.
Everything syncs. A well-built app records the punch locally when there is no signal and uploads later, preserving the original time and position.

The important design decision is step 3: block or flag. Blocking sounds stronger and causes more problems, which the next section explains.

Four failure modes, and how to design around them

ProblemWhy it happensWhat to do Accuracy drift indoorsSatellite signal is weak inside steel and concrete. The phone falls back to wifi and cell, which can be tens or hundreds of metres outSet the radius generously. Never set 20 metres for a building Urban canyon errorSignals bounce off tall buildings, so position jumps between streetsWiden the radius in dense areas and flag rather than block Battery saver interferenceAggressive power saving throttles location, returning a stale positionWarn staff at rollout, and store the reported accuracy value with the punch Permission revokedPhone OS updates reset location permission to "ask every time"The app must detect missing permission and say so plainly, not silently fail

This is the case for flag, do not block, at least at first. A blocked punch means an employee standing at the gate, on shift, unable to start work, phoning a supervisor. That converts a technical inaccuracy into a payroll dispute and a bad morning. A flagged punch records the time, notes that it happened 240 metres from the pin, and puts it in a queue for a manager who can see that the person was there all day. You keep the evidence and lose the confrontation.

Where it genuinely fits

Construction and trades. The site is the workplace, it changes every few months, and no fixed reader survives the environment. Geofencing is close to the only viable method here.
Security and facilities patrols. Several buildings in one shift, with a need to prove which ones were attended.
Home care and field service. Visit-by-visit evidence, often required by whoever funds the service.
Multi-branch retail and hospitality. One system covers ten locations without ten devices to buy and maintain.
Logistics and distribution. Depot arrival and departure without extra hardware in every yard.

Where it does not fit: salaried office staff who work partly from home, where the honest answer is that you do not need attendance at all, and remote knowledge teams, where geofencing a home address is both useless and intrusive. Measure output there instead.

Geofencing is not the same as tracking, and you must say so

This is where most rollouts go wrong, and it is a communication failure rather than a technical one.

Two very different things get sold under the same heading:

Location at punch time. One coordinate captured at check-in and one at check-out. Nothing in between. The system has no idea where anyone is at 14:00.
Continuous tracking. Position sampled throughout the shift, producing a movement trail.

The first is proportionate for attendance and is what most businesses actually need. The second answers a different question, carries materially more legal risk in many countries, and is what your staff will assume you have installed unless you tell them otherwise, in writing, on day one.

Be concrete when you announce it. "The app records where you are at the moment you check in and check out. It does not record your location at any other time, and it does not run in the background." That sentence prevents most of the resistance, and it has to be true.

Rolling it out

Map your sites and set radii generously. Start at 150 to 200 metres. You can tighten later with real data. Starting tight guarantees a bad first week.
Run in flag-only mode for two weeks. Block nothing. Collect the accuracy values and see which sites misbehave.
Fix the sites, not the people. A site where everyone appears 300 metres away has a wrong pin, usually dropped on a rooftop or a car park entrance rather than where staff actually gather.
Confirm offline capture works. Test in airplane mode at your worst-connected site. Basements and rural routes are where this breaks.
Publish the policy. What is captured, when, who can see it, how long it is kept, and what happens if the phone has no signal.
Decide what a flagged punch means. Who reviews it, how fast, and the default assumption. "Assumed present unless there is other evidence" is the defensible starting position.
Only then consider blocking. And only at sites where the data shows the fence is reliable.

Set schedules before go-live too. A geofence that works perfectly while marking everyone late because the default shift is wrong will still be blamed on the geofence. The complete guide to attendance management systems covers the schedule side.

Cost compared with hardware

Geofencing's real advantage over a fixed reader is not accuracy, which is worse. It is that a new site costs nothing. No unit to buy, ship, mount, power, network or replace. For a business whose locations change, that difference compounds every year. We set the two side by side in biometric attendance machines versus mobile apps.

Check the pricing model as well. Per-employee attendance pricing means a seasonal hiring spike raises this bill automatically, which is the worst possible timing for a business with sites opening and closing. Flat versus per-employee pricing covers the arithmetic.

Key takeaways

A geofence is a centre point and a radius. Indoors, GPS accuracy degrades badly, so generous radii are not a weakness, they are correct configuration.
Flag out-of-fence punches rather than blocking them, at least for the first few weeks. Blocking converts technical error into payroll disputes.
Store the accuracy value the phone reports alongside the coordinates. Without it you cannot tell a genuine outlier from a weak signal.
Location at punch time and continuous tracking are very different. Say in writing which one you have.
Best fit is work that moves: construction, patrols, home care, multi-branch, logistics. Worst fit is remote salaried staff.
The cost advantage over hardware is that an extra site is free.

Frequently Asked Questions

How accurate is GPS for attendance?

Outdoors with clear sky, typically within a handful of metres. Indoors, inside a warehouse, or between tall buildings it can be tens to hundreds of metres, because the phone is estimating from wifi and cell towers rather than satellites. Configure radii for the worst case at each site, not the best.

Can an employee fake their GPS location?

With deliberate effort and a mock-location tool, yes. It is also detectable through impossible movement between punches, mismatched device identity and repeated patterns. Judge it against your current process rather than against perfection: a paper register can be signed by anybody with no trace at all.

Is geofencing employees legal?

Capturing location at the moment of a punch, for attendance, with written notice to staff, is broadly accepted in many jurisdictions. Continuous background tracking is treated far more strictly and is restricted or requires specific consent in several countries. Rules differ by country and sometimes by region, so take local advice before enabling continuous tracking.

What radius should I set for a geofence?

Start between 150 and 200 metres for most sites, then tighten only where your own accuracy data supports it. Large sites, multi-storey buildings and dense urban locations need more. A 20 to 50 metre fence around a building will reject genuine punches all day.

What happens if there is no mobile signal at the site?

The app should record the punch on the device with its true timestamp and last known position, then sync when connectivity returns. Ask any vendor to demonstrate this in airplane mode before you buy, because it is commonly claimed and less commonly implemented.

Does the app need to run in the background?

For punch-time capture, no, and that is the version to prefer. Background location is only needed for continuous tracking, which is a different product with different obligations. If a vendor insists on always-on background permission for basic attendance, ask exactly why.

Can I use geofencing for staff who work from home?

You can, and it is usually a poor idea. It means storing home addresses as work locations and gating pay on being inside them. For remote salaried staff, schedule and output are better measures than presence.

TracefyHR captures a location point at check-in and check-out only, never in the background, stores the accuracy the device reported, records punches offline and syncs them later, and flags out-of-area punches for review instead of blocking the shift. See how attendance works or start a 30 day trial with no card.

Geofenced Time Clocks: How GPS Attendance Works and When to Use It