Skip to main content
TurnellaBeta
WFM guideAnalytics

WFM reporting guide

A WFM team that cannot report its own performance clearly cannot demonstrate the value of workforce planning. Most WFM teams produce too many reports with too little insight. Data without analysis is not a report; it is a spreadsheet. The best WFM reports lead with a metric, show the trend, explain the driver, and quantify the impact.

Six core WFM reports

Interval service level report

Intraday (every 30 minutes) + daily summary · Audience: Intraday controller, TLs, Operations Manager

The primary operational tool for intraday management. Shows actual SL vs. target for each interval, enabling break and activity re-timing decisions in real time.

Key metrics to include

  • ·Service level % per 30-minute interval vs. target (e.g. 80/20)
  • ·Average speed of answer (ASA) by interval
  • ·Abandonment rate by interval
  • ·Contacts offered vs. contacts handled
  • ·Agents available vs. required at interval (occupancy implied)

Presentation format

Real-time dashboard (ACD report). Daily summary in table format: hour, SL%, ASA, abandonment%, offered, handled. Red/amber/green traffic lighting against targets.

Common error

Reporting daily cumulative SL only. A cumulative 80% can mask catastrophic interval SL below 40% in peak hours followed by over-staffed low-volume intervals. Always show interval-level data.

Schedule adherence and shrinkage report

Daily (prior day actuals) · Audience: WFM analyst, Operations Manager, TLs

Tracks whether agents are following their scheduled times (adherence) and what proportion of scheduled time is lost to unplanned events (absence, late arrivals) and planned non-contact activities (training, meetings, breaks).

Key metrics to include

  • ·Schedule adherence % by agent and by team vs. target (typically ≥90–95%)
  • ·Actual shrinkage % vs. budgeted shrinkage, broken down by component (planned / unplanned)
  • ·Unplanned absence rate (days lost to sickness / unauthorised absence)
  • ·Late arrivals and early departures: number of occurrences and total minutes lost
  • ·Agents flagged below adherence threshold for follow-up

Presentation format

Daily table by team: team, agents scheduled, adherence%, shrinkage%, unplanned absence%, flagged agents. Week-to-date rolling average alongside daily figure.

Common error

Reporting adherence without distinguishing planned vs. unplanned non-adherence. An agent on approved training is non-adherent to their contact schedule, but this is a WFM scheduling issue (training not reflected in schedule), not a performance issue.

Forecast accuracy report (WAPE)

Weekly (prior week actuals vs. forecast) · Audience: WFM analyst, WFM Manager, Operations Manager

Tracks the accuracy of the WFM team's volume forecasts at each horizon: monthly, weekly, daily, and interval. A WFM team that cannot measure its own forecast accuracy cannot systematically improve it.

Key metrics to include

  • ·WAPE (weighted absolute percentage error) for the prior week at: monthly horizon, weekly horizon, daily horizon, 30-minute interval horizon
  • ·Over-forecast vs. under-forecast split: is the error systematic (consistently over or under) or variable?
  • ·Top 3 days where forecast error exceeded ±15%, with an identified cause for each
  • ·Forecast accuracy trend: rolling 4-week WAPE vs. prior 4-week WAPE, showing whether accuracy is improving

Presentation format

WAPE scorecard: horizon, prior week WAPE%, prior 4-week average, target. Traffic light. Root cause commentary for the worst days.

Common error

Reporting MAPE (mean absolute percentage error) instead of WAPE. MAPE gives equal weight to each interval regardless of volume, so a low-volume interval with a large error has the same weight as a peak interval. WAPE weights errors by volume, making it a better measure of operational impact.

Weekly WFM performance summary

Weekly (for management review) · Audience: Operations Manager, Head of Operations, WFM Manager

The primary management-facing WFM report. Covers the prior week's operational performance with trend, root cause, and forward-looking commentary. Should be produced and distributed by end of day Monday for the prior week.

Key metrics to include

  • ·Service level: actual % vs. target, trend vs. prior week and prior 4-week average
  • ·Schedule adherence: team average vs. target, teams below threshold
  • ·Shrinkage: actual vs. budget, breakdown by component
  • ·Forecast accuracy: WAPE vs. target at daily and interval level
  • ·Headcount: scheduled vs. required, variance and cause (absence, leave, training)

Presentation format

One-page summary: metric scorecard (current week vs. prior week vs. target) + 3–5 sentences of commentary covering the week's key WFM events and forward view for the coming week. No tables longer than 10 rows.

Common error

Producing a report with too many metrics and no commentary. A table of 50 metrics with no explanation is data, not insight. The weekly report should lead with 'What happened, why, and what is being done about it.'

Monthly capacity report

Monthly (for capacity and headcount review) · Audience: Head of Operations, Finance, WFM Manager

The capacity planning report for the month just ended and the forward 8-week projection. Identifies any capacity gaps in the forward period that require action (overtime, agency, BPO) or management escalation (gaps requiring recruitment).

Key metrics to include

  • ·Headcount: actual vs. required vs. budgeted, end-of-month position
  • ·Attrition: exits in the month, annualised rate, vs. assumption
  • ·New starters: actual vs. planned, and whether intakes are on schedule
  • ·Shrinkage: actual vs. budget, and the forward-8-week shrinkage projection
  • ·8-week capacity gap: required staffing vs. projected available by week
  • ·Actions to bridge any gaps: overtime approved, agency booked, BPO volume activated

Presentation format

Capacity table: week, required agents, projected available agents, gap, bridging action. Commentary: key drivers of any gap (attrition above plan, delayed recruitment). Action log: named actions with owners and dates.

Common error

Reporting current-month headcount without a forward projection. The capacity report is only useful if it identifies gaps early enough to act on them. Gaps in weeks 5–8 that are not identified until week 3 produce emergency agency bookings at premium rates.

Quarterly planning review

Quarterly (for senior management and finance) · Audience: Head of Operations, Finance, Senior Management

The strategic WFM report. Covers quarterly actuals vs. plan, updates the rolling 12-month forecast, reviews the attrition and recruitment pipeline, and identifies any long-range capacity risks that require management decision.

Key metrics to include

  • ·Volume: quarterly actuals vs. annual forecast, WAPE at the quarterly level
  • ·AHT: actuals vs. assumption, and whether AHT has changed materially from the planning assumption
  • ·Shrinkage: actuals vs. budget, updated forward assumption
  • ·Attrition: quarterly rate, trailing 12-month rate, vs. annual assumption
  • ·Headcount: end-of-quarter position vs. plan, recruitment pipeline by intake date
  • ·12-month capacity model: required headcount vs. projected available by month, identifying recruitment approval requirements

Presentation format

Formal report with executive summary, 12-month capacity chart, attrition and recruitment pipeline table, and action and decision log. Present the financial implication of any capacity gap (overtime cost, agency cost, SL impact and revenue risk).

Common error

Presenting the capacity model without quantifying the financial impact of gaps. A headcount gap that will require 12 weeks of agency cover at 30% premium must be presented in £ to secure the management decision to recruit. WFM data without financial context does not drive decisions.

WFM reporting principles

Lead with so what, not so here is the data

Every WFM report should open with the most important finding, not with raw data tables. 'Service level was 78% against an 80% target, driven by AHT running 4% above assumption and Tuesday absence running at 22% vs. 12% budget' is a useful report opening. A table of 200 rows with no commentary is not.

Show trends, not snapshots

A single-week SL of 79% tells you nothing about direction. A 4-week trend from 83% → 81% → 80% → 79% tells you SL is declining and intervention is needed. Always show at least 4 weeks of trend alongside the current period.

Quantify the impact in financial terms for management reports

A capacity gap of 5 agents for 8 weeks at 80% occupancy and £12/hr agency rate costs approximately £13,000. A SL miss that drives 500 additional abandoned contacts with a 15% callback rate costs 75 repeat contacts × £4.50 average unit cost = £338. Management decisions require financial context.

Stop reports that are not read or acted upon

Conduct a report audit annually: which reports are read? Which are filed unread? Which metrics in each report are referenced in management discussions? Stop or reduce the cadence of reports that produce no decisions. Every report has an opportunity cost: it takes time to produce and time to read.

Separate operational reports from management reports

Operational reports (interval SL, intraday adherence) need to be fast, real-time, and action-triggering. Management reports need narrative, trend analysis, and financial quantification. Mixing the two produces a report that is too slow for operations and too raw for management.

WFM reporting questions

What reports should a WFM team produce?

Six core report types at appropriate cadences: (1) Interval service level report: intraday and daily summary, for operational management; (2) Schedule adherence and shrinkage report: daily, for operations managers and TLs; (3) Forecast accuracy (WAPE) report: weekly, for WFM analysts and management; (4) Weekly WFM performance summary: weekly, one-page with commentary for management; (5) Monthly capacity report: monthly, with 8-week forward projection and gap analysis; (6) Quarterly planning review: quarterly, for senior management with 12-month capacity model and financial impact quantification. Reports not read or acted upon should be stopped.

Related guides