How the published roster becomes the attendance benchmark — what 'on-time', 'late', and 'no-show' are measured against.
How roster data flows into attendance tracking and what happens when the roster changes after publish.
Attendance accuracy depends entirely on the roster being published before employees clock in.
When a roster is published, Workwisely creates an expected shift record for each assigned employee–date combination. The Attendance module compares actual clock-in/clock-out times against these expected records to calculate:
Set grace periods under Setup → Attendance → Late Arrival Settings. Common configurations:
| Setting | Typical value | Effect |
|---|---|---|
| Late grace period | 5–15 minutes | Clock-ins within this window aren't marked late |
| Early departure grace | 5–10 minutes | Clock-outs within this window aren't flagged |
| No-show threshold | 2 hours | If no clock-in by this offset, generates a no-show alert |
Post-publish overrides update the expected shift record in real time. If an employee was marked 'no-show' but then an override removes their shift for that day (e.g. emergency leave approved after the fact), their attendance record is automatically corrected.
If an employee clocks in on a day when no shift is scheduled for them, the clock-in is recorded as Unscheduled Activity in attendance. This is flagged for manager review — it doesn't generate a roster violation, but it does appear in the attendance exceptions report.
Go to Attendance → Roster-Based Report to see a side-by-side view of scheduled vs. actual hours for each employee. This report is also used by payroll for overtime and allowance calculations.