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 scheduler builds a real plan: shifts carry qualifications for named users or smart groups, templates keep those qualifications, open and claimable shifts surface coverage, and an auto-schedule proposes assignments from configurable rules the planner can adjust. What I cannot find is the demand side — nothing ties planning to POS revenue, footfall or occupancy, no staffing requirement per shift, no labour cost against budget while the plan is still editable, and no sharing of staff across sites; the AI scheduler assigns open shifts by availability, preferences and qualifications, with no forecasting method documented beyond that. 6 7 10 11