Capture in the real workplace
How this is scored
How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.
0 — One browser timer and nothing else; anyone away from a desk records nothing.
3 — Web plus a mobile app, but no offline capture, no shared terminal, and corrections are an admin task rather than a workflow.
5 — Web, mobile and at least one shared capture point (kiosk, terminal or badge), with offline capture that syncs, and a correction workflow with approval.
8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.
10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.
The Works Council Advocate
Capture is documented across terminals, the GFOS app, and smartphones or tablets that can stand in as a shared terminal with multi-user login by employee ID and PIN or QR code, plus offline capture that stores locally during network outages and syncs when the server returns. Corrections run through a defined correction process rather than free editing, which I welcome. GPS recording must be explicitly activated before it is booked with the time data, but we found no public information on what the GPS record stores, who may read an individual's day, or an audit trail showing who changed what. 4 5 8