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 Shift Manager
Photo-uploading last week's wall chart turns it into a reusable template with shifts, departments and roles auto-filled, availability and time off show while I build, and sales-driven labor forecasting plus real-time labor-versus-sales tracking come from POS data. Open shifts exist via the Shift Pool and the mobile manager view sorts coverage by role and department. We found no public information on staffing requirements per shift, on a roster the tool proposes for me to accept or adjust, or on staff shared across locations — "advanced labor recommendations" on the top plan is as close as the pages get. 5 6 2 1