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
Automatic shift planning, schedule templates, shift bids and open shifts are documented, with every location's schedules visible in real time and KPIs such as labour costs and wage percentage factored into planning — this proposes a roster rather than merely drawing one. The demand side stays vague, though: forecasting is named as a module and optimisation is driven by KPIs, but we found no public information tying proposals to a named demand source such as POS revenue, and the optimisation is sold as AI rather than documented. 6 7 2 7