Geofenced, biometric-verified attendance: how it actually works

"Are they actually at the office?" is a question most attendance systems can't answer honestly, since a manual punch can happen from anywhere. MSMEBOT HRMS answers it automatically, using a geofence and a face or fingerprint scan, at the moment of punch-in.

What a geofence actually is

Every branch or office location is set up with GPS coordinates (latitude and longitude) and a radius in meters, typically somewhere between 50m and 5000m. That circle is the geofence. If you leave the coordinates blank for a branch, the geofence stays inactive and every punch from that branch will show as Remote by default.

What happens at punch-in

• The employee types a short agenda for the day (required) and taps the biometric scanner.
• A face or fingerprint scan verifies identity (a face scan also captures a photo).
• The device's GPS location is captured at that instant.
• The system compares that location against the branch geofence and labels the punch In Office (inside the radius) or Remote (outside it).

The same happens at punch-out, alongside a short note on what was completed that day. Both punches store a tappable GPS link that opens the exact location in Google Maps.

Grace time, not a hard cutoff

Attendance isn't all-or-nothing on lateness either. Each Shift has a configurable Grace Time in minutes: how long after the shift start an employee can still punch in before being marked Late. If Late Compensation is enabled company-wide, employees can make up the time later in the day rather than being marked absent outright.

What managers see

Anyone with Real-Time Location Sharing turned on appears as a live pin on the Admin Panel's Live Map, green inside the geofence, orange outside it, grey if sharing is off, updated over a WebSocket connection with no page refresh needed. A history icon next to any employee redraws their movement trail for any past date, useful for confirming a client visit actually happened, or resolving a disputed regularization request.

The point of all this

None of this is about surveillance for its own sake. It's about removing the awkward conversation of "can you confirm you were actually there?" from HR's job entirely, while still letting genuinely remote work be logged honestly as Remote rather than silently rejected.