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
Web app, desktop apps for Windows, Mac and Linux, and offline tracking that syncs on reconnect are confirmed, and timesheets carry an approval module — but I found no public information on a mobile app, a shared terminal, geofenced check-in, or who stands behind each correction. For field and shift crews that is still a desk-centred picture. The automatic app and website tracking, the background AI agent that fills timesheets, and screenshots that an administrator can switch on make me ask what else the capture watches, not just what it measures. 1