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
The auto-scheduler is documented with unusual candour — required shifts, availability, absences, contract hours, overtime balances and skills as named inputs, three optimisation strategies, nothing published automatically, apply all-or-nothing — and required shifts with minimum, maximum and exact occupancy exist per department and team. But the documented inputs contain no revenue figure: POS revenue flows back so the plan "weiß, was die Schicht gebracht hat" and a permission-gated turnover forecast step exists, and I found no evidence the optimiser consumes either; labour-cost draft metrics and budget management sit on Premium, and cross-department staffing appears only as a loaning function across teams. The vendor also brands the feature "Shiftbase's AI" rather than publishing a forecasting method. 6 7 13 6 1 2