Shrinkage

The difference between paid time and available time

Paid time is the total time an agent is scheduled or contracted to work. Available time is the portion of that time where the agent can actually handle customer demand.

The gap between the two is shrinkage.

For example, an agent may be paid for a full shift, but during that shift they will take breaks, attend a team meeting, complete coaching, and possibly spend time away from the queue for admin. None of those activities are unusual. Many are necessary. But they reduce the amount of time available for calls, chats, emails, or messages.

This is why workforce planners cannot simply calculate staffing based on contracted hours. They need to understand how much of that time will realistically be available.

Planned shrinkage

Planned shrinkage includes activities that are known in advance. These might include:

• Breaks
• Lunches
• Annual leave
• Training
• Team meetings
• One-to-one coaching
• Performance reviews
• Planned admin time
• Project work
• Briefings
• Scheduled system downtime

Planned shrinkage is not automatically bad. In fact, much of it is essential. Agents need rest breaks. Teams need training. Supervisors need coaching time. Organisations need briefings and updates.

The problem comes when planned shrinkage is not included properly in forecasts and schedules. If a training session removes ten agents from the queue during a busy period and that time has not been planned for, service levels will suffer.

Good workforce planning treats planned shrinkage as part of normal operations, not an inconvenience.

Unplanned shrinkage

Unplanned shrinkage includes anything that unexpectedly reduces agent availability. This may include sickness, lateness, emergency absence, system outages, over-running meetings, technical problems, or agents being pulled into urgent work.

Unplanned shrinkage is harder to manage because it changes the plan during the day. A schedule may have been accurate at 9am, but by 10am several agents may be off sick, one system may be unavailable, and a meeting may have overrun.

This is where real-time management becomes important. Supervisors and workforce teams need to understand the live impact and decide what can be adjusted. That might mean moving breaks, calling in support, delaying offline work, or accepting that service levels will be under pressure for a period.

Why shrinkage affects service levels

Shrinkage directly affects how many agents are available to meet demand. If shrinkage is underestimated, the contact centre will not have enough live capacity.

For example, if a centre needs 80 agents available to meet its service level but shrinkage is expected to be 25%, it will need to schedule more than 80 agents. If it schedules exactly 80, the actual number available will be lower once breaks, absence, meetings, and other activities are included.

This is why shrinkage must be built into staffing calculations. It influences recruitment, forecasting, scheduling, budgeting, and intraday management.

When shrinkage is planned accurately, service levels are more stable. When it is ignored, teams spend the day firefighting.

Shrinkage and agent wellbeing

Shrinkage is sometimes treated as something to reduce at all costs. That is the wrong approach.

Some shrinkage protects agent wellbeing and service quality. Breaks reduce fatigue. Coaching improves performance. Training builds confidence. Team meetings keep people informed. Removing these activities may improve short-term availability, but it can damage long-term performance.

The real goal is to reduce avoidable shrinkage, not remove useful activity. High sickness, repeated lateness, system downtime, unnecessary meetings, or poorly planned admin may indicate problems that need attention. But planned development and recovery time should not be treated as waste.

A contact centre that constantly cancels coaching and training to keep people on queue may protect today’s service level while creating tomorrow’s quality problem.

Common shrinkage planning mistakes

The first mistake is using a single generic shrinkage percentage for every team, day, and season. Shrinkage changes. Mondays may differ from Fridays. Winter sickness may be higher. Holiday periods may reduce availability. New starters may need more training. Different teams may have different absence patterns.

The second mistake is using unrealistic assumptions. Some organisations plan shrinkage based on what they want it to be rather than what the data shows. This creates schedules that look efficient but fail in practice.

The third mistake is not separating planned and unplanned shrinkage. Without that distinction, it becomes harder to know whether the issue is poor scheduling, high absence, excessive meetings, or operational disruption.

Managing shrinkage properly

Managing shrinkage starts with accurate data. Workforce teams need to track where time is going and understand which elements are planned, unplanned, avoidable, or necessary.

They should review shrinkage regularly and adjust assumptions based on reality. If sickness trends rise, forecasts need updating. If training is planned, schedules need to include it. If system issues are creating lost time, that needs escalation beyond the workforce team.

Supervisors also need visibility of shrinkage during the day. Intraday management helps teams respond when actual availability differs from the plan.

Shrinkage will never disappear. Nor should it. The goal is to understand it well enough to plan honestly, protect service levels, and avoid putting unnecessary pressure on agents.