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 Operations Director
One-click auto-assign fills shifts from stated coverage input using availability and qualifications, rules are honored during auto-assign, and unlimited job sites come with labor sharing between departments and locations plus OpenShifts to close gaps — most of my daily planning loop is there. What the captured pages do not show is forecasting driven by a named data source: labour forecasting and scheduled-versus-budgeted hours appear as tools, but nothing documents the method or a POS or occupancy feed behind it. 2 5 6 1 5