From forecast to intraday: the complete WFM planning loop
How demand, workload, staffing, schedules, real-time control, and learning connect—without treating the forecast as a verdict.
Workforce management is often reduced to a forecast file and a schedule. The actual system is a loop: understand demand, translate it into workload, choose a service promise, calculate required capacity, build a humane schedule, operate the day, and feed what happened back into the next plan.
The gap between theoretical requirement and real coverage is not small. Shrinkage commonly consumes
of paid time. If that time is ignored until the schedule is published, training, coaching, meetings, and absence become surprises the operation pays for with queues and pressure.
Step 1: define the demand
Count work at the grain where capacity decisions happen. Voice and synchronous chat need interval arrivals. Email and persistent messaging need arrival volume plus age and due-date behavior. Separate new demand from reopens, transfers, spam, incidents, and work created by your own process failures.
Segment only where the work genuinely differs: language, channel, skill, severity, customer tier, or operating hours. Too little segmentation hides risk; too much creates forecasts with no stable signal.
Step 2: forecast a range
Start with a transparent baseline such as recent comparable periods, day-of-week patterns, and known events. Add product launches, billing cycles, campaigns, holidays, incidents, and policy changes as explicit adjustments.
Publish a base, low, and high case. The point is not to look uncertain; it is to make uncertainty operable. Record forecast error by segment and horizon so teams learn where extra caution is warranted.
The forecasting definition and forecasting guide cover the underlying mechanics.
Step 3: translate volume into workload
Multiply eligible volume by the correct handle or work time, including after-contact work. Use distributions where long cases matter. For chat, model concurrency as an observed operating curve, not a universal multiplier. For asynchronous work, include backlog clearance and due-date commitments.