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
Weekly-plan templates that import with or without assignments, qualifications and work areas on staff, several locations with an all-locations view, and open shifts with yellow and blue coverage signalling while planning — the planner genuinely sees gaps before publishing. I found no public information on staffing requirements driven by a named demand source, on automatic roster proposals beyond a beta AI assistant with a daily usage limit, or on labour cost against budget while planning. It is a capable plan-builder, not a demand planner. 5 6 9 2 5