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
Templates, recurring shifts and automatic schedule proposals built from availabilities, qualifications and target hours are documented, with several locations and roles, staffing and personnel costs shown per day or week, and published plans pushed to the app where staff can apply for open shifts. What I did not find is demand-based planning from a named source such as POS revenue, footfall or occupancy, staffing requirements per shift, or staff shared across sites — the proposal inputs are availability and hour targets, and beyond naming those inputs the vendor documents no forecasting method. 6 10