A GPS geofence time clock sounds like the obvious fix for people clocking in where they shouldn’t: draw a circle around the work site, and only let punches inside it count. It’s a genuinely useful tool — but it’s routinely oversold as “proof” that someone was at work, and it isn’t that. This is a plain-English look at what a GPS geofence time clock can actually prove, what it can’t, and where you need a different control to close the gap.
We build one, so we’ll be straight about it: Punchwell ships a GPS geofence alongside its kiosk and mobile punch — and we deliberately treat it as a deterrent, not as evidence. Here’s the reasoning.
How a GPS geofence time clock works
The mechanics are simple. You define a work site as a point — a latitude and longitude — with a radius around it. When someone taps “clock in” on their phone, the app reads the device’s reported GPS location and checks whether it falls inside that circle. Inside, the punch is accepted; outside, it’s flagged or refused.
In Punchwell you can set a company-wide fence or a per-office fence, each with its own point and radius, and enter that radius in metres or feet (it’s stored canonically in metres; the unit is just for display and entry). The geofence honors the same enforcement modes as the rest of the clock — block, warn, or flag.
What a GPS geofence can do
Used honestly, a geofence pulls real weight:
- It raises the effort to cheat. For most staff, most of the time, a location check is enough friction to keep punches honest. It closes the casual “I’ll just clock in from bed” habit.
- It follows mobile workers. This is where GPS genuinely beats a network lock — field techs, delivery drivers, multi-site cleaners, visiting nurses. The fence can sit at whatever job site they’re actually at, because it isn’t tied to one office network.
- It gives you a signal, not just a timestamp. A punch with an in-fence location attached is more useful for spotting patterns than a bare timestamp with nothing behind it.
So a geofence is a good layer. The trouble starts when it’s treated as the last layer.
What a GPS geofence can’t prove
Here’s the part vendors tend to whisper:
- GPS location is software-reported, and software can lie. Fake-GPS apps, developer-mode location overrides, and rooted phones can all tell a clock-in screen that a device is standing in the parking lot when it’s on the couch. A geofence tells you where a phone says it is — not where the person actually is. That makes it a deterrent, not proof of presence.
- It needs an app and a permission — on a personal phone. A geofence only works if the device can read GPS and the employee has granted location access to the clock-in screen. That leans on personal phones for a work task, which some staff resent, and it means a denied permission can block a legitimate punch.
- Indoor GPS is weak. Concrete, metal, basements, and big-box interiors all degrade the fix. A worker genuinely at their station can get a fuzzy or missing reading — which is a problem if the clock treats “no clear fix” as “not here.”
That last point is where a lot of geofence clocks quietly punish honest people.
Our honest design: don’t lock out real workers
Because a weak GPS fix is a real-world fact, not a cheating signal, Punchwell’s geofence is built to fail open on the honest cases:
- A missing or weak GPS fix is allowed — and recorded in warn/flag mode — rather than bounced. The person at their station with bad reception still gets to clock in.
- Clock-out is never blocked by distance. Nobody gets trapped on the clock because they walked to their car or their GPS dropped at the end of a shift.
- You choose the enforcement mode. Block, warn, or flag — so you can run the geofence as a soft signal while something stricter does the hard enforcing.
That “something stricter” is the important half of the story.
Where the office-IP lock does the hard part
If a geofence can be spoofed from a couch, what actually can’t be? The answer is a network check. Every internet connection has a public IP address; your workplace has one, or a known set. Flag an on-site employee as office-only and Punchwell’s office-IP clock-in lock refuses any punch that doesn’t come from an allowlisted address — server-side, not merely logged.
The reason this is the hard control: to produce your office’s public IP, the device has to actually be on your office network. There’s no app that makes a phone at home appear to be on your shop’s Wi-Fi without genuinely connecting to it. GPS answers “where does the phone claim to be?”; the IP lock answers “is this device really on the office network?” — and only the second one can’t be faked from home.
So the sensible division of labor is:
- On-site staff → office-IP lock as the hard control. Fixed location, known network, zero personal-phone requirement.
- Mobile staff → GPS geofence as a deterrent at the job site, understood as a deterrent.
- Everyone → optional extras like clock-in time windows and block/warn/flag modes to tune strictness.
Punchwell is built around running both, self-hosted inside your own WordPress site, so whatever location or IP data you collect stays in your own database rather than a vendor’s cloud.
How to use a geofence well
- Don’t sell it internally as surveillance-grade proof. Tell staff it’s a deterrent that keeps the schedule fair, and pair it with the honest fail-open behavior so nobody gets locked out on a bad-signal day.
- Put the hard lock where the value is. For fixed on-site roles, lean on the IP lock; save the geofence for people who legitimately move.
- Mind the practicalities. The mobile/PWA punch screen needs HTTPS and a device that can read GPS; if a role can’t meet that, a kiosk on your network is the better fit.
Frequently asked questions
Can a GPS geofence time clock be spoofed?
Yes. GPS location is software-reported, and fake-GPS apps, developer-mode overrides, and rooted phones can make a device appear to be at the work site when it isn’t. Treat a geofence as a deterrent, not proof of presence. For a control that can’t be faked from home, use an office-IP lock, which requires the device to actually be on your office network.
Does a GPS geofence prove an employee was at work?
Not on its own. It proves where the phone reported it was at the moment of the punch, which can be spoofed and can also fail indoors. It’s a useful signal and a real deterrent, but it isn’t evidence of presence. Pair it with an office-IP lock for on-site staff, which enforces the network the punch comes from.
What happens if GPS is weak or unavailable when someone punches?
In Punchwell, a missing or weak GPS fix is allowed rather than bounced, and it’s recorded in warn/flag mode. Clock-out is never blocked by distance either. That’s deliberate — a bad signal is a fact of the real world, not proof of cheating, so honest workers aren’t locked out.
Is GPS or an IP lock better for my team?
Use the IP lock as the hard control for fixed, on-site staff — it can’t be faked from home and needs no app. Use the GPS geofence as a deterrent for mobile or multi-site workers, since it follows them to the job site. Most businesses are a mix, so Punchwell lets you run both and choose per employee.
The bottom line
A GPS geofence time clock can raise the effort to cheat and can follow mobile workers to a job site — but it proves where a phone claims to be, not where a person actually is, and it can be spoofed or defeated by weak indoor signal. Treat it as a deterrent, build it to fail open for honest staff, and put an office-IP lock underneath it for the on-site roles that should only ever punch from the building.
If you’re on WordPress, see how the two work together on the GPS geofence, kiosk, and mobile punch page.
Punchwell is an independent, third-party maintained GPL fork of the “WP Human Resource Management” plugin. Sturdyhaus is not affiliated with, endorsed by, or sponsored by wpspear, weDevs, the original author, or any other prior maintainer. Product names are referenced descriptively only; all trademarks belong to their respective owners.