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 Skeptic
Weekly-schedule templates with a template manager, a qualification filter, work areas and an all-locations view are documented, and shifts are colour-coded against the number of required staff per shift, yellow marking an uncovered shift and blue a fully staffed one — a planning grid with real coverage signals. We found no public information on demand-based planning from a named source such as POS revenue or occupancy, on automatic roster proposals the planner accepts or adjusts, or on labour cost shown against budget; the 'intelligente Planungshilfe' and the beta KI-Assistent Staffo (daily usage limit, price may change after beta) are names without a documented method. 6 9 1 2 5