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
Desktop, mobile and browser apps plus geofenced GPS start and stop give desk and field crews several ways to record, and timesheets can be edited, approved and then locked. But every capture path runs on the employee's own device — with background tracking on Android — and we found no public information on a shared terminal, on offline capture, or on bulk correction with a change history. As the body that co-determines monitoring, I note that GPS and background location are marketed as features with no stated storage limits. 1 2 3 4 11 12