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 Payroll Officer
The vendor documents automatic, algorithm-based roster generation directly from demand data — production requirements via SAP S/4HANA and connections to ERP, APS and MES systems — with qualification management (shyftskills) ensuring critical positions are staffed only with certified employees and optionally fully automatic replacement of short-term absences. Preferences, wish-shift applications and a traffic-light corridor around weekly contractual hours round out the planning picture; we found no public information on labour cost against budget while planning, cross-location staff sharing, or the forecasting method behind the KI-supported planning claim. 1 3 4 5 6