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 Shift Manager
The captures show a real scheduling product: collaborative planning, rosters published to staff by SMS, scaling from one restaurant to multi-site franchises, with real-time productivity ratios, cash-register (POS) integration and predictive planning claimed on the Time plan. But I found no shift templates, no qualifications attached to shifts, no open shifts or coverage-gap view while planning, and no staffing requirements or automatic roster proposals. That is more than a basic published grid, yet not the demand-driven planning loop I build my Thursday night around. 2 2 1 2