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 Works Council Advocate
Schedule templates, shift bids, shift exchanges and open shifts are documented together with real-time schedule visibility across every location, and the vendor claims automatic planning that factors KPIs, working-time rules and AI-driven optimisations. We found no public information on a named demand data source such as POS revenue or footfall feeding the plan, on accepting or adjusting automatic proposals, or on cross-location staff sharing; and as a works council I note the optimisation is presented as AI with no documented method behind it. 6 7 2 7