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, manual entry, weekly timesheets, mobile and a shared kiosk with QR sign-in cover the capture paths a mixed workforce needs, offline time syncs on reconnect, and entries can be edited and submitted for approval. My concern is what the location features actually record: GPS tracking and "See visited sites and routes" are sold with no statement of what is stored, who can read an individual's day, or how a council could switch it off, and the log of who changed an entry only appears in the top plan's feature list. 1 1 2 3 4