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 schedule generation is well evidenced: manual, semi- and fully automatic modes, templates, assignment by skills and certifications, multi-location planning, and labour cost calculated instantly while the plan is built. What the forecasting is actually fed on stays vague — "real-time trends and operational changes" and "historical patterns, demand forecasts" name no data source such as POS revenue, footfall or occupancy, and the method is only ever called AI. I found no public information on a forecast-versus-actual-hours comparison or on the plan explaining which rule or demand figure drove an assignment. 6 7 1