GPS Time Tracking for Field Workers: How It Works (and the Privacy Question)

Every operator I talk to wants the same two things from GPS on a time-tracking app: proof the crew was actually on the job site, and zero risk of a wage-and-hour or privacy lawsuit. Both are achievable. Most operators just have the implementation backwards.

In the field, the question isn’t should we use GPS — at this point, paper logs and honor-system clock-ins lose to GPS-verified entries every time a labor dispute hits a courtroom. The question is how do we use GPS so it’s defensible. That’s a compliance question more than a technology question, and it’s the part most articles on this topic skip.

Here’s how GPS time tracking actually works for field workers, where the privacy line sits, and what to demand from any vendor before you roll it out to your crew.

What does GPS time tracking actually record?

A well-designed field time tracking app does not stream your crew’s location continuously. That would be a privacy nightmare, a battery disaster, and a legal liability all at once. Instead, modern GPS time tracking records location at specific events:

1. Clock-in — one GPS point captured the moment the worker taps the clock-in button
2. Clock-out — one point at end of shift
3. Break start / break end (optional) — bookends paid vs unpaid time
4. Geofence entry/exit (optional) — passive confirmation crew arrived and left
5. Crew Clock batch entries — one point for the foreman, applied to the whole crew

That’s it. There’s no continuous “GPS breadcrumb trail” unless the operator explicitly opts in to route tracking (which most don’t, and shouldn’t, for indoor crews like cleaning or HVAC service).

Klees stores those event points with a timestamp, a worker ID, and a job-site ID. The data lives behind authentication, retained per your industry’s recordkeeping rules, and accessible to the worker on request — three things the U.S. Department of Labor’s recordkeeping guidance requires regardless of whether you use GPS or paper.

How does a geofence verify a job site?

A geofence is a virtual circle around a known job-site coordinate. When a worker tries to clock in, the app checks whether their phone’s current GPS reading falls inside that circle. If yes, clock-in proceeds. If no, the app either blocks the clock-in or flags it for the supervisor.

The geofence radius matters more than most operators realize:

Site type	Recommended radius	Why
Single building (commercial cleaning, office HVAC)	50–75 meters	Tight enough to prevent off-site clock-in from a parking lot
Standard residential job (roofing, painting)	100 meters	Accounts for GPS drift in dense neighborhoods
Large construction site	200–300 meters	Covers active staging, lay-down, and the building footprint
Multi-building campus (hospitals, schools)	Use multiple smaller geofences	Cleaner per-site reporting than one giant fence
Linear job (road work, fencing)	Geofence each segment	Avoid a 2-mile-wide circle

A geofence that’s too tight creates false rejections every time GPS drifts. A geofence that’s too wide lets a worker clock in from the gas station down the street. The Klees geofence tool defaults to 100 m and gives the supervisor one-tap adjustment per site, which solves the trade-off without making it a science project.

The privacy question: where’s the legal line?

This is where most articles get vague and most operators get nervous. The actual legal line, in U.S. labor law, is clearer than it looks. Three rules cover almost every state:

1. GPS tracking during work hours, on company time, with disclosed business purpose: legal in all 50 states. Job-site verification, accurate payroll, OSHA recordkeeping — all defensible business purposes.
2. GPS tracking off the clock: high risk. Several states (California, Illinois, New York, Texas, Connecticut, Delaware) have specific statutes restricting employer GPS use or requiring written notice. The safest implementation stops GPS the second the worker clocks out.
3. Personal-device GPS without written consent: very high risk. If you require workers to install the time-tracking app on their personal phone, you need a written, signed consent acknowledging the GPS use, the purpose, and the on-the-clock-only scope.

The most common mistake I see: operators buy a tracking app that runs GPS continuously on personal phones with no consent paperwork. That’s the configuration that gets sued. The fix is a vendor that supports event-triggered GPS, a clear written GPS policy, and an opt-out path for workers who provide their own device.

What about battery drain?

The single fastest way to lose crew adoption is an app that kills their phone battery by lunch. Continuous GPS streaming drains 15–25% of a modern smartphone battery over an 8-hour shift. Event-triggered GPS — the model Klees uses — runs at 2–5% across the same shift, indistinguishable from normal background usage.

The math:

1. Continuous GPS: Up to ~3% per hour. Over an 8-hour shift, 20%+ of battery.
2. 1-minute polling: ~1% per hour. Over a shift, 6–8%.
3. Event-triggered (clock-in, clock-out, geofence boundary only): Negligible. Most workers see no measurable difference.

If your vendor can’t tell you which model they use, assume continuous and walk.

What does the supervisor actually see?

A common worker concern: is the boss watching me on a live map all day? On Klees, the answer is no — the supervisor sees crew-level location at meaningful events, not a real-time dot moving down the highway.

The Live Map in Klees shows:

• Where each worker is clocked in right now (point on map at last clock-in or geofence event)
• Whether the worker is inside or outside the assigned job-site geofence
• A historical trail of clock-in / clock-out events for the day, not continuous movement

That’s enough for a dispatcher to redeploy a crew, confirm a worker made it to a site, or pull a clean record for a customer dispute. It’s not a stalking tool. The distinction matters legally, and it matters for crew trust.

For the full mechanics, see the Live Map feature page and the Alta Janitorial case study — Alta runs Live Map across 5 Western states with hundreds of sites and the same event-triggered model described here.

How does GPS pair with selfie verification?

GPS confirms where the clock-in happened. It does not confirm who tapped the button. A worker can hand a phone to a friend, or clock in from inside the geofence and then leave for the day. To close that loop, you need an identity check at clock-in.

That’s what PinShot does. At clock-in, the app takes a quick selfie, runs an anti-spoof score (it detects a photo-of-a-photo and rejects it), and attaches the verified image to the time entry. The full PinShot anti-spoof flow is documented at Why Klees, and the broader features overview shows how PinShot, GPS, and Crew Clock work together.

The combination — geofenced GPS at clock-in, plus a verified selfie at the same moment — produces a time entry that holds up in a wage dispute, a customer SLA challenge, or an internal time-fraud investigation. Without both, you have half a record.

Compliance checklist before you turn on GPS

Before you flip GPS on for your crew, run this list:

1. Written GPS policy distributed to every employee, in their primary language
2. Acknowledgment signed by each worker (paper or digital, dated)
3. Policy states: business purpose, on-the-clock-only scope, retention period, employee right to access
4. State-specific notice where required (CA, IL, NY, TX, CT, DE — verify your state)
5. Vendor confirmed to use event-triggered, not continuous, GPS
6. Geofence radius set per site type, not a one-size default
7. Supervisor training on what the Live Map shows and what it doesn’t
8. Recordkeeping retention configured to your industry minimum (FLSA: 3 years for payroll; longer if you have prevailing-wage exposure)

Operators who run this checklist before rollout report near-zero pushback from crews and near-zero exposure on the legal side. Operators who skip it — well, that’s where the lawsuits come from.

FAQ

Is GPS time tracking legal in California?

Yes, with conditions. California Labor Code §980 and related privacy statutes require employers to provide written notice of GPS tracking and to limit collection to on-the-clock hours when the device is personal property. A signed acknowledgment and a configured event-triggered system keeps you compliant.

Can a worker refuse GPS clock-in?

A worker can refuse to install the app on a personal device. The standard response: provide a company-owned device (tablet kiosk, shared phone) for that worker. You generally cannot compel personal-device GPS, but you can require GPS-verified clock-in on a company-provided device.

How accurate is smartphone GPS for job-site verification?

Modern smartphones are accurate to roughly 5 meters in open sky, 10–20 meters near tall buildings, and degraded indoors. The 100-meter default geofence in Klees absorbs that drift. For indoor-heavy work (cleaning, HVAC service inside buildings), pair GPS with a tablet kiosk at the site entrance.

Does GPS work offline?

GPS hardware works without cell signal — the satellites don’t need internet. The time-tracking app caches the clock-in locally and syncs the GPS point when the phone reconnects. Klees supports offline clock-in for crews on remote sites and uploads the queued entries when service returns.

What’s the retention period for GPS time records?

FLSA requires 3 years for basic payroll records. Prevailing-wage and Davis-Bacon projects often require longer. Klees defaults to 7 years to cover the worst-case audit window, and the retention period is configurable per account.

---

Want a GPS policy template and a geofence-radius worksheet for your crew? Get in touch and Klees field-ops will send the same checklist Alta Janitorial used before they rolled out across 5 states.