Operate · item 25
Capacity and surge plan
A shared service is judged on quarter close, not on an average Tuesday. Every committed level on this estate is priced against a throughput assumption and a number of humans who must be awake to approve things. This page states those assumptions, forecasts the queue into each peak, and says plainly where the plan is short of people before the peak arrives rather than after.
Health
Whether there are enough hands and agents
Plans covered, tight and short, against the queues forecast to breach their service level.
Human coverage at peak
115.0 full-time equivalents needed · 108.6 available
Record-to-Report quarter close
Quarter close · Final two business days of the quarter plus the following four · owner Ana Duarte
Source-to-Pay year-end payment run
Year end · Final ten business days of the fiscal year · owner Tobias Renn
Hire-to-Retire open enrollment
Open enrollment · Three weeks in the second month of the fourth quarter · owner Priya Raman
Order-to-Cash quarter-end order surge
Quarter-end order surge · Final five business days of the quarter · owner Morgan Idris
Customer Service major incident surge
Product incident · Unpredictable, typically 6 to 48 hours · owner Avery Chen
Finance external audit window
External audit · Six weeks following the year-end close · owner Grace Abbott
Human Resources hiring surge
Hiring surge · First eight weeks of the fiscal year · owner Priya Raman
Marketing campaign launch
Campaign launch · Two weeks around each major launch · owner Avery Chen
Actions
What is waiting on a person
Capacity is the one place where the answer is almost always a person, because the shortfall is people.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This desk can start a forecast run — project queue arrivals against declared capacity and publish a breach risk. It cannot hire, reassign a person, change a shift pattern, or move an agent ceiling. Every one of those is an operating decision owned by a function leader.
Live observability
What the record shows right now
Plan coverage. Tight means covered today with no margin.
Current distribution
8 plans
Is policy and strategy coming to fruition
Whether the written intent is holding here
1 of 8 capacity plans are genuinely covered. 5 queues are forecast to breach.
Not holding on the record
The strategy position behind automation on this estate is that agent capacity absorbs volume growth so headcount does not have to. Against that, 5 of 8 plans are short today and 2 have no headroom, and 3 surge playbooks have never been exercised. Forecasts on this page are modeled from historical arrival rates — they are labeled as forecasts because none of them has yet been compared against what actually arrived.
Drill results are measured against a modeled estate on a rehearsal calendar of our own making. Recovery times here are real measurements of a simulation, not evidence that a customer's production estate recovers in the same time.
Volumes, throughput and the review-minute assumptions are modeled. The method is the deliverable: state the peak, state the throughput and staffing the committed level was priced against, forecast the queue into the peak, and name the levers with their lead times. Worst forecast error on file is 22.4%, which is carried on the plan rather than hidden behind a point estimate.
3 of the 8 peak playbooks have never been run, and 6 of the 21 surge levers have never been pulled. An untested playbook is shown as untested here. It is not shown green because it exists.
This page covers surge capacity for peaks. It is not a workforce transition plan: what happens to the people whose work the agents now do is a separate question this estate does not yet answer.