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 Frontline Employee
Required shifts can be set per team and department with minimum, maximum or exact staffing, and the auto-scheduler proposes a full week from availability, approved absences, contract hours, skills and the account's scheduling rules, which the planner reviews and applies or discards — never auto-published. POS revenue flows back into the schedule and a forecast step shows expected turnover, the draft summary shows total labour cost and labour cost as a share of expected turnover, and a Why? button explains each per-shift recommendation; a loaning function lets one person be scheduled across teams. It falls short of the top because the vendor brands the proposal as AI rather than documenting a forecasting method, and comparing forecast, proposal and actual hours in one place is not shown. 7 6 6 1 2