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 planner is a spreadsheet-style grid with drag-and-drop, reusable templates of repeating shift patterns, editing of up to 140 days at once and overnight shifts handled in reminders, reports and pay; rosters are published with change notifications, and facilities and departments are real fields in the product. A real-time labour-cost forecast appears while you schedule, which is the part I care about. We found no public information on qualifications or roles attached to shifts, staffing requirements per shift, coverage-gap views, demand-based planning from POS or occupancy data, or automatic roster proposals. 1 5 6 12