Rostering · for presence-based work
Some work is not a job.
It is being there.
Cleaning rounds, front desks, security patrols, kitchen shifts: work that repeats weekly and lives or dies on coverage. The roster handles the patterns; the schedule board sees the hours; leave blocks both at once.
Patterns, not paperwork
Set a shift once: person, site, times, which weekdays. It repeats until you say otherwise. One-off cover is a date instead of a pattern.
Open shifts fill themselves
Leave a shift unassigned and it becomes claimable. Qualified staff pick it up from their own view; you see the gap close without a single phone call.
Leave that means leave
Unavailability blocks the roster and the job board together, so nobody schedules reactive work onto someone who is on holiday. Rostered hours count toward real utilisation.
One workforce, both kinds of work
The same person can hold a morning cleaning round and take reactive jobs in the afternoon. The schedule board shows shifts and jobs in one capacity picture.
Sites and roles on the shift
Tag shifts with a site and a required role or ticket, so claiming is limited to people who can actually do the work.
Built into scheduling
Rostering is not a separate app to reconcile: it is a page inside the Schedule workspace, sharing people, sites, leave and the board.
Coverage and jobs, one schedule
See how the roster, the board, jeopardy and the optimiser work as one scheduling suite.