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 Operations Director
The automatic proposal is real and its method is documented rather than waved off as AI: staffing counts per shift, over twenty individually prioritised criteria, skills, positive and negative availability, absences, target hours and rest periods feed an algorithm the vendor says was developed with TU Wien, and the result stays editable by drag-and-drop with a traffic-light conflict check before publishing. However, we found no public information on planning driven by demand data such as POS revenue, footfall or occupancy, on labour cost shown against budget while planning, or on sharing staff across locations. 3 4