How to Set Up a Geofenced Time Clock (and Keep It Legal)
A geofenced time clock only lets employees clock in when their phone is inside a virtual boundary around a job site, or flags the punch for review when it isn't. To set one up, map each site, choose block or flag, test the radius on foot, write an exception process and give employees written notice before you turn it on.
Geofencing is good at one thing: showing that a punch happened near the right place. It doesn't prove who was holding the phone, and it can't see whether someone worked once they walked away from the site. Treat it as one control in a small set, and you'll avoid both false confidence and a pile of angry messages from honest employees who couldn't punch in.
What does a geofence check, and what can't it catch?
A geofence compares the coordinates your phone reports with a circle drawn around an address. Inside the circle, the punch goes through. Outside, the app either blocks it or lets it through with a flag for a manager.
That makes it useful for crews who move between sites, for delivery and field teams, and for anyone who might otherwise punch in from the parking lot of a different job. It does not solve buddy punching by itself: a coworker can carry two phones, and a phone left in a truck still reports the truck's location. Pair location with a second check, such as a photo at punch time or a personal PIN, if identity matters to you.
Location also says nothing about the quality of the hours. It tells you where a phone was at two moments, not what the person did between them.
How do you set it up, step by step?
Work through these steps in order, and finish each one before you announce anything to employees:
- List every site where people clock in, with a street address and a pin dropped on the actual entrance, not the mailing address of the office park.
- Decide the rule for outside-the-fence punches: hard block, or allow and flag. Start with flag. Blocking on day one turns every GPS glitch into a payroll dispute.
- Set an initial radius (next section covers how) and save it per site, since a warehouse and a storefront need different sizes.
- Walk the edge of each fence with two phones, one iPhone and one Android, and punch at the inside edge, the outside edge and deep inside the building.
- Write down what an employee does when the punch fails: a text to a supervisor, a manual time request, and who approves it within what timeframe.
- Send employees the written notice, then turn it on.
- Review the flagged punches weekly for the first month and adjust.
How big should the radius be?
Phone location is an estimate, and it gets less precise indoors, near tall buildings and in basements. If the circle is tighter than the phone's error, honest employees get rejected at their own front door.
Say your shop sits on a lot with a building at the back and parking at the front. A circle that only covers the building will reject people clocking in from the parking spot, where many of them start. Draw the circle to include the parking area and the entrance, then test from the far corner of the lot.
Start generous and tighten later. After two weeks, look at the flagged punches: if most are honest people just outside the line, widen it. If the fence is so wide that it covers the coffee shop next door, shrink it. Large campuses and construction sites usually need a bigger radius than a single storefront, and sites with several buildings sometimes work better as multiple small fences than one huge one.
What do you need to check on privacy and pay rules?
Location data about employees is sensitive, so set limits before you collect it. Collect location only at the moment of a punch, not continuously in the background, and never track someone after they clock out. Say this in writing.
Some states require you to give employees written notice of electronic monitoring; New York, Connecticut and Delaware are examples, and the rules change, so confirm the current requirements for every state where you have staff. If you use face matching for identity, biometric privacy laws in some states add consent and retention rules of their own. If people use their own phones, check whether your state expects you to reimburse part of the cost.
Finally, remember pay. If a geofence blocks someone from punching and they work anyway, you still owe them for that time under wage-and-hour rules. Your exception process has to capture that time and pay it. Have an employment attorney review the notice and your policy before launch.
Which geofencing problems come up most often?
These are the failures to plan for before they reach payroll:
- Location permission turned off. The app can't check anything, so the punch fails or gets flagged. Train people to allow location while the app is in use.
- Weak signal indoors. Warehouses, basements and hospitals return poor readings. Test inside, and use a flag instead of a block there.
- Multi-site days. Crews who visit three customers a day need each site saved ahead of time, or a shared "field" fence that a supervisor approves.
- Remote and hybrid staff. A home address is not a work site. Exempt remote employees from the fence rather than tracking their homes.
- Location spoofing apps. Some phones can fake a location. Treat repeated punches from oddly identical coordinates as a reason to look closer, and add photo or PIN checks.
What Good Looks Like
A good geofenced clock is tested on foot at every site, flags before it blocks, pairs location with a second identity check and comes with written employee notice and a paid exception process.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
Does geofencing prevent buddy punching?
Not on its own. Geofencing confirms a phone was near the site, not who was carrying it. To reduce buddy punching, combine it with a second check such as a photo at punch time or a personal PIN, and review flagged or repeated punches each week.
Is it legal to track employee location with a time clock app?
Usually yes when it's limited to clock-in and clock-out, disclosed in writing and never applied off the clock. Some states require notice of electronic monitoring, and biometric checks add extra rules. Because requirements vary by state, have an employment attorney review your notice and policy.
How accurate is phone GPS for a geofence?
Accurate enough for a site-level check, not for a doorway. Readings typically drift more indoors and around tall buildings. That's why you should test at the edges of each fence with more than one phone and set the radius wider than the drift you observe.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Buddy Punch vs Deputy vs When I Work: Hourly Time Tracking & Scheduling Comparison
Compare Buddy Punch, Deputy, and When I Work: GPS geofencing, facial recognition punch-in, shift scheduling, wage compliance, and payroll export.
Geofenced Clock-Ins: Build a Policy or Buy Buddy Punch
Whether a geofenced clock-in tool like Buddy Punch is worth adding, or whether a clearer manual policy solves most of your time-tracking accuracy problem.
Clocking In Clinical Staff Without Losing the Schedule
How Buddy Punch and Deputy handle clinical staff time tracking, shift swaps, and break compliance, and where a practice still needs its own process on top.
First Response and Resolution Time: Set Your Own Targets
Learn how to measure first response and resolution time, segment targets by channel and priority, and set benchmarks from your own data, with a worked example.
Support SLA Policy: Priorities, Targets and Clock Rules
Write a customer support SLA policy: priority definitions, response and update targets, coverage hours, clock rules, escalation and how to handle misses.
Contract Renewal Tracker: Columns, Dates and Alert Rules
Set up a contract renewal tracking spreadsheet with the right columns, a notice-deadline formula and a 90-day review routine that stops surprise auto-renewals.