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
The hardware story is genuinely strong: terminals built by the vendor itself, events stored when an outage occurs, standalone synchronisation by USB, and a virtual terminal on workstation, smartphone or touchscreen with real-time and retrospective declaration modes configurable per employee. But geolocating mobile staff "to check that their declarations are accurate" is marketed as verification, and I found no public information on what the location data stores, who can read an individual's day, or whether the tracking can be switched off — the same platform also lets managers "view people's movements" and "track everyone present", which is a system that watches more than it measures. I also found no public information on a correction workflow showing who changed a time entry and why, so the capture paths are first-class while the answers a works council needs before approval are absent. 1 2 3