Loading
Because the raw data is always slightly wrong — missed clock-outs, forgotten starts — and the correction process is usually someone editing the record directly. Once the original can be overwritten, none of it is evidence.
Recording the start and end of a working period, against the shift it belongs to, from a browser or phone.
Clock-ins attach to the rostered shift. A missing or implausible entry is flagged rather than guessed, and corrections go through regularisation so the original and the change both survive.
Somebody forgets to clock out on Friday. The shift flags as incomplete, they request a correction on Monday with a reason, their manager approves, and both the original gap and the approved value are on the record.
There is no biometric, facial or geofenced verification, and no kiosk mode. If you need proof of physical presence, this is not that.
Attendance reports, timesheets, payroll in Books and capacity in Loop all read the resulting hours.
Web clock-in works from any browser, and a manager can record on their behalf as a regularisation.
No. Clock-in records time, not place.
Yes, and we would recommend it — it is what makes the trail useful later.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.