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
Automatic shift planning, schedule templates, open shifts and shift bids are shown, and every location's schedule is visible in real time — but the demand side stays thin: no POS, footfall, occupancy or booking source is named for forecasting, and the optimisation is sold as "AI-driven" with no documented method, which for me is a request to see the method. Labour costs and wage percentage appear as KPIs rather than a budget check inside the still-editable plan, and we found no public information on sharing staff across sites. 6 7 1 2 7