Staff shift scheduling
Rotas built in minutes, swaps that need one approval instead of three phone calls, and payroll paid for hours actually worked.
A manager builds next week's rota from the one before it, staff see their shifts on a phone, and a swap between two people takes one approval rather than three phone calls. What reaches payroll is what was worked, not what was planned — the two differ most weeks, and the difference used to be reconstructed from memory.
Features
- Rotas built from the previous week and adjusted rather than retyped
- Qualification rules, so a shift cannot be filled by somebody not allowed to work it
- Shift swaps between staff needing a single approval
- Availability and leave requests submitted by staff themselves
- Clock-in and clock-out recorded against the planned shift
- Overtime and wage cost forecast before the rota is published
- Coverage gaps flagged while there is still time to fill them
- Hours worked exported in the shape payroll already expects
The cost forecast is the feature managers keep: seeing the wage bill before publishing a rota changes the rota.