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
Demand-driven planning is properly evidenced: forecasts from sales, footfall, bookings and weather, minimum/target/maximum cover per shift, labour budgets by site, day and hour, and an Autoscheduler that takes budget as an input, builds shifts with people attached in one pass, and hands the manager a draft with a fit-to-demand score, rule warnings and drag-and-drop editing before anything is published. Budget and per-schedule cost visibility sit inside the scheduler itself, which is exactly what I want while a plan is still editable. Two gaps decided the top end: we found no public information on staff being shared and rostered across locations, and the forecasting is labelled AI with no public account of the method. 1 3 4 9 11