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
Capture reaches field crews, not just the desk: web and browser clocking, iOS and Android apps, a shared kiosk, timeclock terminals and Bluetooth beacons are all named, and entries made offline auto-sync once connectivity returns. Corrections run through timesheet approval with a full audit log of every action, filterable by period, user and team, and the pages state plainly there is no keystroke logging, no screenshots and no mouse-movement detection — a tool that measures rather than watches. We found no public information on GPS or geofenced check-in and its limits, nor on what a Bluetooth beacon actually stores, which is the first question co-determination would ask. 1 3 4 6 10