How can agencies reduce buddy clocking and timesheet disputes?
Check the enrolled worker at the shift rather than relying only on a shared code or a typed timesheet. A phone or tablet face check-in with passive liveness can record a local attendance decision offline. Sync records later and reconcile with supervisor approvals; identity, location and hours need separate controls and a workable non-face alternative.
Last reviewed: 18 October 2026 · FaceTagr team
How do manual timesheets and face check-in compare?
| Issue | Manual or code-only process | Face check-in with supervisor review |
|---|---|---|
| Identity | Signature, PIN or code may not verify the person | Live comparison with an authorised enrolled identity |
| Timesheet approval | Depends on staff entering and approving hours | Recorded check-ins still require approval and exceptions |
| Client billing evidence | Timesheet and client sign-off | Recorded time, configured site context and sign-off |
| Connectivity | Paper works offline; online forms vary | Local matching and queued records |
| Worker effort | Writing or entering shift information | Face capture plus a practical alternative |
What does shift check-in look like?
Step 1
Authorise enrolment and map the worker to the assignment.
Step 2
Select the approved site device and configure the shift.
Step 3
Run face matching and passive liveness; capture permitted time and location context.
Step 4
Queue records offline and sync through the agreed integration.
Step 5
Resolve exceptions and reconcile supervisor-approved hours before payroll or billing.
What should the agency agree first?
Face templates are biometric data, even when capture photos are not retained. Define the lawful basis, notice and consent where required, retention, access controls and a workable non-face alternative before rollout. On-device processing does not by itself establish legal compliance. Define who can see records, who approves disputed hours and how records are corrected.
Plan a pilot around your workflow
For privacy or deletion requests, contact support@facetagr.com. Read our privacy policy.
Sources
Product capabilities describe FaceTagr's supported workflows, not third-party endorsement. This page is general information, not legal advice. Check your obligations with your data protection officer or adviser.
Frequently Asked Questions
Can it work without a network?
Yes. FaceTagr's mobile SDK supports fully offline 1:1 verification, 1:N identification and passive liveness on Android and iOS. Reporting and integration need a connection when records are synchronised.
Are workers' photos stored?
Configured mobile attendance workflows can avoid retaining check-in photos or video. Enrolment references, templates and attendance records still need a documented retention policy. Customer-built SDK apps and CCTV may store images according to their configuration; confirm the data flow before deployment.