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
Browser, the app in single- and multi-user mode and a separate hardware terminal cover desk, deskless and site crews, with bookings stored locally offline and synced when the connection returns. GPS is off by default, records a position only per stamp event, and the vendor states plainly that it documents where a stamp came from rather than fencing a radius — the honest answer a works council needs. We found no public information on an audit trail for corrections: administrators can edit times, but nothing public says who changed what, when, or whether a change is reversible. 1 5 6