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
Automatic schedule generation in manual, semi- and fully automatic modes, skill- and certification-based assignment, multi-unit management, and instant labour-cost calculation with cost-overrun alerts while the plan is still being built — most of what thirty sites need. The demand forecast is said to run on historical patterns and real-time trends, but the captured pages name no data source behind it (no POS revenue, footfall or occupancy) and document no forecasting method behind the AI label; I found no public information comparing forecast, proposed roster and actual hours in one place. 6 7 1 2