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
Web, desktop, mobile and even a watch app are real, and timesheets carry an approve, reject and partial-approve workflow with clock actions visible in change history — more than a browser timer. But for my workshop wall and site crews I find no hardware terminal or badge reader, no GPS or geofenced check-in stated with limits, and the offline story is a free standalone timesheet positioned for a short period away from the main system rather than the main app syncing offline. 1 3 4 8 12