Time Tracking That Works Offline With GPS

No signal does not mean no record. Clox checks the geofence and saves each punch on the phone with its real timestamp, then syncs when the crew is back in coverage.

Your crew works where the signal does not. A finished basement with rebar overhead, a trench eight feet down, a new build with no cell tower for miles. If your time tracking only records a clock-in when the phone has bars, half your day goes missing and the other half gets punched in late from the truck on the way home. That is the exact problem people are searching for when they look for time tracking that works offline with GPS.

The question underneath the search is simple. If there is no signal at the punch, does the app still capture where and when the worker clocked in, or does it wait until coverage returns and record the wrong time and the wrong place? Those are two very different tools. This post walks through how Clox handles it, and it is honest about the limits.

What offline actually breaks in most time trackers

GPS and cell signal are not the same thing. A phone can get a location fix from satellites with no cell coverage at all. The part that needs signal is sending that punch to a server. So the failure in most apps is not that the phone cannot find itself. It is that the app will not save anything until it can talk to the server.

That leads to two bad outcomes. Either the worker cannot clock in at all until they walk back into coverage, or the app records the punch at the moment it finally syncs, which is minutes or hours after the real start. Both quietly rewrite the timesheet.

How Clox handles an offline punch

In Clox, the geofence lives on the phone at punch time, not only on the server. A manager draws a radius around a worksite on a map, with a sensible default around 200 meters that you can adjust per site. When a worker taps clock-in, the phone reads its own GPS fix and checks it against that radius right there, offline or not.

If the check passes, the punch is written to the phone immediately, stamped with its real timestamp from the moment of the tap. It sits in a local queue. When the phone gets signal again, whether that is climbing out of the trench or driving back into town, the queued punch syncs to your dashboard with that original time and location intact. Offline does not mean untracked. It means stored now, sent later.

Because the geofence is evaluated at the tap and not at sync, the location decision reflects where the worker actually was when they clocked in. A punch that syncs three hours later from a parking lot with full bars still carries the trench location and the trench time.

The geofence still blocks off-site punches offline

Enforcement is per employee, so you turn it on only for the crews it fits and leave it off for people who bounce between sites all day. For a worker it is enforced on, a clock-in from outside the fence is blocked at the punch, and that block happens on the phone. It does not depend on the server, so it holds even with no signal. The off-site punch is never created in the first place. Most tools only warn after the fact. Clox blocks up front.

The accuracy grace, and what gets flagged

GPS is never exact, and it is worse under concrete and steel. So a punch that lands just outside the radius can still go through if it falls within the phone's own reported accuracy, capped at 100 meters. Those allowed-but-marginal punches are not swept under the rug. They are flagged for you with an "Off the worksite" readout to review at approval, so you decide, not the algorithm. A fix too coarse to trust, worse than about 500 meters or wider than the fence itself, is rejected as too inaccurate rather than guessed at.

At approval you also see three review flags, in priority order:

• mock_location: the device reported a fake or mock GPS provider, the strongest sign someone is spoofing their position.
• impossible_travel: the punch is impossibly far from that same worker's previous punch, given the time between them.
• low_accuracy: a coarse but in-fence fix worth a second look.

Where the location comes from, plainly

Here is the honest part, and it is the same honesty this whole cluster is built on. The location Clox records comes from the worker's phone. It is a strong deterrent, not a guarantee. Geofencing is not foolproof and it is not tamper-proof. Someone determined enough can try to fake a device's GPS, which is exactly why the mock_location flag exists and why blocking, accuracy caps, and review flags work together instead of trusting a single reading.

Treat geofencing as a firm fence that stops the easy, casual off-site punch and surfaces the suspicious one for a human to check. It removes the arguments about whether someone was on site. It does not replace knowing your crew. Any tool that promises a tamper-proof location from a phone is overselling it.

Common objections about going offline

If the punch is stored on the phone, can a worker change the time later?

The timestamp is captured at the moment of the tap and travels with the queued punch. Combined with the impossible_travel and mock_location flags, an edited or faked device state is the kind of thing that surfaces for you at approval rather than sliding through silently. You are reviewing what the phone reported at punch time, not a value the app quietly reconstructed at sync.

What if a worker forgets to clock in until they have signal again?

That is a habit problem, not a signal problem, and it is the same in any system. The point of offline capture is that lack of signal is never the reason for a missing or wrong punch. The tap works the moment they remember, on site, with the real location, whether or not there are bars.

Does the phone drain the battery hunting for GPS in a dead zone?

The location is read at the punch, not held open all day. A worker taps, the phone gets a fix and checks the fence, the punch is saved, and that is it. There is no continuous tracking running in the background between clock-in and clock-out.

The rest of the timesheet keeps working too

Offline GPS is one piece. Clox is time tracking for field crews across the board. One tap to clock in, overtime and breaks calculated automatically, and payroll-ready exports for QuickBooks, Gusto, ADP, and Paychex. The offline punches you captured in the trench flow into the same reports and the same export, with no manual re-entry when the crew gets back to coverage.

If you want the full breakdown of how the fence itself is drawn and enforced, the pillar guide covers it, and there is a companion piece on the mechanics of geofenced time tracking below. You can compare plans on our pricing page, or start a free trial and put a fence around one job site to see how the offline punches land.