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 Field Supervisor
The vendor lists terminal, NFC and a hardware tracker beside app and PC, and the desktop app records offline with sync notifications and conflict handling on reconnect — but the vendor's own help pages state offline capture exists only in the desktop app, only in the calendar, earlier entries are locked until you are back online, and the mobile app is left out entirely. That is offline as a degraded state, not a designed one, and I found no public information on how a terminal behaves when the line is down. Corrections are user edits on a phone; I found no public information on an approval workflow or a trail of who changed what. 2 3 4