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
The planner side is real: drag-and-drop rotas with templates you can apply across any date range, roles with rates per hour or per shift, unlimited rotas and locations, and open shifts that notify eligible staff and update the rota once filled. The Pro plan adds labour forecasting — staff costs as a percentage of sales — and budget caps, though I found no public information on automatic roster proposals or on forecasting driven by a named sales data source. The test for me is whether the finished plan reaches my phone, and free mobile apps with push notifications do that. 2 6 7