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
The autoscheduler both creates and staffs shifts in one pass against contracted hours, availability, skills, rest between shifts and a confirmed budget, flags rule breaks before publish, and hands the planner an editable draft with a fit-to-demand score; cover is set as minimum, target and maximum with unfilled cover flagged, and forecasting draws on named sources — sales, footfall, bookings and weather. Pre-scheduled shifts count against budgets and forecasts. The vendor calls the forecasting AI without documenting the method, and we found no public information comparing forecast, proposal and actual hours in one place, so I stop at the strong-proposal level. 1 3 4 11