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
Timer, desktop, mobile and even a watch are capture paths, and corrections run through an approval workflow with the clock-in, clock-out and break actions visible in a change history — that part I can co-determine with. But the offline story is a free offline timesheet for time away from the main system rather than a designed offline state, and we found no public information on a shared terminal, on bulk correction, or on GPS or geofenced check-in and what it stores, so I cannot judge what the system would watch rather than measure. 1 4 8 12