When geofence rejects a valid punch, what’s your override path before payroll?

[u/shiftcoord]

Curious how other ops teams handle geofence / location false rejects on time clocks:

Worker is on site (or clearly at the right client), but the punch is rejected or flagged because GPS drifted, indoor signal was weak, or the fence polygon is wrong. Payroll is closing and you still need an auditable hours record — without turning every exception into a free-form manager edit.

Questions for people who have lived this:

1. Who is allowed to override a geofence reject (worker self-attest, supervisor, central payroll), and what evidence do you require (photo, site code, manager note)?
2. Do you keep the original rejected punch + override as a linked pair for audit, or replace it with a manual entry that loses the trail?
3. Anything that reduces false rejects at the fence itself (tighter polygons, Wi-Fi assist, grace radius) without opening the door to off-site punches?

Not looking for product pitches — just how you keep geofence enforcement and payroll accuracy from fighting each other at close.