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 planning is real here: forecasted sales, delivery orders and foot traffic feed auto-built templates, the POS integration feeds sales data into the schedule, and hour and wage budgets with real-time variance tracking put labour cost in front of the planner while the plan is still editable — my headline test, and it passes. Auto-fill weighs staff availability, training and cost with configurable priorities such as lowest cost, and real-time sales graphs compare forecast against actual. What I did not find: staff shared across sites, and every optimiser is called AI with no documented forecasting method, which I read as a vendor not yet willing to show its maths. 6 7 6 7