Tuesday is office day. Wednesday is WFH. Thursday is a client site. The biometric machine only exists at HQ. Field staff WhatsApp a selfie. WFH staff are “trusted”. Payroll still treats every absence from the machine as LOP. Three teams, three truths — then attendance vs payroll mismatch shows up as a dispute, not a report.
Hybrid is not “WFH plus a biometric”
Indian SMEs now run three patterns in the same payroll: office shifts, work-from-home, and field / multi-site. A single fingerprint device at the gate cannot see two of those patterns. The design that works is one attendance ledger, with different verification methods per pattern — all feeding the same LOP, OT and shift rules.
Geo-fence vs biometric vs office shifts — what each is for
| Method | Best for | Watch-outs |
|---|---|---|
| Biometric / face at gate | Fixed office, high buddy-punch risk | Hardware cost, DPDP consent, no WFH |
| Geo-fence (punch-time GPS) | Office radius, client sites, field teams | Needs policy on WFH radius vs office days |
| IP / network check | Office Wi-Fi confirmation | Weak alone; easy to bypass with a hotspot story |
| Liveness selfie + time | WFH days without stalking the home | Must not store extra biometric copies you cannot delete |
| Shift + roster engine | Night, rotating, 24×7 ops | Useless if punches live in another app |
Office days
Geo-fence around the campus or biometric at the door. Same late-mark and half-day rules you already published. Do not run a second “manual” register for VIPs — that is how attendance fraud starts.
WFH days
Punch-time location inside a declared WFH zone (or selfie + IP), not all-day GPS stalking. Document the rule in the hybrid policy. Continuous tracking at home is a DPDP and trust failure — see DPDP for HR teams.
Field and multi-site
Client or project geofences, or a check-in at the job GPS. Payroll must know the shift that applied that day, or OT and weekly-off math will be fiction.
Why this shows up on the payslip
False LOP
WFH day with no machine punch treated as absence. Trust dies in one cycle.
Wrong OT
Night shift in Excel, day shift in the app. Labour Code overtime inherits that error.
DPDP on fingerprints
Templates never deleted on exit; no alternative check-in for people who decline biometrics.
Two systems
Mobile app for field, biometric for HQ, payroll from neither — reconcile at month-end.
Hybrid attendance is a policy plus a single punch ledger. The method (geo, face, fingerprint, IP) is a plugin. If payroll cannot see the same day the employee lived, you do not have hybrid work — you have unofficial leave.
The way forward
Write office / WFH / field rules once. Use geo-fence or face for mobile days, biometric only where the gate already exists, and delete biometric data on exit. Feed every method into one attendance module that payroll already trusts. See Bynarize attendance: geo, IP, face, multi-shift and how multi-location tracking fails when every branch buys its own device.
If you are an HR Head or Ops Leader: ask for one report: office vs WFH vs field days last month, with LOP and OT, for one team. If that report takes two tools and a VLOOKUP, your hybrid policy is not operational yet.
Can payroll see every hybrid punch?
Geo-fence, face and shifts in one attendance engine — not three apps.
