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
Shifts go onto people by drag-and-drop with the software constantly checking collisions, availabilities and working-time limits, planning runs per location or across all of them, and an algorithm can propose a whole roster in minutes — as a paid add-on — from required people per shift, regular hours, absences and qualifications, with manual adjustment anytime. I respect that the vendor explains its method: structured evaluation of thousands of plan variants, not learning from data. We found no public information on planning from sales, footfall or booking figures, or on labour cost shown against budget while planning. 1 5 6 7