Shifts rotate and the software assumes they do not
Most attendance products have one company-wide shift. A floor on three rotating shifts then produces a register full of false late marks.
A support floor breaks most attendance software in the same way: three rotating shifts, a night shift crossing midnight, break adherence that matters to the SLA, and a roster that changes every fortnight.
Written from what customers in this sector tell us goes wrong, rather than from a generic list of benefits.
Most attendance products have one company-wide shift. A floor on three rotating shifts then produces a register full of false late marks.
Which quietly breaks any system that assumes a working day starts and ends on the same date.
Everyone off the floor at once is a service problem, not just an HR one, and it is invisible until the queue backs up.
People join and leave every month, so anything requiring manual setup per person becomes a permanent job.
And approving it without seeing who else is already off that shift is how a floor ends up short.
Late marks, half-days, week-off working and shift allowances — all of which have to be right, every month, for a lot of people.
Each person carries their own shift start, grace window and late policy, so a rotating roster is a change to the assignment rather than a workaround. Night shifts crossing midnight are handled as one working day rather than two partial ones.
Configured break deduction, shown as its own line on the register so an agent can see how paid hours were calculated rather than disputing the total.
The approval screen shows who else on the same team is already off, which is the thing a team leader needs to see before saying yes to the fourth request for Saturday.
CSV import for a joining batch, shift and leave policy applied on assignment, and archiving on exit that frees the seat without deleting the payroll history.
A starting point rather than a prescription. Most teams adjust one or two of these in the first month.
| Setting | Typical choice | Why |
|---|---|---|
| Plan | Starter or Growth | Attendance is the load-bearing module here |
| Shifts | One per rotation, assigned per employee | Reassignment on rotation rather than policy edits |
| Grace window | 5 to 10 minutes | Tighter than an office team, because the queue does not wait |
| Late policy | 3 lates = 1 half day, per payroll month | Aligns the deduction to the cycle it will be applied in |
| Break | Configured per shift, deducted automatically | Shown separately so it is checkable |
| Leave approval | Team leader, with the team calendar visible | Prevents a shift being approved into being short-staffed |
| Tracker | Usually not installed | Agents are on a floor; attendance and adherence are the question |
Yes. A shift spanning midnight is treated as a single working day, so a 22:00 to 07:00 shift produces one attendance record rather than two partial ones on separate dates.
Yes. Shift assignment is per employee, which is what makes a rotating roster workable. Reassign on rotation rather than editing a company-wide policy.
Configured break deduction is applied and shown separately on the register. Real-time floor adherence dashboards of the kind a workforce management suite provides are outside what this product does.
Attendance can be posted through the REST API, which is how biometric and access-control systems are usually integrated. There is no out-of-the-box driver for a specific device, so budget for a short integration if punches must come from hardware.
Yes. Cloud plans scale to it and the self-hosted licence has a band for up to 250. Above that, ask for a quote rather than reading the published bands.
Start on the cloud in ten minutes, or tell us your headcount and where the server has to live and we will price the self-hosted licence on the call.