Planning the public sector contact centre — deadline spikes, policy change, no marketing lever

Operations · Sector guide · ~7 minute read

Public sector contact centres — local authority, DWP-style benefits lines, HMRC-style tax operations — plan against demand they cannot shape. Deadlines are set in statute, surges are created by policy announcements, and there is no marketing department to dial a campaign up or down. The citizen often cannot go elsewhere, the budget is fixed in advance, and the workforce is unionised. The planning disciplines exist; they are just different ones.

Deadline-driven demand — the spikes you can see coming

Public sector demand runs on statutory calendars. Self-assessment deadlines (the HMRC 31 January wall), benefit renewal and migration windows, council tax billing in March–April, school admissions dates, electoral registration deadlines, blue-badge and licence renewals — each produces a spike whose date is known a year out and whose size is forecastable from history plus the cohort being written to.

The disciplined planner builds the year around the statutory calendar the way a retailer builds around peak — with one difference: the deadline cannot move, and the citizen cannot defect to a competitor; they simply call again tomorrow. Unanswered deadline-week demand does not disappear, it recycles and compounds. Staff the run-up weeks deliberately to drain demand early, because the final 48 hours can never be staffed to demand.

Policy-change surges and the absence of a marketing lever

The second demand driver is policy change: a budget announcement, a benefit-rate change, a new scheme launch, a fiscal-event news cycle. The press release lands and the phones light up — often within the hour, frequently before the operation has been briefed. Commercial planners smooth demand with marketing timing; the public sector planner has no such lever, because the announcement is made by ministers or members, not by the operation.

The countermeasures are structural: a standing relationship with the policy and communications teams so the planner sees announcements before the public does; pre-built surge playbooks per announcement type; and same-day IVR, web and scripted-FAQ deployment so the predictable 80% of questions are absorbed cheaply. The operations that handle fiscal events well rehearse them; the ones that do not discover the announcement on the news with everyone else.

Channel shift vs the digitally excluded

Most public bodies carry channel-shift targets — move contact to web and app, cut cost per transaction. The targets are legitimate, but the residue is not random: the citizens who remain on the phone are disproportionately older, poorer, disabled, digitally excluded, in crisis, or dealing with cases too complex for the form. Average AHT on the residual voice channel rises as deflection succeeds, exactly as it does after AI deflection in commercial sectors.

The planning discipline: never staff the post-shift voice channel on pre-shift AHT, and treat the assisted-digital and vulnerable-citizen load as a separate forecast stream with specialist capacity. Public Sector Equality Duty and accessibility obligations make this a legal exposure as well as a service one — the channel-shift business case that ignores the excluded cohort understates the residual cost and the risk together. Not legal advice — validate with your equalities and compliance teams.

Statutory clocks, fixed budgets, and the union context

Public sector work carries statutory clocks that commercial sectors do not: FOI requests (20 working days), subject access requests, statutory complaints stages, ombudsman referrals (LGSCO, PHSO and equivalents). These are work-in-progress queues, not contact queues — the planner has to provide working capacity for the casework, separately carved out, or the clocks breach while the phones are answered.

The resourcing context is equally distinctive: budgets are set annually in advance of demand, headcount ceilings are political as well as financial, and the workforce is typically unionised — meaning shift changes, flexible contracts, and overtime all move through consultation and agreement, on lead times of months rather than weeks. The disciplined planner treats union engagement as a planning relationship to invest in year-round, and builds the flexibility into agreements before the surge, not during it.

Public sector CC planning — demand you cannot shape, constraints you must Demand drivers ▸ Statutory deadline spikes (tax, benefits, renewals) ▸ Policy / fiscal-event announcement surges ▸ Annual billing & renewal calendars ▸ Channel-shift residual (harder voice mix) ▸ FOI / SAR / complaints casework ▸ Recycled unanswered demand Planning disciplines ▸ Plan the year on the statutory calendar ▸ Early sight of announcements (policy / comms link) ▸ Pre-built surge playbooks per event type ▸ Assisted-digital stream forecast separately ▸ Casework capacity carved out (clocks protected) ▸ Union agreement on flex, secured in advance No marketing lever, no customer defection — unanswered demand recycles until it is served

The honest public sector planning posture

Build the plan on the statutory calendar, drain deadline demand early because the final 48 hours can never be staffed, get sight of policy announcements before the public does, and forecast the digitally-excluded residue as its own stream rather than an embarrassment to the channel-shift business case. Carve out casework capacity for the statutory clocks, and invest in the union relationship before you need the flexibility. The budget is fixed; the discipline is making the trade-offs explicit rather than letting the queue make them for you.

See also