How can UK construction sites reduce buddy clocking?
A face check-in with passive liveness can help confirm the person attending a shift rather than merely possession of a card, QR code or PIN. FaceTagr's mobile workflow can operate offline at temporary sites and sync later. Keep supervisor review, a lawful basis and an alternative route; an attendance result is not automatic payroll approval.
Last reviewed: 18 October 2026 · FaceTagr team
How do fixed terminals and mobile capture compare?
| Need | Fixed terminal | Phone or tablet capture |
|---|---|---|
| Temporary site setup | Power, mounting and terminal configuration | Device enrolment, mounting if shared, and site setup |
| No signal | Depends on terminal offline support | Offline matching and queued attendance |
| Moving between sites | Move and reinstall hardware | Reassign the configured device and site |
| Payroll | Export or integration required | Sync and integration mapping required |
| Worker exceptions | Supervisor process needed | Supervisor process and non-face route needed |
What should a site pilot measure?
Step 1
Check-in completion during the actual shift rush.
Step 2
Photo and screen replay rejection alongside genuine-worker completion.
Step 3
Network loss, record sync and duplicate handling.
Step 4
Supervisor exceptions and payroll reconciliation, without promised savings.
How does it connect to payroll?
Map worker identifiers, site assignments and attendance records to your payroll or workforce platform through an agreed REST API or export workflow. An integration must be assessed against the software you use.
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.
Does processing on the device remove privacy obligations?
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.
