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 — A shared calendar of shifts; no templates, no roles or qualifications, and no notion of how many people a shift needs.
3 — Shift templates and a weekly grid per location, with roles attached, but staffing needs and qualifications are the planner's memory rather than the system's.
5 — Templates, roles and qualifications, staffing requirements per shift, open shifts, multiple locations and departments, and coverage gaps shown before publication.
8 — 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 Skeptic
Templates, roles with certificate fields like the §34a Sachkundenachweis, staffing requirements per shift and central multi-location planning are all evidenced, and an automatic roster proposal exists as a paid add-on the planner can adjust and restart. Credit where due: the vendor says plainly that the "KI" is not learning from data but scoring thousands of plan variants against stored rules, availabilities and headcounts — but that means no demand source (POS revenue, footfall, occupancy) feeds the plan, and we found no public information on labour cost shown against budget while planning. 1 5 6