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
Templates filterable by team, position or employee and duplicable over ten weeks, positions ranked primary and secondary, and a Smart Planner that proposes full schedules from constraint sets — favouring the lowest hourly rate and the lowest hour balances — are documented. Staffing forecasts are advertised as a higher-tier feature and a cash-register connection exists, but we found no public information naming the data source the forecast uses, showing labour cost against budget, or describing cross-location staff sharing. It does propose rosters and prices people by rate when it does; the forecast input stays behind the word AI. 5 6 2 2