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 Frontline Employee
Templates with qualifications, open shifts and labour sharing across sites are documented, and one-click auto-assign builds a roster that honours the scheduling rules — a planner gets real help, not just a grid. What keeps it below the top bands is demand: labor forecasting and scheduled-versus-budgeted hours are named, but no captured page names a data source like POS sales driving the forecast, and the forecasting method itself is not documented. For me the plan matters mostly once it lands on my phone, and that handoff is covered elsewhere in the pages. 6 5 2 1