Hours the gate can vouch for.
Gate-in and gate-out come from the site geofence, cost-coded to the activity the crew was dispatched to and confirmed against the morning's capture. One entry per shift, approved by exception — three or four a day on a 148-head job instead of 148 lines on a Friday.
What it does
A worker crosses the geofence and the shift opens; they cross it going home and it closes. The hour lands cost-coded to the activity their crew was dispatched to, so the timesheet, the plan and the cost report are one record read three ways rather than three spreadsheets reconciled on Friday night from memory.
What the foreman reviews is the exception list: a punch with no matching dispatch, a shift running two hours past the plan, a gate-in with no gate-out. Everything else is already right. When an hour is disputed, the gate capture from that morning settles it — the frame at 07:02 shows four men walking in, not six.
How it works
- 01
Punch at the fence
The site geofence opens and closes the shift on the phone in the worker's pocket. Punches queue offline for 72 hours and sync when signal returns, and gate kiosks with badge readers cover the crews who do not carry a company phone.
- 02
Code it to the work
The hour inherits its cost code from the crew's dispatch line, so labor lands against the activity that was worked instead of a default bucket. Re-scope a crew at 10:00 and the split follows them for the rest of the shift.
- 03
Approve the exceptions
Unmatched punches, overruns and missing gate-outs go to the foreman; the rest posts on its own. Every hour that reaches payroll carries the geofence event and the gate frame behind it, which is what makes a disputed line a six-minute conversation.
Spec
- PUNCH
- GEOFENCE · AUTO · KIOSK
- OFFLINE
- 72 H QUEUE
- CODING
- FROM DISPATCH LINE
- APPROVAL
- BY EXCEPTION · 3/DAY
3
Exceptions to approve on a 148-head day