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 runs through web, mobile and CloudClock for frontline teams, and timesheets automatically pull time from more than a hundred work apps. The captured page says nothing about offline behaviour, employee-requested corrections with manager approval, or any audit trail of who changed what. As a works council I would need to know exactly what that automatic capture from 100+ work apps observes, and who can read an individual's day, before co-determining its use. 1