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
Week and day templates that can publish straight to staff, open shifts created from templates, and employees filtered by department, employee group and skills with colour-coded conflicts — plus an auto-schedule tool on the Pro plan and revenue forecasting and labour costs named in the tier lists. But we found no public information on staffing requirements per shift, costs checked against a budget while planning, or cross-location staff sharing, so this reads as suggestions the manager accepts or rejects, not a closed loop. 2 3 4