Geofence Time Tracking: How Job Site GPS Works for Field Teams

May 23, 202613 min read

Geofence time tracking requires employees to be within a defined GPS radius of a job site before they can punch in. It doesn't track their location during the shift — it just verifies they're on-site at the start. Most well-designed systems apply the fence only to punch-in, not to punch-out or breaks, so employees aren't stranded if they step off-site for lunch or lose GPS signal at quitting time.

This guide explains how geofenced job sites work, what they protect against, and where the technology falls short.

What Is Geofence Time Tracking?

A geofence is a virtual boundary drawn around a real-world location — typically defined by a GPS coordinate (latitude/longitude) and a radius in feet. When an employee tries to punch in, the app checks their current GPS position against every job site in your account. If they're within the allowed radius of a site, the punch goes through. If they're not, it's blocked with an explanation.

The key word is punch-in only. Once an employee is marked as on-site, subsequent actions — punching out, starting lunch, ending lunch — are intentionally not geofenced. There are three good reasons for this:

GPS drift. A phone that was perfectly positioned at the start of a shift may read 200 feet off an hour later due to satellite geometry changes. You don't want employees unable to punch out because the sky shifted.
Legitimate movement. Employees leave job sites during shifts. A roofer may drive to a supplier for materials. A landscaper may move between multiple addresses in one day. Geofencing every action would create constant friction.
Network outages. Field crews often work in areas with poor cell coverage. A system that blocks punch-out without network confirmation traps employees in a "punched in forever" state — a real data corruption problem.

How GPS Radius Works in Practice

Most apps express the geofence radius in feet (US standard) or meters. Common settings:

| Radius | Best for | |--------|----------| | 165 ft (50 m) | Dense urban job sites, single-building work | | 330 ft (100 m) | Typical commercial or residential site | | 650 ft (200 m) | Large properties, warehouse complexes | | 1,650 ft (500 m) | Rural land with unclear boundaries | | 3,300 ft (1,000 m) | Multi-acre parcels, remote worksites |

GPS on a modern smartphone is accurate to about 10–50 feet under open sky. In a parking garage, basement, or dense urban canyon with tall buildings, accuracy can degrade to 100–300 feet. Set your radius at least 1.5× the expected GPS error to avoid false negatives — employees who are legitimately on-site but getting blocked.

Setting Up Job Sites With Geofencing

The basic setup for any job site:

Name the site. Use a name your employees will recognize — the customer's business name, a street address, or a project code. This name appears on every shift record, approval queue entry, and payroll export.
Set the coordinates. Drop a pin on the map or search by address. The app geocodes the address to a lat/lng coordinate pair.
Set the radius. Start larger than you think you need. You can tighten it after watching whether legitimate employees are getting blocked.
Enable geofencing at the org level. Most apps have a per-org toggle that turns geofencing on or off entirely. Some sites — project-oriented work where employees self-direct their locations — don't need geofencing at all. Disabling it org-wide means the site coordinates still exist for grouping and reporting, but the app won't require GPS verification at punch-in.

For sites without a fixed address (a road clearing project, a pipeline segment, a field that won't have an address until the building is done): drop the pin on the satellite map at the approximate center of the work area, then set a generous radius. Update the coordinates as the project moves.

Project Sites vs. Regular Job Sites

Some field work doesn't happen at a fixed location. Landscaping crews may move among 15 residential addresses in a single day. Construction crews may stage equipment at a different spot than where work is actually happening.

For these workflows, the right configuration is often no geofence — use job sites purely for grouping and reporting without enforcing GPS at punch-in. Employees still punch in to the correct site by tapping it from a list, so your payroll records show which project their hours belong to. You just aren't requiring them to be at GPS coordinates X,Y first.

This is the meaningful distinction between "job site as cost center" (which every field business needs) and "job site as geofenced location" (which only some businesses need).

What Geofencing Actually Protects Against

Geofencing is most valuable in two specific scenarios:

Buddy punching. An employee who isn't on-site asks a coworker to punch in for them. The coworker is at the job site; they could use their own phone or the absent employee's phone to log the start. A geofence doesn't stop this completely — a coworker who shows up at the job site with two phones can still do it — but it raises the bar significantly. The absent employee has to coordinate a proxy who is physically present.

Administrative punch-ins. In workflows without geofencing, managers sometimes punch employees in manually from the office when they know a crew started at 7am. This creates a paper trail but bypasses the actual GPS verification. With geofencing enabled and applied to all punch-ins (not just manual ones), this backdoor closes.

What Geofencing Doesn't Protect Against

Be clear-eyed about the limits:

Two phones, one person. An employee with two phones (or a co-worker willing to carry the phone on-site) can punch in from the job site while working elsewhere.
GPS spoofing. Deliberate GPS spoofing apps exist on both iOS and Android. A determined bad actor can fake their location. Most small-to-mid-market time tracking apps don't detect spoofing.
Layover stops. If an employee passes close to a job site on the way to a different location, they might be within the geofence radius briefly. If they punch in at that moment, the system accepts it.
The punch-out gap. Because geofencing only applies to punch-in, an employee could leave the job site after punching in and never return — but still punch out remotely. The hours are logged as if they were on-site the whole time.

The honest framing for most small businesses: geofencing stops casual cheating and honest mistakes (employees forgetting to punch in). It doesn't stop a determined employee who understands how the system works.

Geofencing and FLSA: What Matters for Payroll

The Fair Labor Standards Act requires you to pay employees for all hours worked. Geofencing affects when time is recorded, not when it legally begins.

If an employee arrives at a job site at 7:00am but your app requires 3 GPS fix attempts (taking 90 seconds) before they can punch in, legally their workday began at 7:00am — not 7:01:30. For most practical purposes this gap is negligible, but if your geofencing system consistently delays punch-in by several minutes, you have both a payroll accuracy problem and potential FLSA exposure.

The practical guidance:

Don't require punch-in immediately upon arrival if your GPS verification takes more than a few seconds. Let employees start work and tap punch-in once the app is ready.
Don't block punch-out based on geofence verification. Employees leave sites for legitimate reasons; blocking their punch-out creates incorrect time records.
Do record the actual GPS coordinate of the punch-in for reference. Useful for dispute resolution without making it a blocker.

How Punch Handles Geofenced Job Sites

Punch applies geofencing exclusively at punch-in. The following actions are never geofenced, regardless of whether geofencing is enabled:

Punch-out
Start lunch
End lunch

This is enforced at the database level, not just in the app UI — the server-side validation trigger exits early for punch-out and break events and does not apply the distance check.

Job site setup in Punch:

Each job site has a name, optional address, and optional lat/lng + radius (in feet, US imperial standard across all surfaces).
Lat, lng, and radius are all optional columns — you can create a job site for cost-center grouping without setting any coordinates. Shifts still associate to that site; the punch-in distance check is simply skipped.
When geofencing is enabled at the org level and a job site has coordinates, Punch checks the employee's GPS position against that site at punch-in time. If they're outside the radius, the punch is blocked with an explanation.

Offline punch-out support: Punch's offline queue handles punch-out, lunch start, and lunch end even when there's no cell service. The action is captured locally with the exact timestamp and synced to the server when the device comes back online. Because punch-out isn't geofenced, this works cleanly — no location check needs to happen at sync time.

Org-level on/off toggle: Owners can turn geofencing on or off for their entire org from settings. Turning it off doesn't delete job site coordinates — it simply stops the punch-in distance check. Useful for seasonal businesses where certain projects have unclear GPS boundaries.

Reports and exports: Every shift record shows which job site the employee punched in to. In Punch's QuickBooks-compatible CSV export, the job site name maps to the Customer column — meaning your payroll export already shows which project each hour belongs to without extra manual tagging.

Multiple sites, one employee: Employees can punch in to any active job site in the org. The geofence check runs against the site they've selected, not all sites simultaneously. If an employee is on-site for Project A and accidentally selects Project B from the list, the distance check will block them — which is the intended behavior.

Common Geofencing Configuration Mistakes

Setting the radius too tight. A 50-foot radius on a construction site with unreliable urban GPS means employees 60 feet away are blocked. Start at 300–500 feet for most outdoor sites; tighten only after watching real-world punch patterns.

Geofencing remote rural sites with poor GPS. When employees are punching in from a field with no tall landmarks, GPS accuracy can degrade to 200+ feet. A tight radius on a remote site will create consistent false negatives.

Keeping geofencing on for office-based admins. If a payroll manager processes timesheets from the office and occasionally needs to punch in (to log their own hours), they'll be blocked unless the office address is a registered job site. Either add the office as a site or create a role-based exemption.

Forgetting to update coordinates when a project moves. A construction project that began at the foundation stage may physically move — utilities work across the street, staging area relocation. Outdated coordinates silently block employees who are doing exactly what they should be doing.

Not communicating the radius to employees. Employees who don't know why they're getting blocked at punch-in will work around it by calling a manager to manually override, or by standing in the parking lot trying different GPS fixes. A 30-second explanation of "you need to be within X feet of the site center" reduces support friction significantly.

Frequently Asked Questions

Does geofencing drain the phone battery? A geofence check at punch-in is a single GPS location request — not continuous GPS monitoring. The battery drain is equivalent to opening Google Maps for a few seconds. Continuous location tracking (where the app monitors your position all day) is a different category entirely and not what job site geofencing does.

Can employees punch in from a car in the parking lot? That depends on your radius setting. If you set a 300-foot radius and the parking lot is 100 feet from the building entrance, yes. If you've set a tight 50-foot radius around the entrance door, probably not. Design your radius based on where employees realistically are when they start work — often that's their vehicle, not the front door.

What happens when an employee is at a site with no GPS signal? If the device can't get a GPS fix, the punch-in attempt will either time out (and block with an error) or succeed after a longer wait if the app has a cached location from recent GPS activity. On iOS, Punch uses a "nearest ten meters" accuracy setting with a 60-second cache — so a recent location fix from the last minute counts. Employees in basements or parking structures will sometimes need to step outside briefly to get a clean fix.

Can I have geofencing on for some sites but not others? The geofence toggle in Punch is org-level (on or off for all sites), but you can achieve per-site behavior by simply not setting coordinates on sites where you don't want geofencing. Sites without lat/lng coordinates skip the distance check entirely, even when org-level geofencing is on.

Does geofencing work for remote workers? Remote workers who punch in from their home address aren't typically appropriate candidates for geofencing — you'd need to set up each employee's home as a job site with appropriate coordinates. Most businesses with remote workers either disable org-level geofencing entirely or handle remote work as a separate site category.

Is GPS location data stored permanently? Punch records the GPS coordinate at punch-in time as part of the time entry. This coordinate is stored with the shift record and visible in the shift detail view. It's not continuously sampled — just a single point at punch-in. Employees can see their own punch-in coordinates; managers can see coordinates for all shifts in their org.

Bottom Line

Geofence time tracking works best when it's applied narrowly: verify that employees are at a job site when they start, then get out of the way. Blocking punch-out or breaks based on GPS location introduces the wrong kind of friction — legitimate reasons to leave a site are common, GPS accuracy is imperfect, and the payroll risk of a blocked punch-out (an employee who can't end their shift) is worse than the fraud risk it prevents.

Set generous radii, leave punch-out unfenced, and use job sites primarily as a cost-center label even when geofencing is off. The combination of GPS verification at punch-in plus per-site shift records gives you both fraud protection and accurate project-level payroll reporting — without the operational headaches of trying to track employee location all day.

Set up your first job site free →