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
Schedules can be built from templates or generated automatically against demand forecasts and budgets, with skills, certifications and workload balance driving auto-assignment across multiple locations and countries — a planning engine, not a weekly grid. The pages never name the data source behind the forecast (no POS revenue, footfall or bookings figure), and cross-location staff sharing is only implied; labour cost is calculated instantly while planning with overrun alerts, which carries it partway toward the highest level. 7 6 1