WFM guideHeadcount management

Contact centre monthly headcount review

Q: What inputs does a contact centre monthly headcount review require?

A contact centre monthly headcount review requires six inputs: (1) Approved headcount plan — the agreed monthly headcount target from the annual planning cycle, showing planned FTE by month and team; (2) Current actual headcount — a confirmed list of currently active employees by team and skill, sourced from HR or the WFM system; (3) Confirmed leavers register — a list of employees who have resigned or had notice confirmed, with their last working date; (4) Confirmed joiners register — a list of approved new starters and their projected start dates from HR or recruitment; (5) Unplanned absence/long-term sickness position — a list of employees currently on long-term absence (typically 4+ weeks), which represents effective capacity loss not reflected in active headcount; (6) Rolling attrition rate — the current 12-month rolling attrition rate, used to project the expected number of leavers in the next 3–6 months if no additional recruitment action is taken.

The monthly headcount review is where the WFM function closes the loop between the annual headcount plan and operational reality. The most common failure is projecting forward using only confirmed leavers and ignoring probabilistic attrition — making months 4–6 appear better than they will actually be.

Why the monthly review is not optional

Annual plans decay within weeks

An annual headcount plan reflects assumptions made in October for the following year. By February those assumptions have already drifted — attrition has run at a different rate, a planned hire cohort was delayed, a new product increased handle time. Without a regular reconciliation, the plan is a point-in-time snapshot that becomes less useful every month.

Recruitment pipelines have fixed lead times

Contact centre recruitment typically takes 4–12 weeks from job posting to start date, plus 6–12 weeks of ramp time before an agent is fully productive. A headcount gap identified in the month it materialises is already 3–6 months too late to close with standard recruitment. The monthly review exists to identify gaps far enough in advance that standard recruitment can still close them.

Attrition is probabilistic, not certain

Most organisations only track confirmed resignations. But historical attrition rates allow the WFM function to predict, with reasonable accuracy, how many additional agents are likely to leave in the next 3–6 months who have not yet handed in notice. Ignoring this produces projections that are systematically over-optimistic.

Finance needs a current cost position

The headcount plan is the primary driver of the contact centre staffing cost line. Finance cannot manage the cost variance without an up-to-date headcount forecast. A WFM function that does not maintain a current rolling headcount forecast forces Finance to use the stale annual plan as a proxy — which is almost always wrong.

The five-step monthly headcount review

Reconcile actual vs. planned headcount

What it involves

Pull actual active headcount from HR/WFM system. Compare against the approved plan for the current month. Calculate variance in FTE and as a percentage of plan. Separate variance by team or skill group where the plan has team-level targets.

Output

Headcount variance table: plan FTE vs actual FTE vs gap (absolute and %) by team.

Common mistake

Comparing against the original annual plan without adjusting for approved headcount changes made during the year. If the plan was officially revised in month 5 but the review still compares against the January version, every subsequent review shows a false variance.

Project forward 3–6 months

What it involves

Apply the confirmed leavers schedule and confirmed joiners schedule to the current actual headcount to produce a projected headcount by month for the next 3–6 months. Add a probabilistic attrition projection using the rolling 12-month attrition rate for the months beyond the confirmed leaver horizon.

Output

Rolling headcount projection: actual + confirmed changes + probabilistic attrition by month for months 1–6.

Common mistake

Projecting forward using only confirmed leavers, ignoring probabilistic attrition. This makes the 4–6 month projection appear better than it will actually be, delaying recruitment triggers until the gap has already materialised.

Compare projection against plan and SL model

What it involves

Overlay the projected headcount against the approved headcount plan. Identify months where the projected headcount will fall below the plan by more than the agreed tolerance (typically 3–5 FTE or 3–5%). Cross-reference against the SL model to determine whether the projected headcount shortfall will breach the SL target — a 3 FTE gap at low volume may be within tolerance; the same gap in peak may not be.

Output

Gap analysis showing months where action is required (projected headcount below plan by more than tolerance).

Common mistake

Applying a uniform tolerance threshold regardless of volume. A 5 FTE gap in a 100-agent operation in a low-demand month may be fully manageable with flex resource; the same gap during Christmas peak may require emergency agency cover. Tolerance should be volume-adjusted.

Determine recruitment action required

What it involves

For each month where a gap exceeds the agreed tolerance, calculate the number of new starters required to close the gap, accounting for ramp time. Work backwards from the required trained-and-productive date to determine the latest acceptable offer date. Compare against the current recruitment pipeline — if the pipeline already has sufficient candidates in process, flag as on track; if not, escalate to HR as a recruitment gap.

Output

Recruitment action table: FTE required by month; latest offer date by cohort; pipeline status (sufficient / gap / critical).

Common mistake

Calculating how many new starters are needed without accounting for ramp time. If a gap of 5 FTE exists in month 4 and ramp time is 8 weeks, the offer needs to go out in month 2 — not month 3. The failure to account for ramp creates a structural lag where recruitment responses always arrive one cohort too late.

Update the rolling headcount forecast

What it involves

Replace the previous month's projection with the updated version incorporating this month's confirmed actuals, new confirmed leavers, new confirmed joiners, and refreshed attrition projections. Archive the previous version. Distribute to HR (to inform recruitment pipeline), Finance (to update cost forecast), and Operations (to set expectations for staffing levels).

Output

Published rolling headcount forecast: updated and circulated to HR, Finance, Operations.

Common mistake

Updating the forecast without archiving the previous version. Without a version history, it is impossible to identify when a forecast deteriorated, whether deterioration was anticipated or sudden, and whether the downstream teams who received the previous forecast took action based on figures that have now materially changed.

What inputs the review requires

Six inputs required before the review can run:

Approved headcount plan — the agreed monthly FTE target (including any in-year revisions); sourced from Finance or WFM planning model
Current actual headcount — confirmed active employees by team and skill; sourced from HR or WFM system (must be current, not last month's extract)
Confirmed leavers register — employees with accepted notice, showing last working date; sourced from HR
Confirmed joiners register — approved new starters with projected start dates; sourced from recruitment/HR
Long-term absence position — employees on absence of 4+ weeks who represent effective capacity loss; sourced from HR or payroll
Rolling 12-month attrition rate — calculated from HR data; used to project probabilistic future leavers beyond the confirmed horizon

If any of these inputs is missing or more than 2 weeks old, the review will produce unreliable outputs. Do not run the review with stale data and present the results as current.

Headcount review questions

What inputs does a contact centre monthly headcount review require?

Six inputs: (1) Approved headcount plan — monthly FTE target including any in-year revisions; (2) Current actual headcount — confirmed active employees by team and skill, current not stale; (3) Confirmed leavers register — employees with accepted notice and last working date; (4) Confirmed joiners register — approved new starters with projected start dates; (5) Long-term absence position — employees on 4+ week absence representing effective capacity loss; (6) Rolling 12-month attrition rate — for projecting probabilistic future leavers beyond the confirmed horizon. If any input is missing or more than 2 weeks old, the review outputs will be unreliable.