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
The Autoscheduler takes location, date range, people and budget, builds and assigns shifts in one pass, works around pre-scheduled shifts, and the manager can adjust by drag and drop before approving against minimum, target and maximum cover, with unfilled cover flagged and a fit-to-demand score on the draft. Demand forecasts are fed by named sources — sales, footfall, bookings and weather — and labour budgets are visible by site, day and hour while planning. We found no public information on staff being shared across locations, and the forecasting is branded as AI rather than documented as a method. 1 3 4 11