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
Capture is the desk and only the desk: a desktop app for Mac, Windows and Linux that records every actively used window — browser tabs, document names, email subjects, terminal titles — plus a free browser timer, and offline is genuinely the designed state rather than a failure mode. But I find no capture path beyond the desk — no mobile capture app, no shared terminal or badge reader, and no correction workflow with approval or any trace of who changed what, since users simply delete or rename tasks themselves. For field, site and shift crews we found no public information at all; the named segments are accountants, agencies, consultants, developers and the like. 2 3 4