Face recognition attendance system for construction sites
Proxy punching and ghost workers cost you real money every month. SitePrime verifies the worker's face on the server and their location against your site's geofence — so attendance is what happened, not what someone wrote in a register.
Server-side verification·Works offline·DPDP-aligned
The problem
You are paying for people who were never there
Every builder in India knows the register is fiction. The supervisor fills it in at the end of the day from memory. One man signs for three. A gang of forty gets marked as forty-six. The numbers are close enough that nobody can prove anything, and far enough off that you are quietly funding a payroll that never picked up a trowel.
The usual fixes don't survive a real site. A fingerprint scanner at the gate makes a queue at 8am, then goes unused because the work is spread across three towers. It fails on hands that are cut, dusty and worn — which is most hands, on most days. And a phone app that checks the face on the phone is trivially defeated: whoever controls the handset controls the answer.
- One worker marks attendance for four of his friends who never came.
- Names on the muster roll that nobody on site can point to.
- Check-ins from home, from the tea shop, from the next site over.
- Payroll computed off a register that cannot be verified after the fact.
- A gate scanner that nobody uses because the work is 200m away.
How it works
Two checks, neither of them on the worker's phone
SitePrime's face recognition attendance system makes two independent things true before a check-in counts. The worker has to be inside your site's geofence, and the face captured at that moment has to match the face that worker enrolled with — a 1:1 verification, run on our server.
That last detail is the whole thing. Plenty of attendance apps do the face match on the handset and send up a "pass". That is a lock with the key taped to the door: a rooted phone or a modified APK just sends "pass" whenever it likes. Doing the match server-side means the phone is only ever a camera. It has no vote on the outcome.
- 1
Enrol once
The worker consents and enrols their face. We store an encrypted descriptor — not a photo library.
- 2
Check in on site
Supervisor or worker opens the Android app at the face of the work and captures the check-in.
- 3
Server verifies
Location is checked against your geofence and the face is verified 1:1 against the enrolled descriptor.
- 4
Payroll uses it
Verified attendance flows into labour tracking and payroll. Nothing is re-keyed.
Why it holds
Built to survive a real site, and a real audit
Server-side 1:1 verification
The match runs on the server against the worker's enrolled face, not on the phone. A rooted handset or a patched APK can't tell the server that a check-in passed when it didn't.
Geofence on top
Face and location are checked together. The right face at the wrong place fails, and so does the right place with the wrong face.
Works with no signal
Basements, cellars, highway stretches, tower cores. The Android app is offline-first — the check-in is captured and queued, then syncs and verifies when the phone finds a network.
Encrypted face descriptors
We store a mathematical descriptor, encrypted — not a photo album of your workforce. It is used for one thing: matching that worker against themselves.
Consent and erasure built in
Enrolment is consented, and a worker's biometric data can be erased on request. This is DPDP-aligned by design, not by policy document.
Straight into labour and payroll
Verified attendance is the attendance payroll computes on. No register, no re-entry, no argument at the end of the month about who was actually there.
Being straight with you
What this does and doesn't do
We would rather you buy this understanding it than be disappointed in month two, so:
It does
- Verify a named worker against their own enrolled face, server-side.
- Refuse check-ins from outside your site's geofence.
- Capture attendance offline and verify it on sync.
- Feed labour tracking and payroll directly.
- Keep biometric data encrypted, consented and erasable.
It doesn't
- Identify strangers — it is 1:1 verification, not surveillance of the general public.
- Track a worker's movement through the day. It records a check-in, not a trail.
- Replace your judgement — failed checks are flagged for a human to resolve.
- Require a phone per worker. Supervisor-led check-in is the normal pattern.
What it connects to
Attendance is only useful if it goes somewhere
An attendance app that just produces a spreadsheet has moved the problem, not solved it. In SitePrime, a verified check-in is the same record your labour tracking and payroll run on, and it sits alongside the daily site report your engineer files from the same phone, on the same trip, in the same app.
- Labour tracking — deployed strength per site, per day, verified
- Payroll — computed on attendance you can actually stand behind
- Daily Site Report — labour deployed matches who checked in
- Reports & analytics — on-site strength across every project
- Role-based access — HR sees payroll, the engineer sees his gang
- Offline-first Android app — one app for check-in, DSR and approvals
FAQ
Questions, answered
Two things have to be true at once, and neither is under the worker's control. First, the phone has to be inside the site's geofence — so a check-in from the tea shop or from home fails. Second, the face captured at check-in is verified on our server against the face that worker enrolled with — so a friend punching in for them fails. Because the match runs server-side rather than on the handset, tampering with the app or the phone doesn't get you past it.
No, and the differences matter on a construction site. A fingerprint machine is one fixed point — a queue at 8am, and useless for a labour force spread across three towers or a linear site. It struggles with the cuts, dust and worn ridges that construction hands actually have. And it's a capital purchase per gate. This runs on the phones your supervisors already carry, moves with the work, and verifies location as well as identity.
The common pattern is supervisor-led: your supervisor's phone runs the check-in for the gang at the face of the work, and each worker's own face is verified at that moment. The worker doesn't need a phone — the verification is of their face, at that location, at that time.
The face descriptor is encrypted and held against your own tenant — isolated from every other company on SitePrime. Enrolment is consented, and any worker's biometric data can be erased on request, which is what India's DPDP framework expects. We store a descriptor for matching, not a browsable photo library.
The check-in is flagged rather than silently dropped, so your supervisor can see it and your admin can resolve it. The point is to make the exceptions visible and few — not to lock a genuine worker out of their day's wages because the light was bad.
Explore
Related to this
- GPS attendance appGeofenced check-in — a worker can only mark attendance standing on your site.Read more
- Daily progress report softwareGeo-tagged DSRs filed from the phone, offline, in under two minutes.Read more
- Construction project management softwareThe whole build — projects, BOQ, planning, procurement, billing — on one system.Read more
Or see everything SitePrime does — all 46 modules, from BOQ to accounts.
Stop paying for attendance that never happened
Enrol a gang, run a week of verified check-ins, and compare it to your register. That comparison is usually the whole sales pitch.
14-day free trial · no credit card · set up in minutes