The Roster and the Attendance Rules Agree
Assign rotating, night and split shifts, publish them to the people working them, and have late marks, overtime and payable days computed against the right shift automatically.
Shift-based businesses usually run two systems that never quite agree: a roster, often a spreadsheet or a whiteboard, and an attendance system that evaluates every punch against one standard timing. The result is that a night-shift worker who clocks in at 21:50 for a 22:00 start is marked late against a 09:00 office shift, a shift that crosses midnight is recorded as two partial days, and overtime is computed against hours nobody actually worked. Supervisors compensate by correcting records after the fact, which is both a monthly workload and a permanent gap in the audit trail. AttendancePay treats the shift as part of the attendance record. An employee is assigned a shift for a date, and their punches are evaluated against that shift — its start and end, its grace period, its break, and whether it crosses midnight. Late marks, early departures, overtime and payable days all resolve against the shift the person was actually rostered on, which removes the correction cycle rather than speeding it up.
What goes wrong when the roster lives elsewhere
Night shifts are recorded as two days
A shift starting at 22:00 and ending at 06:00 spans two calendar dates. Systems that assume a shift fits inside one day produce two partial records, and the payable-days figure is wrong before anyone looks at it.
Everyone is measured against the same timing
An attendance system with one company-wide shift marks an entire night crew late every single day, so the late-mark data becomes noise and gets ignored — including for the people who genuinely are late.
The roster is not visible to the people working it
Shifts are communicated by WhatsApp or a printed sheet on a noticeboard. Someone misses a change, does not turn up, and the disagreement about whether they were told is unresolvable.
Rotation is managed by memory
Weekly rotation across three crews is tracked by a supervisor who knows the pattern. When they are on leave, the pattern breaks and nobody can reconstruct it.
Overtime is computed against the wrong baseline
Without the assigned shift, overtime is measured against a nominal eight hours rather than the actual rostered duration, so it is overstated for short shifts and understated for long ones.
How shift & roster management works
- 1
Shifts are defined once
Each shift carries its start and end, grace period, break duration and whether it crosses midnight, so an overnight shift is understood as a single working session.
- 2
Employees are assigned shifts by date
Assignment can be a standing shift for a role or a rostered pattern that rotates, applied to individuals or to groups.
- 3
The roster is published to staff
Employees see their assigned shifts in the app, so a change is communicated through the system rather than through a message someone may not have read.
- 4
Punches are evaluated against the assigned shift
Late marks, early departures, worked hours and overtime resolve against that employee's shift for that date rather than against a company default.
- 5
The result flows into payable days
Because the shift determines expected hours, the payable-days and overtime figures reaching payroll are computed against what the person was actually rostered to work.
What you get
Overnight shift support
Shifts crossing midnight are treated as one working session rather than two partial days, which is the single most common source of wrong night-shift attendance.
Rotating shift patterns
Assign repeating rotations across crews so the pattern lives in the system rather than in a supervisor's memory.
Per-shift grace and thresholds
Each shift carries its own grace period and timing, so a night crew is not measured against day-shift expectations.
Split and multi-session duties
Support for duties broken across a day, as in hospitality and facility management, without recording the gap as an early departure.
Roster visibility for employees
Staff see their upcoming shifts in the mobile app, which removes the "nobody told me" dispute.
Branch and department shift defaults
Different sites can run different standard timings and weekly offs without separate configurations to maintain.
Weekly off patterns
Configure week-offs per employee group or department, including rotating offs that do not fall on the same day each week.
Shift-aware overtime
Overtime accrues against the rostered shift duration, with distinct treatment for normal days, week-offs and holidays.
Who this is for
See shift & roster management on your own data
Start free for 7 days — no credit card. Or book a walkthrough with our team.
Frequently asked questions
Does it handle shifts that cross midnight?⌄
Yes. A shift is defined with a flag for crossing midnight, so a 22:00 to 06:00 shift is treated as a single working session attributed to one date rather than as two partial days. This is worth testing specifically in any attendance product you evaluate, because it is the most common way night-shift attendance goes wrong and it is rarely mentioned in feature lists.
Can different employees have different shift timings?⌄
Yes. Shifts are assigned per employee and per date, so office staff, a night crew and a rotating production team can run entirely different timings under one company, each evaluated against its own grace period and expected hours.
Can employees see their roster?⌄
Yes, in the staff mobile app. Publishing the roster through the system rather than a WhatsApp message or a printed sheet is what makes a missed shift a factual question rather than a disagreement about whether someone was told.
How does overtime work with shifts?⌄
Overtime accrues against the rostered shift duration rather than a nominal eight hours, with separate treatment available for normal days, week-offs and holidays. Measuring overtime against a fixed baseline overstates it for short shifts and understates it for long ones.
Can week-offs rotate rather than falling on a fixed day?⌄
Yes. Weekly offs are configured per employee group or department and can rotate, which is necessary for any operation that runs seven days a week and cannot give everyone the same day off.
What happens if someone works a shift they were not assigned?⌄
The punch is still recorded, and the mismatch is visible rather than silently absorbed. That matters for both payroll accuracy and coverage reporting, since an unassigned worked shift is usually either a roster change nobody recorded or a genuine coverage exception worth knowing about.