What it means
A contact centre may need twenty agents handling contacts at a given time, but scheduling exactly twenty people leaves gaps when some are on breaks or in training. Shrinkage accounts for those expected unavailable periods.
NiCE describes it as planned and unplanned time that makes scheduled agents unavailable for contacts, with meetings and training as planned examples and sickness and system issues as unplanned ones. This is a capacity measure, not a judgement that every unavailable minute is waste.
A fictional team schedules forty paid hours and has twenty-eight contact-available hours, so the difference is twelve hours, or 30% shrinkage. The ratio should use the same group and time period, and the time categories must be defined: lunch might be unpaid in one workplace and paid in another, and mixing paid hours with all scheduled hours changes the denominator.
If a queue requires twenty people available and expected shrinkage is 30%, a simplified staffing calculation is twenty divided by 0.70, or about 28.6, so schedule twenty-nine before other practical constraints. Real interval planning is more detailed, because staffing formulas assume a stable shrinkage estimate and do not by themselves account for random arrival patterns, service level targets or skill restrictions.
Use workforce planning tools or qualified analysis for real schedules, and remember that cross-trained agents cannot handle two contacts at once, so track available skill capacity rather than treating every scheduled person as interchangeable. Agent shrinkage differs from occupancy, which measures the share of available handling time actually spent on contacts and related work, since a person can be available but not constantly busy.
It also differs from absence rate: absence is one source of unplanned shrinkage, while training, coaching and mandated breaks create planned shrinkage even when everyone attends work. A payroll report and a phone-system report may disagree because they classify after-call work differently, and that time is often part of productive contact handling rather than shrinkage.
Patterns by time of day matter. A daily average can conceal a lunchtime coverage gap, so forecast intervals and stagger planned activities where service demand is high; a fictional support team that schedules all coaching on Monday morning sees a backlog, and moving some sessions to quieter periods improves availability without cancelling coaching.
System outages can make agents unable to work despite being present, so record them separately from leave so management can fix the technical cause rather than blame staff, and expect shrinkage to rise during onboarding because trainees attend classes. A manager should compare planned shrinkage with actual shrinkage: if planned time was 25% but actual was 35%, investigate the difference by category, and do not let one unusual day set a permanent staffing target.
Do not reduce essential training just to improve the metric, since better training may prevent repeat calls and compliance mistakes, and voluntary overtime can fill a short-term gap but repeated use may increase fatigue and turnover. Publish the formula and categories with the metric, because changes to break rules or systems can create apparent trend shifts even when staffing is unchanged; a fair target allows people to rest, learn and take legitimate leave, so shrinkage is a planning allowance for real human work, not a goal of zero.
In practice
Real-world examples.
Example
A centre handling billing calls needs twenty agents available at peak. Knowing that breaks and training make about 30% of scheduled time unavailable, the planner schedules twenty-nine people rather than twenty. Service levels hold at peak without relying on overtime.
Example
A software helpdesk loses a full morning when its ticketing system goes down. Agents are logged in and at their desks, but cannot work on contacts, so the lost hours are recorded as unplanned shrinkage from the outage. Management uses the figure to press the IT team for a fix, instead of blaming staff for poor availability.
Example
A retail bank contact centre finds that all weekly coaching falls on Monday mornings, exactly when call volumes are highest. The manager moves half the sessions to Wednesday afternoons, when demand is lighter. Weekly shrinkage is unchanged, but the queue backlog on Mondays disappears.
Formula
Calculation
Shrinkage = unavailable scheduled hours / total scheduled hours x 100%. Simplified required scheduled staff = required available staff / (1 - shrinkage fraction), when the fraction is below one.
Worked example: a team of 10 agents is scheduled for 40 hours each, so total scheduled hours are 10 x 40 = 400. Planned unavailable time is 40 hours of breaks, 30 of training and 20 of meetings, or 90 hours; unplanned time is 20 hours of sickness and 10 of system outage, or 30 hours. Total unavailable time is 90 + 30 = 120 hours, so shrinkage is 120 / 400 x 100% = 30%, made up of 22.5% planned and 7.5% unplanned.
To staff a queue that needs 20 agents available, divide by one minus the shrinkage fraction: 20 / (1 - 0.30) = 20 / 0.70 = 28.57. Rounding up, schedule 29 agents, which gives 29 x 0.70 = 20.3 agents of expected availability.Case study
Seen in the real world.
In this fictional case, Delta Support schedules forty paid hours and records twenty-eight available hours. Its shrinkage is twelve divided by forty, or 30%. Management separates training from outages and plans coverage by interval. It does not label necessary breaks as poor performance.
The planning team had previously staffed to a flat 20% allowance, which left the queue short at lunchtime and during training weeks. After measuring planned and unplanned time by category, it set a 25% planned and 5% unplanned allowance, and reviewed the split each month. The change cost two extra hires, but cut abandoned contacts and removed most of the emergency overtime. The company and figures are invented for illustration only.
Watch out
Common mistakes.
- Treating shrinkage as the same as occupancy.
- Assuming all unavailable time is avoidable.
- Using a daily average to plan every hourly interval.
Questions
People also ask.
Do breaks count?
They often do if included in scheduled time but unavailable for contacts; define the denominator.
Is lower always better?
No. Cutting required training or rest can harm quality and people.
Why use it in staffing?
It converts required live coverage into a schedule that allows for unavailable time.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%