Shrinkage: The Number That Quietly Breaks Your Staffing Plan

You can forecast contact volume to the interval, buy exactly the headcount the model says you need, and still blow your service level every single day. When that happens, the culprit is usually not the forecast. It's shrinkage — the quiet gap between the hours you paid for and the hours actually spent handling contacts. It's the most under-managed number in workforce planning, and it breaks more staffing plans than bad forecasts do.

Shrinkage is unglamorous, and that's exactly why it leaks. Nobody gets excited about accounting for training time and bathroom breaks. But get it wrong and every downstream number is wrong with it. Here's how to measure and manage it properly.

What shrinkage actually includes

Shrinkage is all the paid time an agent is not available to take a contact. It's bigger than most plans assume because it hides in a dozen small categories:

• Planned, scheduled: training, coaching, team meetings, one-on-ones, planned projects.
• Planned, recurring: breaks, lunches, and the paid time that's simply part of the day.
• Unplanned: sick days, no-shows, tardiness, early departures.
• On-the-clock but off-the-queue: system outages, waiting for a password reset, admin tasks, "quick questions" to a supervisor.

That last category is the sneaky one. It rarely gets logged, so it rarely gets planned — and it can be the difference between hitting and missing service level on a busy afternoon.

Measure it honestly

The single most common shrinkage mistake is measuring only the parts that are easy to see. If your shrinkage number is just PTO and training, it's fiction.

• Capture every category, including the on-the-clock-off-the-queue time. If agents are regularly pulled off the phones for something, it belongs in the number.
• Split planned from unplanned. They're managed completely differently: planned shrinkage you schedule around; unplanned shrinkage you buffer for. A plan that lumps them together can't do either well.
• Track it by interval and day, not as a monthly average. Shrinkage isn't flat — Monday mornings and training weeks look nothing like a quiet Wednesday. An average hides the intervals where you actually get hurt.

The shrinkage-aware staffing calc

The math is simple; the discipline is applying it honestly. The numbers below are illustrative, not benchmarks — plug in your own.

Say an interval needs twenty agents actually handling contacts to hit service level (that's your requirement from the volume forecast). If you schedule twenty people, you will miss — because at any moment some are on break, in a huddle, or off sick. You have to staff up to absorb shrinkage.

The relationship is: staff required = base requirement ÷ (1 − shrinkage rate). If shrinkage runs at, say, thirty percent, then twenty required agents means twenty divided by 0.70 — roughly twenty-nine scheduled. Plan for twenty and you're short by nearly a third of the interval, every day, no matter how good the forecast was.

That gap is why so many "we forecasted it right and still missed" days happen. The forecast was fine. The shrinkage assumption was a guess.

Manage the levers

You can't eliminate shrinkage, but you can shape it. Work the levers in order:

1. Move controllable shrinkage off the peaks. Training, meetings, and coaching are shrinkage you schedule. Put them in the valleys of your volume curve, never the peaks. This one move recovers more service level than most staffing increases.
2. Attack unplanned shrinkage at the root. Chronic absenteeism and tardiness usually trace back to scheduling, morale, or a small number of patterns. Treat them as problems to solve, not weather to endure.
3. Log the invisible shrinkage. Make the on-the-clock-off-the-queue time visible — outages, admin, supervisor questions. You can't manage what you don't measure, and this category is almost always bigger than anyone guesses.
4. Right-size breaks with a schedule. Break and lunch timing is planned shrinkage you can smooth across the interval so it doesn't all land at once.
5. Re-baseline the rate every quarter. Shrinkage drifts with seasonality, headcount changes, and training pushes. A rate you set last year is quietly wrong now.

The overtime trap

When shrinkage breaks the plan, the reflex is overtime — and overtime raises next month's shrinkage, because tired agents take more sick days. Papering over a shrinkage problem with overtime doesn't fix the leak; it widens it and hands you the bill later.

Overtime is a legitimate short-term tool for a genuine spike. It's a terrible tool for a chronic shrinkage gap. Used to plug a structural shortfall, it burns out the exact people you're relying on, which drives up unplanned absence — more shrinkage — which you then cover with more overtime. If you find yourself running standing overtime to make service level, the real problem is upstream in the shrinkage number, and that's where the fix is.

What to do next

• Add up your true shrinkage this month — every category, including the invisible on-the-clock time — and compare it to the rate in your plan. The gap is often several points.
• Recompute one interval's staffing with the honest rate and see whether you've been structurally short.
• Move one recurring meeting or training block off your peak interval and into a valley.
• Split your shrinkage reporting into planned vs. unplanned so you can schedule around one and buffer for the other.

Volume forecasting gets all the attention, but shrinkage is where the plan actually leaks. Measure it honestly, staff up to absorb it, schedule the controllable part into the valleys — and the days when you "did everything right and still missed" mostly disappear.