Short answer
Retail workforce planning converts customer and operating demand into required hours, roles, skills, and availability, then compares that requirement with current capacity. Build ranges rather than one forecast, protect non-selling work, test skill coverage by interval, and assign each gap to hiring, training, mobility, process, or service decisions.
Separate planning from scheduling
Retail workforce planning and workforce management are connected, but they answer different questions.
| Horizon | Planning question | Typical output |
|---|---|---|
| Long range | Which store formats, regions, roles, and capabilities will the strategy require? | Workforce scenarios and capability priorities |
| Seasonal | What demand, campaign, delivery, opening, and leave patterns could change capacity? | Hiring, training, mobility, and budget plan |
| Weekly | Which hours and skills should each store or department have available? | Capacity envelope and coverage requirements |
| Daily | Which named employees work which shifts and tasks? | Schedule and same-day adjustments |
A scheduling system can optimise assignments inside the available workforce. It cannot decide whether the role design, service promise, training lead time, or workforce strategy is right. A workforce plan provides those boundaries and actions.
For the cross-business process, use the complete workforce planning guide. This retail guide starts one level closer to the operation: customer service, task workload, trading hours, and store capability.
Define the service before calculating labour
“Match labour to sales” is not a service definition. Two periods with similar sales can require different work because of product mix, returns, deliveries, replenishment, appointments, queue patterns, loss-prevention needs, or promotional change.
Create a service-and-work map:
| Work stream | Demand unit | Service or completion rule | Required capability |
|---|---|---|---|
| Checkout | Transactions by interval | Agreed queue or coverage rule | Till operation and exception handling |
| Assisted selling | Customer requests or appointments | Coverage by department and interval | Product and service knowledge |
| Returns | Return transactions | Named coverage for approvals | Returns process and authorisation |
| Replenishment | Cases, units, or bays | Complete by agreed time | Stock handling and equipment |
| Online fulfilment | Orders and promised windows | Pick and handoff standard | Picking, substitution, and customer handoff |
| Opening and closing | Store event | Controlled task checklist | Keyholding and local authorisation |
| Training and handover | People or process change | Protected time | Trainer or experienced colleague |
Use internal observation and operating records to estimate work, then review the assumptions with the people who perform it. A single “sales per labour hour” ratio can hide queues, training, recovery, and required control tasks.
Build the demand range
Start with store and interval data, not a national average:
- transactions, footfall, appointments, orders, deliveries, and returns;
- product launch, promotion, markdown, and stocktake dates;
- local events, school or public holidays, weather scenarios, and transport changes;
- opening hours and store format;
- historical intraday pattern and comparable event weeks;
- known construction, closure, or system change;
- the confidence and revision history of each input.
Official market data can provide context. The US Census Bureau's retail data service publishes monthly retail trade releases and historical series. The UK Office for National Statistics retail dataset publishes retail sales estimates by sector and retains previous versions when data is revised. Neither series is a store-level workload forecast. Use it to challenge assumptions about the wider market, then rely on local demand drivers for the operating plan.
Build at least three scenarios:
| Scenario | Meaning | Action question |
|---|---|---|
| Lower demand | Plausible low end, not a target | Which flexible capacity can be reduced without removing minimum skill or control coverage? |
| Base | Current best planning assumption | What capacity and capability should be committed? |
| Higher demand | Plausible high end | Which options can add capacity, change service, or defer work? |
Record which event would move the plan from one scenario to another. A range is useful only when it changes a decision.
Translate demand into productive capacity
For each work stream:
Required work hours = demand units x observed minutes per unit / 60
Use one accounting convention throughout the plan:
- Put variable customer and task work on the demand side.
- Add planned fixed operational work that must be staffed in the interval, such as opening, closing, cleaning, cash control, safety checks, delivery setup, and a handover when the model treats that handover as required work.
- Start the supply side with paid hours, then deduct only paid time that is unavailable for the modelled demand and has not already been counted there, such as breaks or a separate briefing or training session.
Never count the same activity as required demand and also deduct it from supply. State where briefing, training, handover, meetings, and other paid activities sit in the chosen convention. Do not quietly assume every paid minute is customer-facing capacity.
Then compare requirement with usable supply:
Usable capacity = contracted or available hours minus planned absence, protected activity, and other unavailable time
Keep headcount, paid hours, and productive hours separate. Ten employees with short overlapping availability are not equivalent to ten employees whose hours cover the trading pattern. Forty hours from people without the required approval or product skill do not close a skilled-coverage gap.
Add the capability and availability layer
Create a role-by-interval matrix:
| Interval | Required people | Till | Returns approval | Keyholder | Product specialist | Fulfilment |
|---|---|---|---|---|---|---|
| Example interval | Range | Minimum or range | Minimum or range | Minimum | Minimum or range | Minimum or range |
This is a planning matrix, not an employee scorecard. Record only job-relevant skills under a defined proficiency method. Let employees and managers correct inaccurate records. Distinguish trained, recently observed in practice, and authorised where the difference matters.
Include:
- availability by interval and contract;
- planned leave and known training;
- realistic hiring and onboarding time;
- transfer or temporary assignment options;
- skill expiry or authorisation rules;
- single points of dependency;
- roles needed for safe and lawful operation.
The UK Health and Safety Executive's shift-work guidance treats workload, breaks, training, facilities, supervision, and handovers as connected parts of shift design. Local employment law, collective agreements, contracts, predictive-scheduling rules, and consultation requirements vary across US and UK locations. Review them before changing hours or work patterns.
Acas states that proposed UK contract changes may require genuine consultation with affected employees and representatives, depending on the circumstances. Its employer guidance on contract changes is a useful prompt to involve the right owner before a planning scenario becomes a schedule change.
Fictional worked store example
North Street Home is a fictional UK retailer planning a Saturday promotion. These figures are invented to demonstrate the method.
For the noon-to-four interval, the store creates a demand range:
| Work stream | Lower | Base | Higher | Planning assumption |
|---|---|---|---|---|
| Checkout | 14 hours | 17 hours | 20 hours | Transactions multiplied by observed handling time |
| Assisted selling | 7 hours | 9 hours | 12 hours | Department coverage plus expected requests |
| Replenishment | 6 hours | 8 hours | 10 hours | Delivery and promotion volume |
| Returns | 2 hours | 3 hours | 4 hours | Expected transactions plus exception time |
| Fixed control and handover | 4 hours | 4 hours | 4 hours | Opening handoff, cash and floor controls |
| Total productive work | 33 hours | 41 hours | 50 hours | Four-hour interval |
The base scenario implies slightly more than ten people working productively on average across the interval. The draft schedule contains 44 paid hours. Under this example's convention, the handover is already included on the demand side, while breaks and a separate paid team briefing are excluded from demand and deducted once from supply. They reduce usable capacity to 40 hours. The schedule also includes only one person authorised for returns and no product specialist after three o'clock.
The issue is not simply “one hour short.” The store has a small base-capacity gap and two skill-coverage gaps.
The planner records options:
| Option | Helps with | Constraint | Decision trigger |
|---|---|---|---|
| Move the paid briefing before noon within scheduled hours | Base capacity in the peak interval | Attendance, shift coverage, and handover quality | Use if all participants can attend without creating an earlier gap |
| Add a trained four-hour shift | Checkout and returns | Availability and budget | Use when advance demand reaches the higher threshold |
| Cross-train an existing colleague | Future returns coverage | Training and observed-practice time | Complete before the next promotion |
| Change appointment capacity | Assisted selling | Customer promise | Use only before bookings are confirmed |
| Defer non-urgent replenishment | Short peak gap | Aisle and stock impact | Use within agreed store rule |
The store chooses one immediate schedule adjustment and one cross-training action. It does not claim the promotion will follow the base forecast. It checks transactions, queues, unfinished work, exceptions, breaks, and employee observations after the event, then updates the assumptions.
Convert gaps into a workforce action plan
For every gap, select from the full response set:
| Gap | Possible responses |
|---|---|
| More hours needed briefly | Availability change by agreement, temporary capacity, task timing, or service adjustment |
| Persistent capacity gap | Hiring, contract mix review, operating redesign, or store-hours decision |
| Skill coverage gap | Training, supervised practice, authorisation, mobility, or external hiring |
| Single-person dependency | Knowledge transfer, documented handover, deputy coverage, or role redesign |
| Demand uncertainty | Better event data, smaller commitment, trigger-based option, or faster review |
| Availability mismatch | Recruitment proposition, scheduling process, contract review, or service-window change |
Do not assume hiring is always the answer. Do not assume retention, mobility, or cross-training will work on demand. Give each option an owner, cost, lead time, evidence requirement, and stop or change rule.
Use a planning ledger:
- demand range and confidence;
- required variable work and fixed operational activity;
- paid supply, each unavailable-time deduction, and usable capability coverage;
- gap by interval, role, and skill;
- selected workforce or service action;
- owner and decision date;
- leading evidence and outcome measure;
- review and assumption update.
Employee conversations can improve assumptions about handovers, training, task sequence, and availability constraints. They remain one evidence source. They do not reveal a guaranteed retention outcome or predict which employee will leave.
After the planning method is defined, review the Lontra product approach if guided conversations could collect store knowledge for a specific assumption or action. Verify participant access, languages, group reporting, permissions, source review, routing, export, and fit with the retailer's planning and scheduling systems.
A useful retail workforce plan shows how a service promise becomes work, how work becomes capacity and capability, and how each gap becomes a decision. Its quality appears after the period, when planners compare assumptions with reality and improve the next scenario.
