GPS Time Tracking That Blocks Off-Site Clock-Ins

You do not want a report that tells you someone clocked in from their driveway. You want the punch stopped before it happens. Here is how Clox blocks an off-site clock-in at the punch, when a marginal punch is still allowed, and what gets flagged for you to review.

You are searching for this because a warning is not enough. You already know a crew member can tap the clock-in button from their truck, their driveway, or a job across town. What you want is software that stops the punch before it ever lands, not a note after the fact that you have to chase down on Friday.

There is a real difference between an app that warns and an app that blocks. A warning still creates the punch. Someone still has to notice it, question it, and decide whether to fix it. A block means the off-site clock-in never gets created at all. Clox blocks.

This post walks through exactly how that works: the block itself, the grace built in for GPS drift, and the flags you see at approval. It also covers the honest limits, because the location comes from a phone and no honest tool pretends otherwise.

Warn versus block, and why it matters

Most GPS time tracking tools take the punch first and ask questions later. The worker clocks in, the app records the coordinates, and if the location looks wrong you get a flag or a colored dot on a report. The time entry is already in the system. Now the burden is on you to catch it, ask about it, and correct payroll before it goes out.

Clox works the other way around for anyone you enforce it on. The geofence is checked at the moment of the punch. If the phone reports a location outside the worksite radius, the clock-in is refused. No time entry is created. There is nothing for you to catch later, because the off-site punch was never allowed to exist.

How the block actually works

You start by drawing the fence. In Clox, a manager opens a worksite on a map and sets a radius around it. The default lands around 200 meters, which suits most job sites, and you can widen or tighten it per worksite. A tight downtown lot and a sprawling development get different radii because you set each one yourself.

Enforcement is per employee, not blanket. You choose which crews the fence applies to. A framer who stands on one site all week can be enforced hard. A service tech or a foreman who hits five addresses a day does not have to fight a fence at every stop. That choice is yours, worker by worker, so the block lands where it helps and stays out of the way where it would only cause friction.

When the fence is enforced for a worker and they try to clock in from outside it, the punch is blocked on their phone. They see that they are off the worksite. No entry syncs to you, because none was created. This is the core of what you searched for: the off-site clock-in is stopped at the source.

The accuracy grace, so real work does not get blocked

A hard fence with no give would punish honest workers. Phone GPS drifts. A worker standing well inside the fence can have their phone report a position that lands just past the line. Blocking that person would be wrong, and they would start to distrust the whole system.

So Clox builds in a grace. A punch that falls just outside the radius can still be allowed if it lands within the phone's own reported GPS accuracy, capped at 100 meters. The worker gets to clock in and keep working. But that punch is not treated as clean. It is flagged for you with an "Off the worksite" readout, so you can glance at it during approval and decide for yourself.

There is a floor on trust, too. If the phone's fix is too coarse to mean anything, worse than about 500 meters or wider than the fence itself, Clox rejects it as too inaccurate. A location that vague cannot honestly say whether the worker is on site or three blocks away, so it does not get to pass.

The three flags you see at approval

Some punches are allowed through but deserve a second look. Clox shows you three review flags at approval, in priority order, so you know what you are looking at without digging.

1. mock_location: the device reported a fake or mock GPS provider. This is the strongest signal that someone is trying to spoof their position, and it sits at the top for a reason.
2. impossible_travel: the punch is impossibly far from that same worker's previous punch. If the last clock-out was across the county a few minutes ago, the math does not hold up.
3. low_accuracy: a coarse but in-fence fix. The worker appears to be inside the fence, but the reading was loose enough that you may want to confirm.

These flags do not block on their own. They inform. You stay the decision-maker at approval, with the context in front of you instead of buried in a coordinate dump.

The honest limits

Here is the part some vendors will not say plainly. The location comes from the worker's phone. That makes GPS geofencing a strong deterrent, not a guarantee. It raises the effort and the risk of clocking in from the wrong place, and the block plus the flags make casual gaming pointless. But it is not foolproof, and anyone who tells you their geofence is tamper-proof is selling you something.

What Clox does is stack honest defenses. The punch is blocked outside the fence. Marginal punches are graced but flagged. A mock GPS provider is caught and raised to the top of your review. An impossible jump between two of the same worker's punches is called out. None of these is a single unbreakable wall. Together they make an off-site clock-in far more trouble than it is worth, and they put the evidence in front of you when something looks off.

Common objections, answered straight

Will this block my foreman who drives between five sites a day?

Only if you enforce it on him, and you would not. Enforcement is per employee. Turn it on for the crews who hold one site and leave it off for the people who move all day. The block is a tool you point where it helps, not a blanket that catches everyone.

What happens to a worker with no signal on a remote site?

They still clock in. The geofence check runs on the phone at punch time, and the punch is stored locally with its true timestamp. When signal comes back, it syncs. A dead zone does not become an excuse to lose the punch or skip the fence.

Will honest workers get blocked by a jumpy GPS reading?

That is exactly what the accuracy grace is for. A punch just outside the line still lands if it falls within the phone's reported accuracy, up to 100 meters, so the framer standing at the fence line is not locked out by drift. It gets flagged for your review, not refused.

Can someone fake their location?

They can try, and this is the honest answer. A mock GPS provider is one of the more common tricks, which is why mock_location is the top review flag. It does not block automatically, but it puts the punch at the front of your queue with a clear label. Combined with the impossible-travel check, faking a location is far riskier and far more visible than it is on a warn-only tool.

Where the block fits in the rest of the app

Blocking off-site clock-ins is one feature inside a full time-tracking app for field and trade crews. Clox is one-tap clock-in, with overtime and breaks calculated automatically and payroll-ready exports for QuickBooks, Gusto, ADP, and Paychex. The geofence is there to keep the timesheet honest before it ever reaches payroll.

You can see the full picture of the geofencing side in our geofencing pillar guide, and the wider field-crew workflow in our field crews guide. If your real worry is padded hours in general, our piece on how to spot and stop time theft covers the patterns beyond location.

Getting started is low-commitment on purpose. You get 14 days free with no credit card to start, and a 30-day money-back guarantee if it does not fit your crew. See pricing or create an account and draw your first worksite. The iPhone app is on a TestFlight beta, and anyone can also clock in from a phone browser at app.getclox.com.