Demand-based staff scheduling builds each store roster around an hour-by-hour forecast of customer demand, instead of a fixed weekly template. Staff hours follow footfall and sales, so you stop paying for idle cover in quiet hours and stop under-resourcing the peaks that drive conversion.
Why fixed templates leak margin
A template roster repeats the same shift pattern each week, tuned lightly by a manager who knows the store. It is fast to run, and that is its appeal. The problem is that it encodes an assumption that demand is roughly flat across the week and the day, which is almost never true in retail.
The result is a structural gap between when staff are paid and when customers arrive. On a single day the gap looks trivial: a couple of quiet hours over-covered, one peak hour stretched. Across a year and an estate, it is one of the largest recoverable costs in the business, because labour is usually the biggest controllable line after cost of goods.
The four moving parts
Demand-based scheduling has four components. Skip any one and it does not work.
- A demand forecast at the store and daypart level. Not a chain average. Each store has its own rhythm, and you staff to the hour, so the forecast has to be that granular. See demand and footfall forecasting.
- The signals that move demand. Day of week, season, paydays, weather, promotions and local events all shift footfall. A model that ignores them mis-staffs the days that matter most.
- An optimisation step. Given the forecast and your constraints (contracts, availability, skills, compliance), search the roster options for the lowest-cost one that still covers demand. See staff scheduling optimisation.
- A baseline and measurement. Track labour cost-to-sales and service against an agreed starting point, so you can prove the change worked.
A worked example
Take a grocery store with a sharp 5pm to 7pm checkout peak and quiet mornings. Under a template, the opening crew is sized for an average that fits neither end of the day: too many hands at 9am, too few tills at 6pm. Queues build at the most valuable hour, and some shoppers abandon the basket or switch to a closer store.
Rebuild the roster from a demand forecast and the hours shift: fewer at the quiet open, more at the evening peak, with no necessary increase in total hours. The checkout peak is covered, the morning stops over-spending, and the change is measured against the baseline so finance can see it is real. This matters because, as retail operations research shows, labour moderates how traffic becomes sales; the peak you under-cover is the revenue you cap.
How to move without disrupting stores
The risk operators worry about is chaos: new rosters that managers will not run and staff will not accept. The way to avoid it is sequence, not speed.
- Start with a scan, not a rollout. Quantify the gap in a sample of stores and agree the baseline first.
- Pilot in a small group. Prove the change against the baseline before touching the estate. A documented traffic-based labour planning approach exists precisely so this can be done methodically.
- Give managers tuned templates. Planners adjust a roster that is already shaped to their store, rather than building from a blank grid, so the local fit adds no manual effort.
- Work within contracts and fairness rules. Demand-matched does not mean unstable. Constraints on availability, minimum shifts and fairness are inputs to the optimisation, not casualties of it.
What good looks like
A mature demand-based operation runs forecasts per store automatically, refreshes rosters on a regular cadence, measures accuracy and labour cost-to-sales continuously, and improves both over time. It is less a project than a habit. Our approach walks through the five stages we use to get there.