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 Operations Lead
This is the part that fits my workforce: robust badge terminals rated for cold rooms and high-pressure cleaning, smartphone badging for short-term staff, PC or phone declaration for the office, geolocated clocking for mobile crews, and terminals that keep storing events through an outage and can sync standalone via USB. What holds it back is corrections: we found no public information on bulk correction or an audit trail showing who changed a time entry, and the stated geolocation purpose comes without stated limits. 1 2 3