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
Shift cards carry custom requirements and while planning you are shown exactly the employees who fit them, which is the qualification guard I want before someone lands wrongly on the till. Automatic roster proposals from an algorithm weighing rules, skills and fairness, demand and revenue-based planning with till data flowing into the plan, staffing requirements per shift, labour cost and time accounts held against budget, open shifts and templates are all documented. The pages show planning all locations and teams in one place, but we found no public information on staff being shared across locations, so I stop just short of the top of this band. 5 5 6 6 6 2