Clock-ins checked against each employee's actual policy — lateness, half-days, and forgotten checkouts handled automatically, not eyeballed at month-end.
Every punch is measured against a real policy the moment it happens.
A short device PIN on a shared terminal, or clock in from a mobile device — no separate login required for a floor shift.
Layer face verification on top of the PIN for employees you've enrolled, so a shared terminal PIN can't be used by the wrong person.
Lateness and half-day status are computed against the employee's actual policy thresholds — not left for a manager to work out by hand.
When enabled, a clock-in has to happen within a set radius of the property — it can't be started from somewhere the employee isn't at.
With a short PIN on a shared terminal, or from a mobile device. Optional face verification can be layered on top of the PIN for an extra check, if you've enrolled the employee's face.
It's calculated against the employee's assigned policy — the grace period and late threshold are read from the policy, and a punch-in past that window is flagged as late, not just recorded as a plain time.
It's resolved automatically the next time the system checks — following whatever your policy specifies (auto-checkout, mark absent, or route to manager approval), instead of leaving an open punch sitting there indefinitely.
Yes — total hours worked are compared against the policy's half-day threshold to determine it, rather than a manager eyeballing the clock-in and clock-out times.
Yes, if geo-fencing is enabled on the employee's policy — a clock-in attempt outside the configured radius is rejected.