Workforce Demand Forecasting

Workforce demand forecasting estimates how much work will arrive and when it will arrive. The demand unit can be calls, chats, tickets, orders, visits, cases, or tasks. The forecast should use the same time interval, queue, channel, location, and skill detail needed for staffing decisions.

Demand forecasting is not the same as staffing forecasting. Demand forecasting predicts the work. Staffing forecasting converts that demand into people or hours after average handling time, occupancy, service targets, shrinkage, skills, and uncertainty are applied.

Workforce demand forecasting process

Collect consistent historical demand by the planning interval.
Mark missing data, system outages, one-time anomalies, and known events.
Backtest suitable methods on recent periods that were not used to fit the model.
Add known future drivers, such as campaigns, holidays, launches, or opening-hour changes.
Publish a baseline forecast and an uncertainty range by queue or work type.
Measure WAPE for error size and bias for repeated over- or under-forecasting.
Convert the approved demand forecast into staffing requirements and schedule coverage.

Common workforce demand forecasting methods

Useful methods include comparable-period averages, seasonal naive forecasts, exponential smoothing, ARIMA models, daily profiles, and multi-seasonal methods. The best method depends on the operation's data. Test models on the operation's own history instead of selecting one only because it is more complex.

Why this matters for planners and team leads

A weekly or monthly total can hide the peaks that create queues, overtime, and missed work. Forecast at the level where staffing can change. Contact centers may need 15-minute or 30-minute intervals, while project or field teams may make decisions by day or week.

Review demand error separately from staffing error. A demand forecast can be accurate while staffing still fails because handling time, shrinkage, attendance, skills, or the schedule were wrong. Keeping the layers separate makes the corrective action clear.

Example in practice

A support operation normally receives 80 calls between 09:00 and 09:30 on Monday. A recent product release creates a repeatable 25% increase, so the adjusted demand forecast is 100 calls for that interval. The planner keeps the release adjustment separate from the baseline so its effect can be reviewed later.

After the interval ends, actual demand is 108 calls. The team records the forecast error and checks whether the miss was isolated or part of a repeated low bias. The approved demand forecast then feeds handling time, queueing, shrinkage, and skill calculations for the staffing plan.