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
There is real planning machinery here: roster templates with positions that layer or replace shifts, filtering by site and position, open shifts with a best-match list and unavailable staff shown separately, and the labour budget compared week by week while the roster is still editable. But I found no public information tying a roster to demand — no POS, occupancy or bookings feed appears on any page I read — and the AI rostering drafts from a text description via an assistant skill rather than from demand data, so the loop my locations need is not documented. 4 7 1 3