Schedule Horizon and Planning Interval Selection

From WFM Labs

Schedule horizon refers to the length of the future period for which a workforce schedule is planned and published — ranging from same-day intraday planning to quarterly or annual coverage plans. Planning interval refers to the granularity of the time periods into which a scheduling day is divided, most commonly 15 or 30 minutes. These two parameters jointly define the resolution and reach of a scheduling system: the horizon determines how far in advance staffing decisions are committed, while the interval length determines how precisely demand fluctuations within a day can be represented and matched. Both parameters involve fundamental tradeoffs between forecast accuracy, scheduling flexibility, computational feasibility, and regulatory compliance.

Planning Interval Selection

Standard Interval Lengths

Contact centers most commonly use 15-minute or 30-minute intervals. Hourly intervals are used in some back-office and workforce planning contexts. Intervals shorter than 15 minutes (e.g., 5-minute) are technically feasible but rarely implemented in practice due to computational burden and the statistical instability of demand forecasts at very fine granularity.

The choice of interval length affects:

  • Forecast granularity: Volume forecasts disaggregated to 15-minute intervals capture intraday demand peaks more precisely than 30-minute intervals, where within-interval variation is averaged.
  • Erlang calculation precision: Erlang-C and Erlang-A calculations are performed per interval; shorter intervals produce more staffing requirement data points and allow finer-grained alignment between shift structure and demand.
  • Schedule complexity: Shorter intervals increase the number of constraint-satisfaction requirements in Schedule Generation, raising computational cost and solution time.

Arguments for 15-Minute Intervals

For synchronous voice channels and high-volume chat, 15-minute intervals are standard because:

  • Within-30-minute demand variation is operationally significant. A 30-minute interval that averages 100 calls may contain a 15-minute peak of 140 calls and a 15-minute trough of 60 calls; staffing to the average will cause service level degradation during the peak.
  • Service level targets for voice are typically measured over short windows (e.g., 80% within 20 seconds), making within-interval peaks directly actionable.[1]

Arguments for 30-Minute Intervals

For asynchronous channels (email, back-office, social media) and lower-volume environments:

  • Within-interval demand variation is less consequential because queue buffering absorbs short-term spikes.
  • Forecast accuracy at 15-minute granularity may be insufficient to justify the additional complexity; the standard error of a 15-minute forecast is higher relative to its mean than a 30-minute forecast.
  • Computational feasibility in scheduling optimization is improved with longer intervals, particularly relevant for smaller operations without enterprise WFM systems.

Multichannel Interval Consistency

Operations handling multiple channels may use different interval lengths per channel, maintaining 15-minute intervals for voice while using 30-minute or hourly intervals for email and back-office. WFM systems must reconcile these when planning blended agent schedules, since an agent handling both voice and email within a shift must be assigned to one channel at a time at the interval level.

Statistical Stability Considerations

Interval-level forecasts are subject to higher relative error at finer granularity. A 15-minute interval with an average of 20 calls has a higher coefficient of variation than a 30-minute interval averaging 40 calls, even with the same underlying arrival process. Probabilistic Scheduling approaches account for this uncertainty by expressing staffing requirements as distributions rather than point estimates, which partially mitigates the granularity risk.[2]

Schedule Horizon Selection

Common Horizon Lengths

Horizon Typical Use
Same-day (intraday) Real-time adjustments; see Real-Time Schedule Adjustment
1–3 days Short-range adjustments; Overtime and Voluntary Time Off (VTO) Management decisions
1–2 weeks Primary scheduling horizon; standard for most WFM cycle
4–8 weeks Agent preference bidding, vacation planning; see Schedule Bidding and Preference-Based Scheduling
Quarterly/Annual Capacity planning, headcount strategy; see Capacity Planning Methods

The primary scheduling horizon — the period for which shift assignments are finalized and published — is most commonly 1–2 weeks, with earlier drafts generated further in advance for agent preference collection.

Horizon and Forecast Accuracy

Longer horizons allow greater operational planning time but carry greater forecast uncertainty. A 6-week forecast for a specific 15-minute interval on a Tuesday morning carries substantially more error than a 3-day forecast. The horizon selected for final schedule publication should reflect the point at which forecast accuracy is sufficient to support confident staffing decisions, balanced against:

  • Agent notification requirements: Labor Law and Scheduling Compliance may mandate advance schedule publication (7–14 days) regardless of forecast uncertainty at that horizon.
  • Agent planning needs: Agents with personal obligations (childcare, second employment) require sufficient advance notice to arrange their lives; longer horizons improve employee experience even when forecast accuracy is lower.
  • Operational flexibility: Shorter horizons allow schedules to incorporate later, more accurate forecasts, reducing expected overstaffing and understaffing, but compress the time available for agent communication and preference processing.[3]

Rolling vs. Fixed Horizon Scheduling

  • Fixed horizon: Schedule is generated for a defined future period (e.g., the calendar week from Monday to Sunday) and published at a fixed point (e.g., 10 days prior). Simpler to administer and predictable for agents.
  • Rolling horizon: Schedule is continuously regenerated for a window of fixed length (e.g., always 14 days ahead). More responsive to forecast updates but requires more frequent scheduling cycles and can create agent confusion if schedule changes occur frequently.

Most contact centers use a fixed-horizon approach with defined exception processes for intraday and short-notice adjustments.

Horizon Effects on Scheduling Methods

The horizon interacts with the scheduling method employed:

Intraday Planning Interval =

Separate from the scheduling interval, intraday operations may use a shorter monitoring interval — sometimes called the reporting interval or adherence interval — for real-time performance tracking. Common practice is to monitor Adherence and Conformance at 15-minute intervals even when the scheduling interval is 30 minutes, allowing earlier detection of coverage gaps without adding complexity to the scheduling problem.

Maturity Model Considerations

Maturity Level Typical Practice
Level 1 30-minute or hourly intervals. Weekly or monthly scheduling horizon. Interval selection driven by convention rather than demand characteristics.
Level 2 15- or 30-minute intervals selected based on channel type. 1–2-week primary scheduling horizon. Fixed-horizon cycle with defined publication date.
Level 3 Interval length calibrated to channel and volume. Multichannel interval management. Horizon aligned with both forecast accuracy curve and regulatory advance notice requirements.

See WFM Labs Maturity Model.

Related Concepts

References

  1. ↑ Gans, N., Koole, G., & Mandelbaum, A. (2003). Telephone Call Centers: Tutorial, Review, and Research Prospects. Manufacturing and Service Operations Management, 5(2), 79–141.
  2. ↑ Koole, G. (2013). Call Center Mathematics. VU University Amsterdam.
  3. ↑ Gans, N., Koole, G., & Mandelbaum, A. (2003). Manufacturing and Service Operations Management, 5(2), 79–141.
Retrieved from "https://wiki.wfmlabs.org/w/index.php?title=Schedule_Horizon_and_Planning_Interval_Selection&oldid=875"