Roster building & demand planning
How this is scored
How a plan gets built across locations, roles and qualifications — templates, staffing requirements, forecasting from sales or occupancy, and whether the product proposes a roster or only draws one.
0 — Not a rostering tool; shifts cannot be planned in the product (a time clock, HR file or messenger only).
3 — A weekly shift grid per location with shift templates and roles attached, and the roster published to staff.
5 — Shift templates with roles or qualifications on shifts, several locations or departments, and open shifts or coverage gaps shown while planning.
8 — Staffing requirements per shift and demand-based planning from a named data source (POS revenue, footfall, occupancy or bookings), automatic roster proposals the planner can accept or adjust, labour cost shown against budget while planning, and cross-location staff sharing.
10 — Planning closes the loop: forecast, proposed roster and actual hours compared in one place, the proposal explains which rule or demand figure drove each assignment, and the vendor documents the forecasting method rather than calling it AI.
The Shift Manager
This builds the plan the way I need on a Thursday night: I set how many people each shift needs, the algorithm developed with TU Wien proposes a week in about forty seconds, and I can drag shifts around afterwards or rerun it keeping existing assignments, with over twenty criteria — skills, availability, absences, rest periods — each prioritised from very high to ignore and saved as reusable templates. Shift types come as templates, planning runs per work area with its own configuration, and open shifts are visible for eligible staff to claim. We found no public information on forecasting from POS revenue, footfall or bookings, on labour cost against budget while planning, or on cross-location staff sharing. 3 4