OneRostaStart free

Shrinkage Explained: Where Your Support Team's Scheduled Hours Actually Go

8 min readBy Maria L
Smiling agent on a video call at home

Quick Summary: Shrinkage is the share of scheduled or paid time when support agents are unavailable for customer interactions. It can include leave, training, meetings, breaks, and other off-queue activities, depending on how your organization defines the measure. This guide explains how to define and calculate shrinkage consistently, estimate the capacity you need, and reflect unavailable time in your roster.

Every new support manager experiences the same baffling arithmetic in their first quarter.

You have a team of 6 agents, each scheduled for 40 hours. That gives you 240 scheduled hours for the week, but it does not mean all 240 hours are available for customer interactions.

So you build a schedule that fills 240 hours of shifts across Live Chat, Phone, and Email.

During the week, agents also take approved leave, attend meetings and training, complete coaching, take breaks, or work on projects away from the queue. Suppose your records show that 60 of those 240 scheduled hours were unavailable for customer interactions. That is 25% shrinkage for this example.

The 60-hour figure is illustrative, not a benchmark. Your own result depends on what activities you include and how your team records them. If you do not account for unavailable time, your coverage plan can promise more customer-facing hours than the team can actually provide.

What Is Shrinkage in Workforce Management?

In customer support and workforce management (WFM), shrinkage describes the share of available work time when agents are not available to handle customer interactions. Teams may define the denominator differently, so state whether your calculation uses paid hours, scheduled hours, or another consistent base. One common planning formula is: 1

Formula: Shrinkage % = Unavailable Hours ÷ (Hours in the chosen denominator) × 100

Shrinkage is not a measure of laziness. It can include planned activities such as coaching, training, team meetings, and breaks, as well as unplanned absence. Which items belong in the calculation depends on how you define the measure and whether your planning system already schedules those activities separately. A useful starting point is to document every included category and apply the definition consistently.

The Two Buckets: External vs. Internal Shrinkage

A common way to organize the categories is to separate time away from the workplace from off-queue activities during a shift. Exact classifications vary by organization, so document what your own calculation includes:

1. External Shrinkage (Out-of-Office)

External shrinkage covers time when the agent is away from work entirely:

  • Approved Annual Leave / PTO: Vacations and personal days.
  • Public & National Holidays: Bank holidays across the countries where your remote team resides.
  • Unplanned Sickness & Emergencies: Last-minute callouts, migraines, child sickness, or family emergencies.
  • Parental or Bereavement Leave: Formal extended leave policies.

Planning note: Track planned time away, such as approved leave, separately from unplanned absence where useful. Both can reduce the capacity available for scheduled customer coverage, but they may need different forecasts and responses.

2. Internal Shrinkage (In-Office, Off-Queue)

Internal shrinkage covers time when the agent is clocked in and working, but not actively handling tickets, calls, or chats:

  • Team Meetings & 1-on-1s: Weekly syncs, retrospectives, and managerial catch-ups.
  • Training & Coaching: Onboarding, QA score reviews, product feature briefings.
  • Rest & Meal Breaks: Scheduled lunch hours and mandatory 15-minute screen breaks.
  • Special Projects & Extra Tasks: Writing help center articles, testing bug reports, or mentoring junior agents.
  • System Downtime & Technical Issues: Internet drops, SaaS outages, or VPN disconnections.

Planning note: Internal activities may happen during a shift. If the work is necessary, include it in the operating plan so queue coverage does not assume the agent is continuously available.

Is There a "Normal" Shrinkage Rate?

There is no single percentage that applies to every support team. The result depends on team policies, work type, leave entitlements, training requirements, and the exact denominator and activities you count. Instead of borrowing an industry figure, calculate a baseline from your own historical records. The contact-center formula commonly combines internal and external shrinkage hours over available hours. 1

For a useful comparison over time, keep the measurement method stable. You can look at monthly or rolling-period results, then investigate changes by category: for example, planned leave, sickness, training, meetings, or system interruptions. Treat an unusual week as a signal to understand, not as proof that someone is underperforming.

How to Estimate Capacity Requirements with Shrinkage

If you need a certain number of productive hours and expect a known share of scheduled hours to be unavailable, divide productive hours by the available share. This is a capacity-planning estimate, not a complete schedule. It does not replace interval-level staffing calculations for real-time channels.

The Correct Formula (Gross-Up Math):

Formula: Gross Hours Needed = Net Productive Hours Needed ÷ (1 - Shrinkage Rate)

Let’s apply this to a simplified example:

  • Illustrative net productive hours required: 160 hours per week
  • Measured historical shrinkage: 25% (0.25)

Formula: Gross Hours Needed = 160 ÷ (1 - 0.25) = 160 ÷ 0.75 = 213.3 hours

Formula: Total Agents Needed = 213.3 ÷ (40 hours/week) = 5.33 agents

This gives a rough capacity equivalent of about 5.33 forty-hour schedules. It does not mean that 5.33 agents will provide four agents on queue at every moment. To plan continuous coverage, also account for demand by interval, skills, shift lengths, handovers, rest requirements, and local working-time rules.

4 Rules for Managing Shrinkage Without Micromanagement

Use shrinkage as a planning measure, not as a proxy for individual effort. To manage it constructively:

1. Schedule Internal Shrinkage Intentionally

Coordinate 1-on-1s and training with the forecast so they do not unintentionally reduce coverage during a busy interval.

  • Where possible, schedule meetings and coaching during periods with lower forecast demand, after checking the impact on coverage.
  • Explicitly allocate "Extra Task" hours on the shift schedule so off-queue work is visible to everyone.

2. Connect Approved PTO Directly to the Shift Schedule

Approved time off recorded in a separate HR system can be missed when the operational roster is maintained elsewhere. That can leave the roster showing coverage from someone who is unavailable.

  • Keep your leave tracker and your shift roster unified so approved PTO automatically flags coverage gaps weeks before they happen.

3. Review Trends Over Time

Avoid drawing conclusions from one unusually high or low week. Compare a consistent period over time, and review seasonal patterns separately so recurring capacity needs are visible.

4. Protect Dedicated "Off-Queue" Time

If agents are expected to complete documentation, QA reviews, or other off-queue work, set aside time for it and make its effect on customer-facing capacity visible.

How OneRosta Makes Shrinkage Visible and Manageable

A basic shift spreadsheet may show that someone is scheduled from 09:00 to 17:00 without making clear how those hours are split among customer channels and other tasks.

OneRosta helps make task assignments and coverage visible in the schedule:

  • Dedicated Task Types: Assign shifts specifically to Live Chat, Phone, Email, or Extra Tasks (training, documentation, meetings). You know exactly how many agents are actually customer-facing.
  • Integrated Leave Tracking: Approved annual leave, sick days, and contractor time-off live in the same grid. You never have to cross-reference a separate HR spreadsheet.
  • Instant Deficit Alerts: When planned leave or an off-queue task drops real-time queue staffing below your target, the hourly coverage strip highlights the gap in red.
  • Auto-Balanced Scheduling: OneRosta can generate and balance task assignments across Live Chat, Phone, Email, and Extra Tasks, while leads review coverage and make adjustments.

Plan for Reality, Not Wishful Thinking

Shrinkage isn't a problem to eliminate—it is the natural cost of employing human beings who need rest, growth, and lives outside of work.

When you measure unavailable time consistently and include it in capacity planning, the roster is more likely to reflect the hours your team can actually cover. Then review the schedule against demand, skills, and approved leave before publishing it.

Ready to see what your real team coverage looks like?
Explore OneRosta's free interactive sandbox demo (no sign-up needed) →

Staffing & shrinkage calculator

Seats needed, daytime (12h)3
Seats needed, overnight (12h)1
Contracted hours per agent / week40h
Shrinkage30%

Seat-hours per week

336

Agents needed (minimum)

12

A planning estimate only — it does not model queue arrival patterns.

See it on a real rota

Try the interactive sandbox — no account or sign-up needed.