Loading
Because the rota is usually built in a spreadsheet from a leave list exported on Friday. Anything approved after that is invisible until somebody does not turn up.
Planning who works when: shift patterns, published rotas, and coverage visible per team and per day.
Rotas are built against the personnel record, so approved leave is already excluded. Coverage gaps show as you plan rather than after publishing.
A manager rosters next month. Two people have leave approved that week; neither can be assigned, and the gap is visible while there is still time to fill it.
It does not optimise rotas automatically or enforce working-time rules. It shows you the shape of the week; the compliance judgement is yours.
Attendance records against the published shift. Loop reads roster and leave together for capacity. Desk reads coverage for queue staffing.
Swaps are requested and approved, so the rota and the record stay in step.
Yes, defined per team and applied forward.
Yes, where the person is assigned to more than one location.
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.