Prove who turned up, at every client site
FaceTagr helps recruitment agencies and staffing platforms check that an enrolled worker attended the assigned client site. Mobile face matching and passive liveness can run offline, with timestamped attendance records synced later. Use FaceTyck Attendance or evaluate SDK integration in your candidate app, with supervisor approvals, privacy safeguards and a non-face alternative built into the rollout.
Last reviewed: 18 October 2026 · FaceTagr team
Where can staffing lose time and money?
| Problem to assess | Operational risk | What to evaluate |
|---|---|---|
| Buddy clocking | One person checks in for another | Live face match, passive liveness and exceptions |
| Worker substitution | Person arriving differs from enrolled worker | Identity recheck against the authorised reference |
| Timesheet disputes | Unclear hours delay payroll or billing approval | Timestamp, site context, supervisor review and reconciliation |
| Weak client-site signal | Online check-in fails or is deferred | Offline matching, queued records and later sync |
| Eligibility and identity confusion | A face result is mistaken for a legal check | Separate identity matching from prescribed right-to-work checks |
Should your agency use the app or embed the SDK?
For agencies: evaluate FaceTyck Attendance on a shared site tablet, supervisor phone or supported worker device. For staffing software and VMS vendors: embed recognition and passive liveness inside your Android, iOS, Flutter or React Native candidate app. Map worker, client, assignment and shift identifiers before agreeing a REST API or export integration. No named recruitment-software integration is assumed.
What if you already use QR or biometric check-in?
QR confirms a code was presented; a face workflow can add a check against an enrolled identity. Existing biometric apps may already use device authentication, selfie matching or another engine. Establish the current method first, then compare genuine-user completion, liveness and offline behaviour in a side-by-side pilot. Keep QR or manual attendance as a practical alternative where required.
How do you protect temporary workers?
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. Configured attendance capture can avoid retaining check-in photos or video, but enrolment references, templates and records still need protection.
How much hardware does a client site need?
Use a supported phone or tablet already available, or evaluate an entry-level Android tablet from about $100. This is an approximate hardware estimate only; licence, setup, integration and support are separate.
What should a first client-site pilot prove?
Step 1
Choose one client site and a defined shift group, with appropriate worker permissions.
Step 2
Compare the current QR or timesheet process with face check-in and a non-face alternative.
Step 3
Test poor connectivity, worker substitution attempts and genuine-user exceptions.
Step 4
Reconcile records against supervisor-approved timesheets and client billing, rather than promising savings.
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 face recognition stop buddy clocking for agency workers?
A live face comparison and passive liveness can reduce opportunities to check in for another worker. It is not an absolute fraud guarantee; enrolment quality, thresholds and supervisor exceptions matter.
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.
Can we embed it in our candidate app?
Yes. Evaluate native Android, iOS, Flutter or React Native SDK integration with your software provider. Shift, GPS, sync and approval rules remain part of the host application.
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.