Geofencing Time Clock for Multiple Locations: How It Works and How to Set It Up
How a geofencing time clock for multiple locations checks punches, how to set radius and rules per site, and how to handle GPS drift and exceptions.
On this page
- How a geofencing time clock for multiple locations works
- Setting it up across several sites
- 1. Clean up your location list first
- 2. Pick a radius per site, not one for everyone
- 3. Decide who can punch where
- 4. Choose “block” or “flag”
- 5. Write down the exceptions
- Common problems and how to fix them
- How ClockLap handles geofencing
- FAQ
- Does a geofencing time clock track employees all day?
- What radius should I use for each location?
- Can one employee clock in at more than one location?
- What if an employee’s phone has no GPS signal?
- Is geofencing enough to stop buddy punching?
A geofencing time clock for multiple locations draws a virtual boundary around each of your sites and checks an employee’s phone location when they clock in or out. If the punch happens inside a site’s boundary, it’s accepted and tagged to that site; if it happens outside every boundary, the system blocks it or flags it for a manager to review. Below is how that works in practice, how to set it up across several sites, and what to watch for before you roll it out.
How a geofencing time clock for multiple locations works
Every geofencing system follows the same basic loop:
- You define each site. Each location gets a pin on a map (usually from its street address) and a radius, which forms a circle around the site.
- The employee punches from their phone. The mobile app reads the phone’s GPS position at that moment.
- The system compares the position to your sites. Depending on the tool, it checks either the sites the employee is assigned to, the site their shift is at, or every active site.
- The punch is accepted, blocked or flagged. Inside a fence, the punch goes through and records which location it matched. Outside, it’s either refused or saved with a warning for review.
Some tools go one step further and clock people in or out automatically when they enter or leave a site, rather than waiting for a manual tap. That’s convenient for crews who move between job sites, but it needs clear rules so nobody is paid for sitting in the parking lot.
Setting it up across several sites
Rolling out geofencing to one store is easy. Rolling it out to ten is where small decisions start to matter.
1. Clean up your location list first
Make sure every site has a consistent name staff will recognize (“Downtown”, “Warehouse 2”) and a correct address. Then check the pin on the map. Addresses for malls, business parks and large plants often resolve to the middle of a property, not the staff entrance.
2. Pick a radius per site, not one for everyone
A single radius rarely fits every location. Vendor help docs commonly start around 100 metres and let you tighten or widen it per site. As a rough guide:
| Site type | Starting radius | Why |
|---|---|---|
| Small storefront on a street | Tight | Neighbouring businesses are close by |
| Store inside a mall or plaza | Medium | GPS drifts indoors and pins may sit mid-property |
| Warehouse, yard or plant | Wide | Staff park and enter far from the address point |
| Construction or field job site | Wide, adjusted per job | Boundaries change as the job moves |
Start tighter, then widen sites where honest employees keep getting flagged.
3. Decide who can punch where
Choose one of these rules and apply it consistently:
- Assigned sites only: employees can punch only at locations on their profile. Best for staff tied to one or two stores.
- Shift location: the punch must match the site on today’s schedule. Best when people float between locations.
- Any active site: the punch is accepted at any of your locations and tagged to that site. Simplest for small teams with shared staff.
4. Choose “block” or “flag”
Blocking off-site punches stops problems at the source, but it can strand an employee whose GPS is acting up. Flagging lets the punch through and puts it in front of a manager at approval time. Many multi-site teams flag first, review the exceptions for a few weeks, then switch problem sites to blocking.
5. Write down the exceptions
Decide in advance how you’ll handle off-site work (deliveries, training at another store, client visits), dead zones with weak signal, and staff without smartphones. A shared kiosk or a supervisor clocking in the crew covers the last two cases.
Common problems and how to fix them
- GPS drift indoors. Accuracy depends on the device, the building and nearby structures. Widen the radius for that site rather than for all of them.
- Wrong pin. If one site produces lots of flags, the pin is probably in the wrong spot. Move it to the staff entrance.
- Overlapping fences. Two stores in the same plaza can overlap. Use shift-location rules so punches land on the right site.
- Privacy concerns. Explain to staff that location is checked at clock-in and clock-out. If you use any ongoing location features, make them opt-in and say so in your policy. Check your provincial or state rules on employee monitoring before rollout.
How ClockLap handles geofencing
ClockLap’s iOS and Android apps include geofenced automatic clock-in and clock-out, so time starts and stops as staff arrive at and leave a site. Alongside that, you can require a photo at clock-in, let a supervisor clock in a whole crew, or set up kiosk mode with PINs or QR badges for staff who don’t use their own phones. An opt-in live crew map is available for teams that want it.
Geofenced punches then flow into the rest of the workflow: multi-level timesheet approvals, US state and Canadian provincial overtime rules, and job costing by site. When the hours are approved, ClockLap’s ready-made integrations can send them on to payroll tools such as ADP Workforce Now, Gusto, QuickBooks Online and Paychex Flex (payroll connections are currently labelled beta on clocklap.com).
Pricing is one plan with every feature included: $1 per staff member per month and $2 per manager or admin per month, with no setup fees or contracts and 30 days free with no card needed. Geofencing isn’t an add-on or a higher tier.
FAQ
Does a geofencing time clock track employees all day?
Not necessarily. Most geofencing time clocks check location only at the moment of a punch, or when someone crosses a site boundary for automatic clock-in. Continuous tracking is a separate feature, and it’s best kept opt-in and clearly explained.
What radius should I use for each location?
Start with a tight radius at street-front sites and a wider one at warehouses, plazas and job sites. Adjust any site that produces frequent false flags.
Can one employee clock in at more than one location?
Yes. Assign multiple sites to the employee, or use a rule that accepts any active location and tags the punch to the site it matched.
What if an employee’s phone has no GPS signal?
Have a fallback: a shared kiosk at the site, a supervisor clocking in the crew, or a flagged punch that a manager reviews before payroll.
Is geofencing enough to stop buddy punching?
It stops punches from the wrong place, but not punches by the wrong person. Pair it with photo at clock-in or kiosk PINs if identity is the concern.