Shrinkage and Staffing Calculator
Estimate required contact center headcount from volume, occupancy, concurrency, shrinkage, and schedule coverage for BPO workforce planning.
Staffing inputs
Enter workload, productivity, occupancy, shrinkage, and planning buffer to get a first-pass FTE estimate.
Staffing output
The result shows the base FTE requirement and a more realistic staffed number after shrinkage and buffer.
You need about 20 staffed FTE based on workload, productivity, occupancy, shrinkage, and the planning buffer you entered.
Staffing math
| metric | value |
|---|---|
| Workload units | 10000 |
| Productive rate per FTE | 900 |
| Occupancy | 85% |
| Shrinkage | 28% |
| Base required FTE | 18.16 |
| Recommended staffed FTE | 20 |
Planning notes
- Use this as a first-pass staffing estimate, then pressure-test it against arrival patterns and service-level targets.
- If shrinkage assumptions are uncertain, model a conservative case before final staffing approval.
- Separate training and nesting capacity from steady-state capacity in the final WFM plan.
What this tool helps you do
Shrinkage is the quiet killer of staffing plans. A plan that ignores it underestimates headcount by 20-35 percent in most contact centers. This calculator keeps the shrinkage conversation explicit rather than hidden in a single number.
- Stop planning staffing with a single lumped shrinkage assumption.
- Keep chat concurrency visible instead of buried in another spreadsheet.
- Scenario-test service level, occupancy, and shrinkage tradeoffs fast.
- Produce a defensible staffing ask for finance and commercial teams.
How it will work
- Enter volume and AHT: Add forecasted contact volume and average handle time.
- Set occupancy and service level: Choose the target occupancy and service level you are planning for.
- Apply shrinkage: Break out planned and unplanned shrinkage to get a realistic total.
- Review and export: See productive FTE and total headcount, then export the scenario for WFM and governance reviews.
Common use cases
New contract staffing
Build the initial staffing plan during transition planning.
Peak season forecasting
Scenario-test volume spikes and shrinkage changes together.
Commercial modeling
Support per-FTE pricing discussions with transparent staffing math.
Gap analysis
Compare actual staffing against the required plan to find capacity gaps.
Why this matters for BPO operators
Staffing errors show up as SLA misses, agent burnout, and overtime costs. Most of those errors are foreseeable if shrinkage is modeled properly.
A transparent calculator also makes client and finance conversations cleaner because the reasoning behind the headcount number is visible.
Output and export options
Export the scenario so WFM, finance, and client governance can all review the same math.
Who this is for
- Workforce managers and planners
- Ops managers and account leaders
- Finance business partners to ops
- Transition leads standing up new accounts
- Consultants delivering WFM engagements
Related Tools
Build a weighted support KPI scorecard covering FCR, AHT, SLA, CSAT, response time, and resolution time for BPO contact center and CX operations.
Build a browser planning sheet for forecast, required staffing, actual staffing, adherence, and variance analysis used in BPO workforce management.
Turn QA misses and KPI gaps into structured coaching plans with issue pattern, target behavior, actions, owner, and follow-up date.
Related Guides
Workforce Management, QA, Training, and Performance lesson on Workforce Management in BPO.
Workforce Management, QA, Training, and Performance lesson on Forecasting and Capacity Planning for Contact Centers.
Workforce Management, QA, Training, and Performance lesson on Scheduling and Shrinkage Explained.
Workforce Management, QA, Training, and Performance lesson on Occupancy vs Utilization vs Adherence.
Privacy-first workflow
Staffing inputs stay in your browser. Elysiate does not need your volume, AHT, or shrinkage numbers on a server to calculate headcount.
Frequently Asked Questions
Does this use Erlang math?
The calculator uses standard queueing assumptions appropriate for contact center planning. Results are intended for planning discussions, not real-time WFM.
Does it support chat concurrency?
Yes. Concurrency inputs let you model chat workloads realistically alongside voice.
Can I compare scenarios?
Yes. You can create and export multiple scenarios for side-by-side review.