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 Field Supervisor
Offline is a designed state here, not a failure mode: bookings store locally when the server is unreachable and sync on return, any phone or tablet becomes a shared terminal with PIN or QR login for several workers on one device, and stationary terminals are named as the alternative, on top of iOS and Android apps with QR-code cost-centre switching. GPS capture is opt-in; I found no public information on its limits, and none on bulk corrections with an audit trail of who changed what. 4 5 8