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
| Dimension | Workforce forecasting | Workforce planning |
|---|---|---|
| Core question | How many contacts will we receive? | How many agents do we need? |
| Time horizon | Short-term: daily, weekly, 30-day. Medium-term: monthly, quarterly | Short-term: weekly schedule. Medium-term: monthly headcount. Long-term: quarterly/annual budget |
| Primary inputs | Historical volume data, AHT trends, known events (campaigns, billing cycles, holidays) | Forecast output, shrinkage, service level target, attrition rate, budget |
| Primary outputs | Predicted contact volume by interval, day, week, month | Required staff per interval, scheduled staff, hiring plan, labor budget |
| Who does it | WFM analyst (or supervisor in smaller operations) | WFM analyst + operations manager + HR (for hiring) |
| Frequency | Weekly (short-term), monthly (medium-term) | Weekly (schedule), monthly (headcount review), quarterly (budget) |
| Key metric | Forecast 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:
- Pull actual contact volume for the same day of week, for each of the last 4 weeks
- Calculate the average for each 30-minute interval
- Adjust for known events that will change volume (a billing cycle adds 15–20%, a holiday reduces volume by 30–50%)
- Apply a trend adjustment if volume has been consistently growing or declining
Example — forecasting Monday 10:00–10:30 AM:
| Week | Actual calls in this interval |
|---|---|
| 4 weeks ago | 52 |
| 3 weeks ago | 48 |
| 2 weeks ago | 55 |
| Last week | 51 |
| Average | 51.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 level | Assessment | Typical cause of inaccuracy |
|---|---|---|
| 95%+ | Excellent | — |
| 90–95% | Good | Minor variability, acceptable |
| 85–90% | Needs improvement | Missing event adjustments, insufficient historical data, or outdated trend assumptions |
| Below 85% | Unreliable | Forecast 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:
| Step | Calculation | Example |
|---|---|---|
| 1. Workload | Forecast volume × AHT (seconds) / 3,600 | 120 calls × 360 sec / 3,600 = 12 hours of work in a 30-min interval |
| 2. Base staff needed | Workload / interval length (hours) | 12 / 0.5 = 24 agents minimum (at 100% occupancy) |
| 3. Staff for service level | Apply Erlang C or WFM tool for target SL (e.g., 80/20) | Approximately 28 agents for 80/20 with this workload |
| 4. Scheduled staff | Staff 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:
- Which agents work which shift
- Where breaks are placed (staggered so net available agents stay above the requirement)
- How days off are distributed
- How time-off requests are handled against coverage requirements
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 input | Value | Source |
|---|---|---|
| Current headcount | 100 agents | HR records |
| Required headcount (from forecast + staffing calculation) | 105 agents | Planning calculation |
| Monthly attrition rate | 3% (3 departures/month) | Attrition tracking |
| Recruiting lead time | 3 weeks | HR |
| Training time | 4 weeks | Training team |
| Hires needed per month | 3 replacements + growth hires | Planning output |
| Hiring must start | 7 weeks before agents are needed on phones | Recruiting + 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 failure | Planning consequence | Operational impact |
|---|---|---|
| Volume under-predicted | Not enough agents scheduled | Service level misses, overtime to cover gaps, agent burnout |
| Volume over-predicted | Too many agents scheduled | Low occupancy, agents idle, wasted labor cost |
| Daily total correct but interval distribution wrong | Right number of agents but in the wrong intervals | Service 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 hires | Progressive understaffing — gets worse each month |
| Events not included (billing cycle, campaign) | Normal staffing on a high-volume day | Service 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 failure | Root cause | Operational 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 volume | Planning used equal shifts instead of volume-matched staffing | Overstaffed in off-peak, understaffed in peak — both cost money |
| New hires not ready when needed | Planning did not account for recruiting + training lead time | 7-week gap between departure and replacement being productive |
| Budget surprise | Planning did not convert headcount needs into labor cost projections | Operations runs over budget, reactive cost cuts follow |
| Absenteeism not buffered | Planning used 0% absence assumption or underestimated shrinkage | Every 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:
| Day | Forecasting activity | Planning activity |
|---|---|---|
| Monday | Compare last week's forecast to actual — calculate accuracy, note bias | Review last week's service level, overtime, and adherence |
| Tuesday | Adjust this week's remaining intervals if volume is tracking differently than forecast | Adjust this week's schedule if needed (move training, shift breaks) |
| Wednesday | Build next week's interval-level forecast | — |
| Thursday | — | Build next week's schedule from the forecast |
| Friday | Finalize forecast | Publish next week's schedule (2 weeks ahead target) |
Monthly cycle:
| Activity | Forecasting | Planning |
|---|---|---|
| Volume review | Compare monthly forecast to actual. Update trend assumptions | — |
| Headcount review | — | Compare actual headcount to plan. Calculate hires needed for next month |
| Shrinkage recalculation | — | Recalculate actual shrinkage from time tracking data. Adjust scheduling assumptions if actual differs from plan |
| Attrition review | — | Update attrition rate and replacement hiring timeline |
| Budget check | — | Compare actual labor cost to budget. Flag if trending over |
Quarterly cycle:
| Activity | Forecasting | Planning |
|---|---|---|
| Trend analysis | Review 12-month volume trend, seasonal patterns, year-over-year growth | — |
| Headcount plan | — | Project required headcount for next quarter based on volume forecast + attrition |
| Budget planning | — | Convert headcount plan to labor cost projection |
| Benchmark review | Compare forecast accuracy to target | Compare 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 complexity | Impact on forecasting | Impact on planning |
|---|---|---|
| Different volume patterns per client | Each account needs its own forecast — Client A peaks mornings, Client B peaks afternoons | Schedules must be built per account, with cross-trained agents for flexibility |
| Different SLA targets | Client A requires 80/20, Client B requires 90/10 — the 90/10 client needs proportionally more agents per call | Staffing calculation uses different service level targets per account |
| Client volume changes | A client may ramp up or wind down volume with limited notice | Planning must include contract review and early warning of volume changes |
| Billable utilization | Non-billable time (bench, training) affects revenue | Planning 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).
