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 Smart Planner is documented down to its rules: it proposes schedules from constraints the planner sets (availability, daily amplitude, weekly rest days), assigns by priority rules from lowest hourly rate to standard-over-extras contracts, and the top tier carries staffing forecasts; templates can be built from filtered team or position views and applied over ten weeks. We found no public information naming the demand source behind the forecast, labour cost shown against budget while planning, or staff shared across sites, so the proposal engine is real but the demand loop is not shown. 2 5 6 2