Geofencing for Time Tracking: A Practical Guide

The Hours You Never See

Most of the hours you pay for look fine on paper. An employee clocks in at 8:03, clocks out at 16:58, and the timesheet adds up. Revenue comes in from the client at the contracted rate. Payroll runs. Everyone goes home.

But if you are paying for work on a specific jobsite — a construction project, a client office, a warehouse, a hospital — the timesheet only tells you half the story. It says when someone worked. It does not say where.

For a lot of businesses that distinction doesn't matter. For a lot of others, it's the whole game.

What Geofencing Actually Is

A geofence is a virtual boundary drawn on a map. Your time tracker uses the employee's GPS location at the moment they clock in to check whether they are inside that boundary. If they are, the clock-in is allowed. If they aren't, it is either blocked, flagged for review, or silently logged for compliance — depending on how strict your policy is.

That's it. No satellites following your employees around all day. No background tracking. The employee's location is captured once at clock-in and once at clock-out, compared to the fence, and then nothing happens until the next clock event.

Where It Earns Its Keep

Four patterns cover most real-world use cases.

Construction and job sites. A framer does not need to clock in from the truck yard or from home. The site has an address. Draw a polygon around the site — irregular shapes are fine, that's what polygons are for — and the clock-in only fires when the crew is actually there. When the project ends, the fence goes away with it.

Multi-office companies. A consulting firm with offices in Vancouver, Calgary, and Toronto doesn't want employees clocking into "Vancouver office" from their couch. One fence per office, all assigned org-wide, and the time entry records which office the clock-in actually matched. Now your occupancy reports are honest.

Field services. Technicians who bill client visits by the hour. The job happens at the customer's address, not on the way there. A fence per client site, assigned to the specific project, means billable time doesn't start until the tech is on-premise. Your invoices match reality and your client trusts your bills.

Healthcare and shift work. A hospital campus with specific buildings. A clinic with parking shared by three businesses. Labour regulations often require that shift time is counted from the moment the worker is at their station, not when they scanned their key card at the perimeter. A polygon fence around the correct building enforces that without anyone having to manually police it.

Circle or Polygon?

The two shapes handle almost everything.

A circle is a centre point plus a radius. Simplest possible fence. Good for a single-building office, a small warehouse, a standalone retail location. Ten-metre radius for a tiny site, 500-metre radius for a large campus. You pick the centre on a map, drag a handle to set the radius, you're done in 30 seconds.

A polygon is an ordered list of vertices. More work to draw, much more precise. Use it when the site has a shape — a construction zone spanning half a city block, a U-shaped hospital that doesn't fit neatly into a bounding circle, a delivery depot that wraps around a parking lot the public can access.

Most teams start with circles because they are faster to draw, and convert the few that matter to polygons over time. Neither is objectively better. They serve different geometries.

Three Modes — A Rollout Strategy

Geofencing adoption fails when it goes from "off" to "block everything" overnight. Your GPS fences will have edge cases you did not anticipate. An employee whose office sits right on the fence boundary. A warehouse back door that puts workers 20 metres outside the polygon. A mid-tier Android phone that reports 200-metre accuracy on a cloudy day.

The better way is three modes, in sequence.

Start in LOG_ONLY. No employee-visible change. Every clock-in proceeds normally, but the system records whether the location fell inside or outside the fence. After two weeks you have real data on how well your fences cover the work that actually happens. Now you know which ones to redraw, which sites need a polygon instead of a circle, and which employees are doing legitimate work 30 metres outside your boundary because that's where the shaded break area is.

Graduate to OPTIONAL. Clock-ins still succeed, but out-of-bounds attempts are flagged on a compliance dashboard. The employee experience is unchanged; managers start reviewing flagged entries weekly. This is where you build trust in the system before it starts saying no.

Switch on REQUIRED. Now out-of-bounds clock-ins are blocked with a clear rejection modal showing the nearest allowed site and the distance to it. Use this once your fence coverage is solid and you have a process for employees who genuinely need to work off-site (a remote exception assignment, a temporary override).

The trap is skipping the first two phases. The cost is a week of angry Slack messages from people whose clock-ins mysteriously fail. Don't do it.

Whose Fence Wins

A single fence can apply to different targets — the whole organization, a single department, a specific user, or a specific project. When an employee clocks in, the most specific match wins.

Start at the top: if the project they're clocking into has its own fence, that fence applies. If not, does the user have one assigned to them directly? If not, their department? If not, the org-wide default? That's the resolution order, and it matches how most enterprise HRIS tools handle location policies.

In practice it means you can set a sensible org-wide default ("all clock-ins must come from one of our three offices") and then override it per project for edge cases ("Q4 Warehouse Build is on-site only") and per user for remote exceptions ("Sarah works from home on Fridays"). The four levels of scope cover almost every policy you'd want to express.

What About GPS Accuracy?

This is the question everyone asks second, right after "can I use polygons?". The short answer is: you can't trust a single GPS fix to the metre, so geofencing has to be tolerant of that by design.

A good implementation does three things. First, it captures the accuracy of the reading alongside the position itself — most browser and OS location APIs return this. Second, it treats the effective allowed area as the fence radius plus a configurable tolerance plus the accuracy of the individual reading. A 50-metre GPS fix inside a 100-metre fence is obviously inside; a 200-metre GPS fix just barely outside a 100-metre fence is ambiguous, and the tolerance-plus-accuracy math treats it as inside. Third, it rejects readings whose accuracy is worse than a configurable threshold — a 5-kilometre fix is not useful for enforcement, so the clock-in fails with a specific "GPS too weak" message that tells the employee to move near a window.

The net effect is that mobile-web GPS, which is routinely 50-200 metres noisy, still works reliably for a 100-metre office fence. Not by pretending the noise isn't there, but by accounting for it at check time.

Privacy and Trust

Geofencing can slide into creepy territory fast if you let it. The guardrails are simple and should be non-negotiable.

Capture the location only at clock events. Not in the background. Not continuously. Not when the app is closed. Employees should be able to open the app, work, close it, and only when they tap Clock In does their location get read. That's the whole lifecycle.

Store the result, not the history. A single lat/lng on the time entry, tied to the clock-in/out you just performed, is sufficient for compliance. You do not need a minute-by-minute trail of where the employee was during the shift. You need to know where they were when they said they were working.

Be transparent about what's enforced. If geofencing is on for a team, tell that team. Show the employee, before they tap the button, what fence they are being checked against and whether they currently pass. The "live status banner" pattern — green when inside, amber when outside, with the name of the nearest allowed site — turns a system that could feel like surveillance into one that reads as "here's the information I need to do my job."

Enforcement without transparency is surveillance. Enforcement with clear, contextual feedback is just a workflow.

Offline Workers

One last problem. Your field crews sometimes work where there is no cellular signal. A construction site in a basement. A client building with bad reception. A delivery route through a mountain pass. The clock-in has to work anyway.

The pattern most mobile-native workforce apps converge on is an offline queue. The app captures the clock event locally, including the timestamp and the last known GPS fix, and queues it. When the device comes back online, the queued event replays against the server with the original timestamp and location. A sensible drift tolerance (say, up to 24 hours into the past and 15 minutes into the future) prevents abuse.

Not every workforce tool handles this. The ones that don't tend to have a ticket queue full of "my clock-in didn't save" support requests. If your team genuinely works off-grid, ask about offline behaviour before you buy.

How BookYourPTO Does It

All of the patterns above are how the BookYourPTO geofencing feature is built. Circles and polygons from a single editor. Three modes — LOG_ONLY, OPTIONAL, REQUIRED. Four scope levels with the most-specific-wins resolution. Accuracy-aware distance checks with configurable tolerance and max-accuracy thresholds. A live status banner on the employee clock-in screen. An offline-queue timestamp protocol on the mobile API. A compliance dashboard with CSV export and a full audit trail of every fence change and every blocked attempt.

It is available on every plan that includes time tracking, works with both Google Maps and OpenStreetMap (no lock-in to one vendor's key), and takes about a minute to set up your first fence.

Start a trial at bookyourpto.com, or read the feature details at /geofencing.