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
Shift templates carry working time and a role and drop by drag-and-drop onto a weekly grid, open shifts cover short-notice gaps, and the planner can enter a staffing-requirement figure and generate a roster from self-defined rules, then accept, reject or generate an alternative — a real proposal function, not just a grid to draw on. We found no public information on demand-based planning from a named data source such as POS revenue or occupancy, labour cost shown against budget while planning, or staff sharing across locations. 1 5 6