Attendance
Punches from terminals, phones and the field: in one timesheet.
Biometric devices push directly to the platform. The mobile app clocks in inside a geo-fence with a photo. Both land in the same record, and the record says where each punch came from.
Biometric terminals push to the platform directly.
Devices are registered per site and push each punch as it happens. Every punch is kept as its own log line, badge, timestamp, direction, before it becomes attendance.
Keeping the raw log separate is what makes a mis-mapped badge recoverable. HR maps badge IDs to employees in a side-by-side screen, and existing logs are back-filled against the mapping rather than re-punched.
-
Geo-fenced mobile clock-in
The app will only clock in inside a defined boundary, and captures a photo with the punch.
-
Field visits
Site visits are recorded against the person who made them, for roles that do not sit at one location.
-
Validation
Records can be left unvalidated deliberately, and an unvalidated record is visible as exactly that.
The failure this is built against
“Nobody clocked in” and “nothing was recorded” are not the same day.
They produce an identical empty query, and confusing them turns a data outage into an imaginary crisis. Attendance states its own freshness, and anything reading it inherits that.
A rule that depends on attendance will decline to run against a stale feed rather than report an absence it cannot stand behind.
See attendance with its gaps intact.
The demo shows unvalidated records and stale-source states, not a perfect week.