Attendance · Glossary

Liveness Detection

Also called: face liveness check, anti-spoofing, presentation attack detection

Definition

Liveness detection is the check inside a face or selfie attendance app that confirms a real, living person is in front of the camera rather than a printed photo, a phone screen playing a video, or a mask. It runs before the face is matched against the enrolled record, so an employee cannot mark attendance for a colleague by holding up their picture.

Active versus passive liveness

Active liveness asks the person to do something – blink, turn the head, smile, follow a dot on screen – and checks that the motion is natural. It is easy to explain to workers and hard to beat with a still photo, but it adds two to four seconds per punch and can fail for people wearing thick spectacles or standing in harsh sunlight.

Passive liveness analyses a single frame or a short burst without asking for any action. It looks at skin texture, reflections, depth cues and moiré patterns that appear when a camera photographs another screen. It is faster and less annoying at a busy gate, but relies more on the phone camera quality. Most attendance apps now combine both: passive by default, with an active challenge when confidence is low.

The spoof types it has to catch

The attacks an Indian employer actually sees are low-tech. A helper hands his phone with a WhatsApp DP of an absent colleague to a friend; a supervisor holds up a laminated ID-card photo; a guard replays a selfie video. High-end 3D masks are rare outside films. A good liveness layer therefore concentrates on print attacks, screen-replay attacks and cut-out masks, and flags them rather than silently rejecting.

Liveness does not verify identity. It only answers 'is this a live human'. Identity is the separate face recognition match against the encrypted descriptor stored at enrolment. Both must pass, and both should be logged, so that a rejected punch shows why it failed.

  • Print attack: paper photo or ID-card photo held to the camera
  • Replay attack: photo or video shown on another phone or tablet
  • Mask or cut-out: a printed face with eye holes, worn by someone else
  • Twin or look-alike: a genuine live face that is not the enrolled person – caught by the match step, not by liveness

Why it matters for selfie attendance and payroll

Without liveness, a selfie attendance system is just a photo log that someone has to inspect by eye at month end. With it, the punch is trustworthy at the moment of capture, which is what makes attendance-linked payroll and client billing defensible. It is also the control that closes the buddy punching loophole that fingerprint cards and PINs never solved.

Under the DPDP Act, face data is personal data; the employer should tell employees that a liveness check and face match are performed, what is stored (descriptors, not raw images) and for how long. Put this in the attendance policy rather than relying on a verbal briefing.

Example: a rejected punch at a housekeeping site

At 06:58 a housekeeping supervisor in Noida tries to mark in three absent staff by pointing his phone at their ID photos. The passive check flags flat texture on all three attempts and asks for a blink; nothing moves. All three punches are refused and logged as 'liveness failed' with a timestamp. The live monitor shows the three as absent at 07:15, and the operations head calls the site instead of discovering the gap on the client's bill.

How Attend Mitra handles this

Attend Mitra's face-recognition and selfie attendance include a liveness check before the face match. The app stores encrypted face descriptors rather than photos, records why a punch was rejected, and pairs the result with the GPS stamp and geofence rule for the site, so a supervisor can see failed attempts on the live monitor.

Frequently asked questions

Can liveness detection be fooled by a high-quality photo?
A plain print or a phone screen is what liveness is designed to reject, and a decent implementation catches these reliably. Sophisticated 3D masks or deepfake video streams injected into the camera feed are harder, but they need technical effort far beyond what an employee marking proxy attendance would attempt. Combine liveness with geofencing and device binding to make the effort pointless.
Does liveness slow down attendance at a busy gate?
Passive liveness adds well under a second. Active challenges add a few seconds each. For a factory gate with 300 workers in a 20-minute window, use a kiosk tablet with passive liveness and reserve active checks for low-confidence results, or spread arrival across staggered shift starts.
Is liveness detection the same as face recognition?
No. Liveness checks that a real person is present; face recognition checks who that person is. An attendance app must do both. Liveness alone would let any live person punch for anyone; recognition alone would accept a photo of the right person.
What happens when a genuine employee fails the check?
It happens with poor lighting, backlight from the sun, or a cracked camera. The app should let the employee retry, and if it still fails, submit a punch that a supervisor approves through regularization. Keep a count of repeated failures per person so you can fix the cause – often it is simply re-enrolling the face in better light.

Related terms

Face Recognition Attendance
Face recognition attendance verifies an employee's identity at punch time by converting a live camera frame into a numeric face descriptor and comparing it with the descriptor stored at enrolment. A match above a set threshold, combined with a liveness check to reject photos and videos, records the punch. It runs on dedicated terminals or on ordinary Android and iOS phones.
Selfie Attendance
Selfie attendance is a mobile attendance method in which the employee takes a photo of themselves in the app at punch time. The app verifies the face against the enrolled profile, stamps the punch with GPS coordinates and time, and stores the image or its descriptor as evidence. It is the standard method for security guards, field sales and other staff who work away from a fixed device.
Buddy Punching
Buddy punching is when one employee marks attendance on behalf of another who is late, absent or has already left – swiping a colleague's card, entering their PIN, signing their name in the register or punching from their phone. It inflates paid days and overtime for people who were not at work, and it is the main fraud that biometric and face-verified attendance systems exist to stop.
Proxy Attendance
Proxy attendance is the Indian workplace term for attendance recorded for a person who was not actually present – a colleague punching for them, a supervisor marking absent workers present in the register, or a contractor listing 'ghost' workers who exist only on the muster roll. It covers buddy punching and goes further, into supervisor and contractor-level fraud that affects wages, PF, ESI and client billing.
GPS Spoofing / Mock Location
GPS spoofing, or mock location, is the practice of making a phone report a false position so that a GPS or geofenced attendance punch appears to come from the work site when the employee is somewhere else. It is usually done with a free 'fake GPS' app and Android's developer-options mock-location setting, and it is the main fraud risk in mobile attendance for field and security staff.
Attendance Management System
An attendance management system is software that records when employees start and finish work, applies the company's shift, late-mark and leave rules to those records, routes corrections through approvals, and produces the attendance reports and paid-day counts that payroll depends on. It replaces paper registers, Excel sheets and WhatsApp messages with one auditable record per employee per day.

Go deeper

See how this works inside Attend Mitra

Verified attendance, shift rosters, leave, and payroll-ready reports in one platform built for Indian teams.

Browse all terms