A field workforce attendance app that checks the face and the site.
A UK workforce-management software company couldn't track whether field workers were actually on site. Attendance was marked by hand, and nobody could stop a colleague checking in for someone else. We built a mobile attendance app with geofenced check-in and face verification, running on Azure. The Android app is published and an Azure-hosted API is in place. Employees register with their own face images, and admins approve every profile before first login.
| Before | With the attendance app | |
|---|---|---|
| Marking attendance | Marked manually and unreliable | Check-in only on a valid site, with the clock starting on a face match |
| Proxy check-ins | No way to stop a buddy checking in | Failed matches are logged to the admin panel |
| Leave requests | No proper system | Requests go to the manager of the employee's current site for approval |
| No signal | Attendance couldn't be captured | Check-ins are stored on the device and synced when it reconnects |
| New staff | No controlled onboarding | Employees register with photos and an admin activates the profile |
Employees register in the app and capture face images, and an admin reviews and activates the account. After that, every shift follows the same path.
The clock starts only when the camera face matches the registered face, so a colleague can't clock in for someone else.
Check-in is allowed only on a valid site. Anywhere else, the app says "You are not in site reach".
Check-ins made with no signal are stored locally and synced when the device reconnects.
An admin reviews the photos and activates each account before first login, and sees every failed face match.
Leave requests go to the manager of the employee's current site, who sees a Staff on Site view and the timesheet.
Face and location data is personal data under UK GDPR. Employees register their own face images, and push notifications tell them they're being tracked within the marked area.
The app captures a face at check-in and matches it against the employee's registered face using an Azure face-recognition service. The clock starts only on a match, and failed matches are logged to the admin panel.
The check-in is held on the device and synced when it reconnects.
Employees register their own face images and are notified when they're tracked within the marked area. An admin approves every profile, and the data is treated as personal data under UK GDPR.
Yes. The same attendance system was later offered as a white-label product with the reseller's own logo and colours, sign-in and sign-out photos, and site zones drawn on a map as polygons, circles or squares.
Tell us how your crews check in today. We'll show you how a person-approved attendance flow could work for your sites.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.