HiveDesk
<- Back to Blog

Workforce Planning vs. Forecasting in Call Centers — What Each One Does and How They Work Together

Vik Chadha
Vik Chadha · · Updated · 11 min read
Workforce Planning vs. Forecasting in Call Centers — What Each One Does and How They Work Together

In a call center, workforce forecasting and workforce planning are often used interchangeably. They are not the same thing. Forecasting is an input to planning. If you confuse them — or skip one — you end up with schedules that do not match demand, hiring that lags behind attrition, and costs that surprise you at the end of the quarter.

Forecasting answers: how much work is coming?

Planning answers: how many people do I need, when do I need them, and what does it cost?

Forecasting predicts the workload. Planning converts that prediction into staffing decisions. You cannot plan without a forecast, and a forecast without a plan is just a number that nobody acts on.

Side-by-side comparison

DimensionWorkforce forecastingWorkforce planning
Core questionHow many contacts will we receive?How many agents do we need?
Time horizonShort-term: daily, weekly, 30-day. Medium-term: monthly, quarterlyShort-term: weekly schedule. Medium-term: monthly headcount. Long-term: quarterly/annual budget
Primary inputsHistorical volume data, AHT trends, known events (campaigns, billing cycles, holidays)Forecast output, shrinkage, service level target, attrition rate, budget
Primary outputsPredicted contact volume by interval, day, week, monthRequired staff per interval, scheduled staff, hiring plan, labor budget
Who does itWFM analyst (or supervisor in smaller operations)WFM analyst + operations manager + HR (for hiring)
FrequencyWeekly (short-term), monthly (medium-term)Weekly (schedule), monthly (headcount review), quarterly (budget)
Key metricForecast accuracy — how close was the prediction to actual?Schedule efficiency, overtime %, headcount vs. plan

What forecasting actually involves

Short-term forecasting (next 1–4 weeks)

Short-term forecasting predicts contact volume at the interval level — typically 30-minute intervals — for the upcoming scheduling period. This is the forecast that determines next week's schedule.

Data sources:

  • Same day/week from the prior 4–8 weeks (recent pattern)
  • Same period from the prior year (seasonal pattern)
  • Known events: marketing campaigns, product launches, billing cycles, system changes, holidays

Method:

The simplest reliable approach for most call centers:

  1. Pull actual contact volume for the same day of week, for each of the last 4 weeks
  2. Calculate the average for each 30-minute interval
  3. Adjust for known events that will change volume (a billing cycle adds 15–20%, a holiday reduces volume by 30–50%)
  4. Apply a trend adjustment if volume has been consistently growing or declining

Example — forecasting Monday 10:00–10:30 AM:

WeekActual calls in this interval
4 weeks ago52
3 weeks ago48
2 weeks ago55
Last week51
Average51.5

If no known events will change the pattern, the forecast for next Monday 10:00–10:30 is approximately 52 calls.

If a billing statement mails this Friday and historically billing cycles increase Monday volume by 18%, the adjusted forecast is 52 × 1.18 = 61 calls.

Medium-term forecasting (1–6 months)

Medium-term forecasting predicts monthly volume to inform hiring decisions and budget planning. It does not need interval-level detail — monthly or weekly totals are sufficient.

Data sources:

  • Monthly volume for the trailing 12 months
  • Year-over-year growth rate
  • Known business changes (new client for BPOs, product launch, market expansion)

Why it matters for planning: If medium-term volume is growing at 5% per quarter, and you are at 100 agents today, you will need approximately 105 agents next quarter — before accounting for attrition. If your attrition rate is 3% per month, you need to hire 3 replacements plus 5 growth hires = 8 hires in the next quarter just to maintain coverage. Without the forecast, the hiring plan is reactive rather than proactive.

Measuring forecast accuracy

Calculation:

Forecast accuracy (%) = 100 − |((Actual − Forecast) / Forecast) × 100|

Accuracy levelAssessmentTypical cause of inaccuracy
95%+Excellent
90–95%GoodMinor variability, acceptable
85–90%Needs improvementMissing event adjustments, insufficient historical data, or outdated trend assumptions
Below 85%UnreliableForecast method is broken or data is wrong. Schedules built on this forecast will be consistently over or understaffed

Track bias separately from accuracy. If your forecast is 92% accurate but always over-predicts (you consistently forecast more calls than arrive), the schedule is consistently overstaffed. If it always under-predicts, you are consistently understaffed and covering the gap with overtime. Bias tells you which direction to adjust.

What planning actually involves

Planning takes the forecast and converts it into staffing decisions. The forecast says "520 calls will arrive between 10 AM and noon on Monday." Planning says "we need 28 agents on the phones during that window, which means scheduling 40 agents to account for shrinkage."

From forecast to required staff

The calculation chain:

StepCalculationExample
1. WorkloadForecast volume × AHT (seconds) / 3,600120 calls × 360 sec / 3,600 = 12 hours of work in a 30-min interval
2. Base staff neededWorkload / interval length (hours)12 / 0.5 = 24 agents minimum (at 100% occupancy)
3. Staff for service levelApply Erlang C or WFM tool for target SL (e.g., 80/20)Approximately 28 agents for 80/20 with this workload
4. Scheduled staffStaff for SL / (1 − shrinkage)28 / (1 − 0.30) = 40 agents scheduled

Each step depends on an accurate input. If the forecast is wrong (step 1), the workload is wrong. If AHT has changed and you are using an old number, the workload is wrong. If shrinkage is underestimated, you schedule too few agents. The planning output is only as good as its inputs.

From required staff to the schedule

The schedule translates the required-staff-per-interval calculation into actual shift assignments:

From required staff to the hiring plan

Planning also determines whether you have enough agents to fill the schedule — and if not, when to hire.

Planning inputValueSource
Current headcount100 agentsHR records
Required headcount (from forecast + staffing calculation)105 agentsPlanning calculation
Monthly attrition rate3% (3 departures/month)Attrition tracking
Recruiting lead time3 weeksHR
Training time4 weeksTraining team
Hires needed per month3 replacements + growth hiresPlanning output
Hiring must start7 weeks before agents are needed on phonesRecruiting + training lead time

Without this planning step, hiring is reactive — you notice you are short-staffed, start recruiting, and spend 7 weeks covering the gap with mandatory overtime while the new hires go through training.

What happens when forecasting fails

Forecasting failurePlanning consequenceOperational impact
Volume under-predictedNot enough agents scheduledService level misses, overtime to cover gaps, agent burnout
Volume over-predictedToo many agents scheduledLow occupancy, agents idle, wasted labor cost
Daily total correct but interval distribution wrongRight number of agents but in the wrong intervalsService level misses during peaks even though daily staffing looks adequate
Trend not captured (volume growing 5%/month but forecast is flat)Headcount plan does not include growth hiresProgressive understaffing — gets worse each month
Events not included (billing cycle, campaign)Normal staffing on a high-volume dayService level collapses on event days, emergency overtime

Every forecasting failure creates a planning failure. But the reverse is also true — a perfect forecast produces nothing if nobody converts it into a staffing plan. An operation that forecasts 15% volume growth but does not hire is as understaffed as one that did not see the growth coming.

What happens when planning fails

Planning failureRoot causeOperational impact
Chronic overtime (5%+ of hours every week)Planning did not account for shrinkage, or did not hire to cover attrition$156,000+/year in overtime premium for a 100-agent operation at 10% OT
Schedule does not match volumePlanning used equal shifts instead of volume-matched staffingOverstaffed in off-peak, understaffed in peak — both cost money
New hires not ready when neededPlanning did not account for recruiting + training lead time7-week gap between departure and replacement being productive
Budget surprisePlanning did not convert headcount needs into labor cost projectionsOperations runs over budget, reactive cost cuts follow
Absenteeism not bufferedPlanning used 0% absence assumption or underestimated shrinkageEvery sick call creates a service level miss

How they work together in practice

The forecasting-planning cycle runs continuously. It is not a one-time exercise — it is a recurring process that adjusts as reality diverges from prediction.

Weekly cycle:

DayForecasting activityPlanning activity
MondayCompare last week's forecast to actual — calculate accuracy, note biasReview last week's service level, overtime, and adherence
TuesdayAdjust this week's remaining intervals if volume is tracking differently than forecastAdjust this week's schedule if needed (move training, shift breaks)
WednesdayBuild next week's interval-level forecast
ThursdayBuild next week's schedule from the forecast
FridayFinalize forecastPublish next week's schedule (2 weeks ahead target)

Monthly cycle:

ActivityForecastingPlanning
Volume reviewCompare monthly forecast to actual. Update trend assumptions
Headcount reviewCompare actual headcount to plan. Calculate hires needed for next month
Shrinkage recalculationRecalculate actual shrinkage from time tracking data. Adjust scheduling assumptions if actual differs from plan
Attrition reviewUpdate attrition rate and replacement hiring timeline
Budget checkCompare actual labor cost to budget. Flag if trending over

Quarterly cycle:

ActivityForecastingPlanning
Trend analysisReview 12-month volume trend, seasonal patterns, year-over-year growth
Headcount planProject required headcount for next quarter based on volume forecast + attrition
Budget planningConvert headcount plan to labor cost projection
Benchmark reviewCompare forecast accuracy to targetCompare schedule efficiency, overtime %, cost per call to benchmarks

For BPOs: forecasting and planning per client

BPOs must forecast and plan per client account, not just in aggregate. Each client has different volume patterns, AHT, service level requirements, and staffing needs.

BPO complexityImpact on forecastingImpact on planning
Different volume patterns per clientEach account needs its own forecast — Client A peaks mornings, Client B peaks afternoonsSchedules must be built per account, with cross-trained agents for flexibility
Different SLA targetsClient A requires 80/20, Client B requires 90/10 — the 90/10 client needs proportionally more agents per callStaffing calculation uses different service level targets per account
Client volume changesA client may ramp up or wind down volume with limited noticePlanning must include contract review and early warning of volume changes
Billable utilizationNon-billable time (bench, training) affects revenuePlanning must minimize bench time by aligning hiring with confirmed volume

An aggregate forecast that predicts 5,000 total calls across all clients is useless for planning if it does not show that Client A will receive 3,000 and Client B will receive 2,000 — because the agents are not interchangeable between accounts (unless cross-trained).

Vik Chadha

About the Author

Vik Chadha

Founder of HiveDesk. Has been helping businesses manage remote teams with time tracking and workforce management solutions since 2011.

Try HiveDesk Free for 14 Days

Increase productivity, take screenshots, track time and cost, and bring accountability to your team. $5/user/month, all features included.