“GPS verified” sounds like a binary answer: the worker was there or was not. Location technology does not work that way. A phone reports a position estimate, a radius or accuracy value, and a timestamp influenced by satellites, cell networks, Wi-Fi, device settings, building materials, and the surrounding environment. A serious time-clock policy explains that uncertainty instead of hiding it behind a green pin.
The practical question for a field-service company is whether the evidence is good enough for the decision being made. A location estimate may help associate a punch with a building, but it should not be treated as proof of every task, a basis for an automatic wage deduction, or a precision guarantee indoors. StockPoint uses photo plus building PIN plus GPS-with-honest-accuracy because several imperfect signals are more informative when their limits remain visible.
The DOL Fact Sheet on hours worked makes a separate point that matters here: time records support an employer’s duty to count compensable work. A GPS tool is an attendance aid, not a substitute for paying for required work, reviewing edits, or investigating a complaint. The best policy tells workers how the system works, how to report a failed signal, and how corrections are approved.
What a phone location reading can and cannot say
Outdoor satellite positioning can be useful, but the reported accuracy is an estimate, not a courtroom measurement. In open conditions a device may show a small accuracy circle; around tall buildings, under heavy cover, or near reflective surfaces the estimate can worsen. Indoors, the phone may rely more heavily on Wi-Fi or cell-assisted positioning, and the result can be less specific than a user expects.
A company should display the accuracy value and timestamp with the punch. A reading that says the device estimated a 12-meter radius communicates something different from one with a 150-meter radius. StockPoint’s honest-accuracy approach is deliberately less dramatic than claiming that every map dot identifies an exact room. The record can still be useful when paired with a building PIN, assignment, photo, and supervisor review.
The record should also distinguish device location from worker identity. A phone can be shared, a device can be left in a vehicle, and a worker can select the wrong assignment. PINs, worker authentication, assignment restrictions, and exception review address those risks; none is perfect by itself. The point of a verification stack is to make a false explanation harder while preserving a fair path to correct a genuine device problem.
Why a 200-foot geofence is not a presence guarantee
A geofence is a rule applied to a location estimate. If the circle or radius is broad, a worker may be allowed to punch from a neighboring property; if it is narrow, a legitimate worker may fail to punch near a building entrance. The result depends on the building layout, the device reading, and the policy, not just the number of feet entered in an admin screen.
Imagine two buildings separated by a parking lot and a loading area. A 200-foot radius around Building A may overlap the lot and part of Building B, especially if the device’s own accuracy circle is larger. Treating the resulting green status as exact would create false confidence. A better workflow records the estimated accuracy, requests the building-specific PIN, and asks for a work-related photo or checkpoint when appropriate.
Geofences should be tested during the actual shift, with the devices and entrances workers use. Document where the rule fails, how supervisors handle a blocked punch, and whether the system captures the original attempt. StockPoint can keep the attempted event and the approved correction in an audit log, so a connectivity or location issue is explained rather than silently converted into an absence.
The verification stack that survives real buildings
A useful stack starts with a worker signing into the assigned shift and selecting the correct building. The system records the time, the location estimate and accuracy, and a building PIN or equivalent shared-secret control. A photo or checkpoint can document a selected condition of the work, while the supervisor resolves exceptions and closes the record without deleting the history.
Each layer answers a different question. Identity asks who submitted the event; time asks when; assignment asks which job; PIN asks whether the person had a building-specific code; GPS adds contextual location; photo or checkpoint adds limited evidence of work condition. StockPoint connects these inputs to per-building punches, which lets a manager review a particular visit instead of a worker’s entire day as one undifferentiated line.
Privacy and proportionality matter. Location collection should be limited to the work event or another defined operational purpose, access should be role-based, and the company should explain retention and review. EEOC guidance on employment records and state privacy rules may affect a company’s policy; when a business operates in multiple states, it should have counsel validate the notice and monitoring language rather than copying a generic template.
GPS evidence and wage-and-hour records are different systems of meaning
A worker who is inside a building preparing equipment may be working even if the phone has not produced a usable location estimate. A supervisor who asks for a text after clock-out may create compensable work even though the time clock is closed. The employer must correct the record and pay lawful wages; an app cannot make an uncompensated task disappear.
For that reason, never configure a GPS failure as an automatic unpaid absence. Route the event to a correction workflow that records the worker’s explanation, the supervisor’s decision, and any supporting evidence. StockPoint’s per-worker payroll locking helps prevent the same approved time from being paid twice, but payroll locking is not permission to reject time that was actually worked.
A client portal can show proof-of-work photos and live checkpoint status without exposing a worker’s full location history. That separation is useful when a facility manager needs service evidence but does not need employee-level monitoring details. It also lets a contractor use the same verified punch for cost-plus billing, payroll preparation, and job-cost analysis rather than exporting different versions to different systems.
How to write an honest GPS policy
Start by saying what the system records and when. Explain that GPS is an estimate with an accuracy value; it may be degraded indoors or near obstructions; a failed reading is handled through an exception process; and workers can report a wrong assignment, device issue, or unsafe condition. State who reviews data, how corrections are logged, and how long records are retained under the employer’s legal and operational obligations.
Train supervisors not to promise certainty that the tool cannot deliver. “The map says you were not there, so you will not be paid” is both a poor management practice and a wage risk. “The punch has a large accuracy radius; please confirm the building PIN and tell us what happened” is a reviewable process. The difference is not just tone; it is whether the company can distinguish evidence from inference.
For a field-service operator, the decision standard should be simple: use the least intrusive combination of evidence that reliably supports scheduling, quality, invoicing, and payroll. Read the time and attendance features and the article on off-the-clock work claims before setting a policy. A system is trustworthy when it admits uncertainty and still gives a supervisor a clear next action.
Accuracy is a product and management decision
The record should be understandable to the worker who created it. Showing a map without the accuracy radius invites a manager to overread the evidence, while showing only an error code leaves the worker with no path to fix it. A bilingual explanation of the punch, the failed signal, and the correction route is a practical control: it improves the quality of the next event and makes a later review less dependent on translation or memory.
Do not evaluate accuracy only from the office. Test at the actual entrance, stairwell, loading dock, basement, and interior areas where crews begin work. Repeat the test with the common phone models and with ordinary weather and network conditions. Record the observed failure modes and set a correction service level. If a building routinely blocks location, the right answer may be a PIN, supervisor confirmation, or another access control rather than an ever-smaller geofence that rejects legitimate work.
A location record is most persuasive when the company is equally willing to consider evidence that contradicts it. If a worker has a verified building PIN, a time-stamped completion photo, and a supervisor confirmation while GPS reports a large radius, the manager should review the complete event rather than defaulting to the map. This is not leniency; it is evidence discipline. It prevents a low-quality signal from becoming a low-quality payroll or client decision.
A supervisor can use a short evidence hierarchy for a disputed event. First confirm the assigned building and worker, then review the time and accuracy radius, the PIN result, any photo or checkpoint, and the worker’s explanation. Compare the event with access or shift context only when the company is permitted to do so. Record the conclusion and the reason. This creates a repeatable decision instead of a manager’s personal instinct about whether a dot looks convincing.
Put the evidence to work
The most defensible GPS time clock is not the one with the most confident language. It is the one that records the accuracy estimate, combines location with identity and building context, supports photos or checkpoints when they are appropriate, and keeps corrections visible. That design helps the contractor answer a client’s service question without turning a weak signal into a payroll penalty.
StockPoint provides per-building punch verification with photo, PIN, and GPS-with-honest-accuracy, plus bilingual workforce surfaces and an audit trail. It does not claim GPS can prove an exact indoor position or every completed task. Sign up at getstockpoint.com to give your team a practical verification workflow that respects the limits of location data while producing records a supervisor can actually use.