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
Algorithm-based roster generation and demand-based planning are well documented: plans are created automatically directly from demand data, fed from production requirements via SAP S/4HANA and ERP, APS and MES connections, with qualification management (shyftskills) ensuring critical positions are staffed only with certified employees, open shifts staff can claim, and fully automatic backfilling of short-notice absences. We found no public information on labour cost shown against budget while planning or on cross-location staff sharing. Planning is marketed as "KI-unterstützt", and for a works agreement my colleagues and I need the method documented so we know which rule or demand figure drove each assignment. 1 3 4