WFM guidePlanning

Contact centre workforce planning cycle

Q: What is the workforce planning cycle in a contact centre?

The workforce planning cycle in a contact centre is the set of recurring planning processes at different time horizons that together determine how many agents are available at each interval and how many will be recruited, trained, and deployed over the coming year. It operates at six levels: interval (15-30 minute intraday management); daily (next-day schedule adjustments and exceptions); weekly (schedule publication and shift allocation for the coming week); monthly (4-8 week capacity gap analysis and management); quarterly (rolling 12-month headcount review and recruitment planning); and annual (headcount budget and long-range resource modelling). Each level produces decisions that constrain or inform the others. A gap identified in the quarterly review triggers a recruitment decision that will not produce trained agents for 8-12 weeks — a lag that must be anticipated in the monthly and weekly plans.

Q: What should a contact centre quarterly capacity review include?

A contact centre quarterly capacity review should include: (1) Actual vs. forecast volume for the quarter just ended — was the forecast accurate? What drove divergence? (2) Rolling 12-month volume forecast update — revise the annual forecast based on latest actuals and business intelligence; (3) Headcount position — current headcount vs. required headcount by month for the next 12 months; (4) Attrition projection — forecast exits by month based on historical attrition patterns and known leavers; (5) Recruitment and training pipeline — agents currently in recruitment, offer, or training by start month; (6) Capacity gap by month — the gap between projected available agents and required agents, after attrition and before new starters are trained; (7) Actions required — recruitment approvals, training schedule adjustments, or planned use of overtime/BPO to bridge gaps.

WFM operates at six time horizons simultaneously — from 15-minute intraday intervals to the 12-month headcount budget. Each level makes decisions that constrain the others. The operations that plan well at all six levels consistently outperform those that only manage the week ahead.

The six planning horizons

Interval level

15–30 minutes cycle · Current shift window

Intraday controller / RTA analyst

Key decisions at this level

→Break and off-phone activity timing adjustments based on current SL position
→Emergency redeployment of cross-skilled agents to address real-time queue pressure
→Callback queue management — activate or increase callback offer if queue builds
→Management notification when SL is outside recovery thresholds

Inputs

·ACD real-time queue data
·Current agent state (available/in-contact/ACW/offline)
·Scheduled activities for the shift

Outputs

✓Break and activity re-timing directives
✓Intraday management log for post-day review

Common failure mode

Intraday controller reacting to ACD data that is 5–10 minutes stale, or managing to cumulative SL (daily average) rather than rolling SL (current interval). Both produce responses that are too slow.

Daily level

1 day cycle · Tomorrow's schedule window

WFM analyst / scheduling team

Key decisions at this level

→Approve or deny last-minute absence, annual leave, and schedule change requests
→Adjust tomorrow's schedule based on updated volume forecast (if materially different from the weekly plan)
→Identify and notify agents whose schedule change is required due to changed demand profile
→Confirm training, meetings, and off-phone activities still viable at updated volume levels

Inputs

·Updated volume forecast for tomorrow
·Absence and leave requests received
·Agency/flex pool availability for tomorrow
·Events notified since the weekly plan was published

Outputs

✓Confirmed schedule for tomorrow
✓Approved/denied leave responses

Common failure mode

Daily scheduling runs on yesterday's forecast rather than today's updated view. Demand intelligence gathered during the day (event notifications, marketing emails, billing run) is not fed back into the daily schedule update.

Weekly level

1 week cycle · Next 1–2 weeks window

WFM scheduler / WFM analyst

Key decisions at this level

→Publish and communicate agent schedules for the coming week
→Optimise shift allocation to match forecast demand profile
→Approve or queue annual leave requests against the 4-week leave plan
→Set training and off-phone activity schedule that fits within capacity without breaching SL
→Identify any staffing gaps that require agency or overtime coverage

Inputs

·2-week volume forecast by interval
·Agent availability and contracted hours
·Leave plan and pending leave requests
·Training schedule from L&D
·Agency availability

Outputs

✓Published schedule for week ahead
✓Agency/overtime booking for gaps
✓Leave plan update

Common failure mode

Schedule published without a constraint check against the SL model — shifts are allocated to days and intervals that do not match the demand shape, and the intraday team inherits a structurally mis-staffed schedule.

Monthly level

1 month cycle · 4–8 weeks ahead window

WFM manager / planning manager

Key decisions at this level

→Identify capacity gaps for the next 4–8 weeks against the current staffing position
→Activate BPO overflow, agency, or overtime to bridge short-term gaps
→Adjust training volumes if headcount is insufficient to sustain current training load
→Escalate gaps that cannot be bridged within the planning window (recruitment lead time > 4 weeks) to the quarterly plan
→Review leave accrual position and forecast leave burden for the month ahead

Inputs

·Rolling 8-week volume forecast
·Current headcount with absence and attrition adjustments
·Recruitment pipeline — confirmed starters within the next 8 weeks
·Leave plan and accrual position

Outputs

✓8-week capacity position summary
✓BPO/agency/overtime commitments
✓Escalation items to quarterly review

Common failure mode

Monthly review focuses on the immediate 4 weeks only. Gaps in weeks 5–8 are not identified until they become urgent — too late to recruit, and often too late to book agency resources at standard rates.

Quarterly level

3 months cycle · Rolling 12 months window

Head of WFM / Head of Operations / Finance

Key decisions at this level

→Update the rolling 12-month volume forecast based on latest actuals and business intelligence
→Review headcount position vs. required staffing for each month of the next 12 months
→Approve recruitment numbers and intake dates to fill projected gaps
→Review and update attrition assumptions based on latest 3-month actuals
→Agree annual leave plan parameters (leave coverage, maximum leave by period)
→Review shrinkage assumptions — has the shrinkage component changed since the last review?

Inputs

·Quarterly business performance data (volume, AHT, shrinkage actuals)
·Business forecast from commercial/sales teams
·Attrition data for the quarter
·Recruitment pipeline status
·Known headcount exits for the next 12 months

Outputs

✓Updated 12-month capacity model
✓Recruitment approval and intake schedule
✓Attrition assumption update
✓Escalation items to annual plan

Common failure mode

Quarterly review uses the same volume forecast that was built at the start of the year — not updated for actuals. By Q3, the 12-month forecast is often materially wrong, producing either an over-hired position (cost) or an under-hired position (SL failure).

Annual level

12 months cycle · 12–24 months window

Senior leadership / Finance / Head of Operations

Key decisions at this level

→Set headcount budget for the year: FTE target by month, incorporating attrition assumptions and productivity targets
→Approve capital investment in WFM technology, training, and infrastructure
→Set SL and quality targets for the year — the basis for all downstream staffing calculations
→Agree the volume forecast that underpins the headcount budget — key risk if volumes diverge from plan
→Agree the shrinkage budget — what level of non-productive time is funded?
→Set the BPO/agency mix — what proportion of flexible capacity is provided via partners?

Inputs

·5-year commercial forecast (from strategy / commercial team)
·AHT improvement programme targets
·Technology investment roadmap (automation, AI, channel shift)
·Prior year headcount actuals vs. plan
·Industry benchmarks for shrinkage, attrition, AHT

Outputs

✓Headcount budget by month and quarter
✓Recruitment plan for the year
✓Training plan and L&D budget
✓BPO contract parameters

Common failure mode

Annual plan uses a point-in-time volume forecast without scenario modelling. When volumes diverge from plan (they always do), there is no pre-agreed trigger or response mechanism — management debates whether to hire reactively (expensive) or wait (risky to SL).

Quarterly capacity review: what to cover

The quarterly review is the most critical planning meeting in the WFM calendar. It is the level at which recruitment decisions are made — and recruitment has an 8–12 week lag to first productive agent. Missing the quarterly review cycle by even one month can produce a multi-week staffing gap that cannot be corrected in time.

1.
Volume actuals vs. forecast for the quarter just ended
What drove divergence? Systematic over/under-forecast? One-off event? This informs whether the annual forecast model needs recalibration.
2.
Rolling 12-month volume forecast update
Update the annual forecast based on latest actuals. If volumes are running 8% above plan, the headcount model built on the original forecast is 8% understaffed.
3.
AHT actuals vs. assumptions
If AHT has changed materially (new products, new processes, increased complexity), the staffing calculation based on old AHT is wrong. Recalculate required headcount with updated AHT.
4.
Shrinkage actuals vs. budget
Has shrinkage increased (more absence, more training, more meetings)? If so, the scheduled headcount produces less available time than planned — a hidden capacity gap.
5.
Headcount position by month for the next 12 months
Required agents (from updated forecast and AHT/shrinkage) vs. projected available agents (current headcount minus projected attrition plus confirmed starters). The gap is the recruitment target.
6.
Attrition update
What was the actual attrition rate for the quarter? Update the 12-month attrition projection. Under-estimating attrition is the most common cause of unexpected capacity gaps.
7.
Recruitment pipeline
What is in the pipeline by start date? Are there enough candidates at each stage to deliver the required intake dates? Is the pipeline at risk?
8.
Actions and owners
Each gap in the capacity model must have a named action (recruit X by date / book agency for months Y-Z / approve overtime budget for peak period) and a named owner with a deadline.

Decision lag: how far ahead each level must plan

Every workforce planning decision has a lag — a minimum lead time before it produces productive capacity. Planning decisions that are triggered too late cannot be recovered in time to prevent a service impact.

Decision	Minimum lead time	Planning level that owns it	Risk if triggered too late
Agent shift change (individual)	2–5 days	Daily / weekly	Agent non-compliance if insufficient notice; unfilled slot
Agency / flex pool booking	3–7 days (standard), same-day (premium rate)	Weekly / monthly	Premium agency rates; unavailability in tight labour markets
Overtime authorisation	3–5 days to identify willing agents	Weekly / monthly	Insufficient volunteers; agent burnout if used repeatedly
BPO volume increase (within contract)	5–10 days (typical contract activation clause)	Monthly / quarterly	BPO cannot staff without notice; SL failure during gap
New employee recruitment (start date)	8–14 weeks (advert + shortlist + offer + notice + training)	Quarterly	Capacity gap cannot be closed for 2–3 months; forced reliance on agency at higher cost
New employee training completion	2–8 weeks post start date (depending on product complexity)	Quarterly / annual	Starters on site but not yet productive — headcount present but capacity not available
Headcount budget approval	3–4 months before financial year start (typical)	Annual	If headcount is underfunded, recruitment cannot proceed even if the capacity gap is visible

Planning cycle questions

What is the workforce planning cycle in a contact centre?

The workforce planning cycle is the set of recurring planning processes at six time horizons: interval (15-30 minute intraday management of breaks and redeployment); daily (next-day schedule adjustments); weekly (schedule publication and shift allocation); monthly (4-8 week capacity gap identification); quarterly (rolling 12-month headcount review and recruitment planning); and annual (headcount budget and long-range resource modelling). Each level produces decisions that constrain or inform the others. A gap identified at quarterly review triggers a recruitment decision with an 8-12 week lag — a lag that must be anticipated in all shorter-cycle plans.

What should a contact centre quarterly capacity review include?

Eight items: (1) Volume actuals vs. forecast for the quarter just ended — what drove divergence?; (2) Rolling 12-month volume forecast update based on latest actuals; (3) AHT actuals vs. assumptions — recalculate required headcount if AHT has changed; (4) Shrinkage actuals vs. budget; (5) Headcount position by month for the next 12 months — required vs. projected available; (6) Attrition update — revise the 12-month attrition projection; (7) Recruitment pipeline status by start date; (8) Named actions with named owners and deadlines for each identified gap.