WFM guideReporting

WFM performance reporting

Q: What should a monthly WFM performance report include?

A monthly WFM performance report should cover five areas: (1) Forecast accuracy — WAPE at volume and interval level, with explanation of the largest deviations. (2) Schedule coverage — coverage efficiency ratio (% intervals where scheduled agents met the Erlang C requirement), scheduled vs. required variance, shrinkage realisation rate. (3) Intraday effectiveness — % intervals where SL was within 5pp of target, intraday intervention log (what the RTC team did and what effect it had), break timing compliance rate. (4) Headcount position — scheduled vs. required headcount, confirmed leavers, new starter pipeline, net headcount trajectory vs. plan. (5) WFM function inputs to SL outcome — the WFM post-mortem: of the SL failures in the month, how many were attributable to forecast error vs. schedule design vs. adherence vs. intraday management failure vs. factors outside WFM control (unplanned volume spike, IT outage, etc.). This attribution is the most important section because it directs the correct intervention.

A WFM performance report is a self-assessment of the planning function — did the forecast match reality, did the schedule meet the staffing requirement, was intraday management effective? It is not a general contact centre performance report. The distinction matters for both audience and intervention.

WFM function performance vs. contact centre operational performance

Dimension	WFM function performance	Contact centre operational performance
What it measures	Quality of forecasting, scheduling, and intraday management	What agents and teams achieved (SL, AHT, CSAT, adherence)
Primary owner	WFM Manager	Operations Manager / Director
Key questions	Was the forecast accurate? Was the schedule right? Did intraday manage the queue?	Was SL met? Was AHT on target? Was adherence within tolerance?
SL failure interpretation	Was SL failure caused by WFM error (forecast, schedule, intraday)?	Was SL failure caused by agent behaviour (adherence, AHT), external events?
Correct intervention	Forecasting review, schedule rebuild, RTC coaching	Adherence programme, AHT coaching, recruitment
Reporting audience	WFM Manager, Operations Director (for planning inputs)	Operations Director, Finance, Senior Leadership

Five sections of the monthly WFM performance report

Forecast accuracy

Purpose

Measures how accurately the WFM function predicted the volume that arrived. This is the foundational WFM output — every downstream output (schedule, staffing, intraday plan) depends on the quality of the forecast.

Key metrics

WAPE (Weighted Average Percentage Error) at daily and interval level. Direction of error (over-forecast vs. under-forecast). Accuracy by day of week and by contact type (if disaggregated).

Primary audience

Senior WFM leadership and Operations Director. Finance if the cost model uses forecast volume as an input.

Common reporting error

Reporting only the monthly WAPE without reporting interval-level accuracy. A monthly WAPE of 5% can mask severe interval-level errors (off by 20% at peak, off by 20% at trough in the opposite direction) that cause SL failures even though the daily total is close to plan.

Schedule coverage and quality

Purpose

Measures whether the schedule produced by the WFM function was capable of meeting the SL target if followed perfectly. This is the WFM function's scheduling self-assessment — did we build the right schedule?

Key metrics

Coverage efficiency ratio (% intervals where scheduled agents ≥ Erlang C requirement). Scheduled vs. required interval variance (average agent difference per interval at peak). Shrinkage realisation rate (actual shrinkage vs. planned shrinkage assumption). AHT realisation rate (actual AHT vs. scheduled AHT assumption).

Primary audience

WFM Manager and Operations Director. Provides evidence for whether an SL failure was a schedule problem vs. an adherence or forecast problem.

Common reporting error

Reporting schedule coverage at daily or weekly level. Coverage must be assessed at half-hour interval level — a schedule can have 100 agents across a day but be severely short at 09:30 if the shift starts are wrong. Daily or weekly coverage figures smooth over interval-level gaps.

Intraday management effectiveness

Purpose

Measures how effectively the RTC team managed the queue within the constraints of the published schedule. Intraday management cannot fix a wrong schedule or a wrong forecast — but it can minimise the damage when both are correct and something unexpected happens.

Key metrics

% of intervals where actual SL was within 5 percentage points of the target. Average interval SL deviation. Break delay rate (% of breaks that were delayed by more than 30 minutes due to queue management). Intraday intervention log — actions taken and queue outcome (did queue recover?). Escalation rate (% of days requiring supervisor escalation).

Primary audience

WFM Manager and Operations Manager. Not typically reported to Finance or Director level unless there is a specific intraday problem to escalate.

Common reporting error

Not maintaining an intraday intervention log. Without a log, the monthly report cannot show what the RTC team did or what effect it had. The WFM function appears passive — just monitoring rather than managing. The intervention log is also the evidence base for identifying which types of events require which responses.

Headcount and establishment position

Purpose

Reports the current headcount position against the required establishment, including the leavers pipeline and new starter pipeline. This is the bridge between WFM planning (what headcount is needed) and HR/recruitment (what headcount is being delivered).

Key metrics

Scheduled headcount vs. required headcount (net and by skill). Confirmed leavers in the next 90 days. New starter pipeline (expected join dates and training completion dates). Net headcount trajectory vs. the approved establishment plan. Headcount risk — any skills where the pipeline does not cover the confirmed leavers.

Primary audience

Operations Director and Finance. Finance uses this to track the headcount cost against budget. HR Recruitment uses this to prioritise hiring activity.

Common reporting error

Reporting headcount in FTE without separating by skill or queue. An operation that has 300 agents but needs 30 French-speaking agents and only has 18 is not 300 FTE — it has a 12-agent shortfall in a specific skill that will not be visible in the aggregate FTE count. Always report headcount by skill where specialist skills exist.

SL outcome attribution

Purpose

The most important section of the WFM performance report. For the intervals that missed the SL target, what was the primary cause? This attribution directs the correct intervention — a scheduling error requires a different response from an adherence problem, which requires a different response from an unforeseeable volume event.

Key metrics

% of SL failure intervals attributable to: forecast error; schedule design; adherence/shrinkage overrun; intraday management failure; external factors outside WFM control (unplanned volume spike, IT issue, weather event). Total SL impact (PP difference from target) by cause.

Primary audience

All stakeholders. This is the report section that justifies the WFM function's value — it shows that WFM can diagnose the root cause of SL failure accurately, which is the prerequisite for fixing it.

Common reporting error

Omitting this section entirely and reporting only the SL outcome. A WFM function that reports SL missed target without attributing the cause is unable to recommend an intervention. It also allows stakeholders to assume that every SL miss is a WFM failure — even when some failures are caused by adherence, unplanned volume, or IT issues that are outside the WFM function's control.

WFM reporting questions

What should a monthly WFM performance report include?

Five areas: (1) Forecast accuracy — WAPE at volume and interval level, largest deviation explanations. (2) Schedule coverage — coverage efficiency ratio, scheduled vs. required variance, shrinkage and AHT realisation rates. (3) Intraday effectiveness — interval SL deviation, break delay rate, intervention log. (4) Headcount position — actual vs. required by skill, leavers pipeline, new starter pipeline. (5) SL outcome attribution — the most important section: of the intervals that missed SL, what proportion was attributable to forecast error, schedule design, adherence overrun, intraday management failure, or external events outside WFM control. The attribution section is what distinguishes a diagnostic WFM report from a raw data dump — it directs the correct intervention.