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 Payroll Officer
Required shifts with minimum, maximum and exact occupancy per department and team, POS revenue flowing back into the plan, and an auto-scheduler that proposes a complete schedule from contract hours, skills and rules, applied or discarded with total labour cost and labour-cost percentage shown on the draft, plus a loaning function across teams and per-shift recommendations that explain themselves with a Why button. It stays below the top because the forecast is sold as AI rather than a documented method, drafting covers one department at a time, and applying a proposal is all-or-nothing with no undo. 6 6 7 1 13 1