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 — Not a time-recording tool; working time cannot be captured in the product.
3 — Clocking in and out or a timer in the browser or an app, with manual entries; offline use, shared terminals and corrections are basic or not described.
5 — Web and mobile apps for clocking in and out, a shared kiosk, terminal or badge option or offline capture that syncs, and corrections requested by the employee and approved by a manager.
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
Automatic capture runs quietly in the background across web, Windows, macOS, iOS and Android — opt-in, storing only page titles and timestamps of active apps, no screenshots or keystrokes, the private timeline staying private until the user approves sharing and AI-drafted entries never shared without review — which is the privacy shape I want on paper. But it serves a desk workforce: we found no public information on kiosks, terminals, badge options or offline capture, corrections are documented as editable with no approval trail or audit of who changed what, and location tracking appears in a feature list with nothing said about what it stores or who can read it. 1 3 2 7