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 Skeptic
Automatic proposals are real and documented: staffing requirements per shift, skills, availabilities, absences, rest periods and weekend rules feed a prioritizable algorithm with over twenty criteria, developed with TU Wien and named as such rather than dressed up as AI — a point in the vendor's favour. What keeps it off the top band: the staffing requirement is a number the planner types in per shift, not something derived from POS revenue, footfall or occupancy, and we found no public information on labour cost shown against budget while planning or cross-location staff sharing. 3 4