A Simple Formula for Whether Your Service Team Is Overloaded

Available capacity per person is working hours minus time lost to meetings, administrative work, and reasonable breaks. Say your team's actual working week nets out to somewhere around 60 to 70 percent of a nominal forty-hour week once meetings and admin are subtracted, which is a typical range for most service roles once you subtract everything that isn't direct client or ticket work. Multiply that by headcount to get team capacity, then compare it against demand: the actual hours of work the team's current ticket or project volume requires. When demand consistently runs above capacity, you have a real staffing gap, not a motivation problem.

Work through the capacity check in this order:

1. Take each person's working hours and subtract time lost to meetings, administrative work, and reasonable breaks to get available capacity.
2. Multiply available capacity per person by headcount to get the team's total capacity.
3. Estimate demand from actual time-tracking data, weighted by average handling time per category rather than raw ticket count.
4. Add a rough estimate of after-hours or weekend work, so it is not treated as free.
5. Compare demand with capacity each month, and treat a gap that persists for two or three months as a real staffing signal.

The most common mistake is estimating demand from ticket count alone, without weighting for how long each ticket actually takes. Ten quick tickets and ten complex ones are wildly different workloads with the same count. Pull actual time-tracking data for a representative sample of recent work, and weight your demand estimate by real average handling time per category rather than treating every ticket as equivalent.

A second common mistake is measuring demand only during business hours, missing the after-hours or weekend load that some service teams quietly absorb without it ever showing up in a standard capacity calculation. If your team fields any after-hours escalations at all, however occasional, build a rough estimate of that time into the demand side rather than treating it as free.

Say a five-person support team has 35 available hours each per week after meetings and admin work, giving 175 hours of weekly capacity, and say last month's ticket volume, weighted by actual handling time, worked out to 210 hours of demand. That's a 35-hour weekly shortfall, roughly one additional full-time person's worth of work the team is absorbing through extra hours or slipping response times, and that gap is the number worth bringing to a staffing conversation, not a vague sense that the team seems stretched.

Running the same math for each of the last three or four months, rather than a single snapshot, shows whether the gap is a temporary spike or a settled pattern, which changes what kind of response actually makes sense.

A one-off busy week doesn't need a staffing response, but a gap that persists for two or three months running is a real signal. Options include hiring, redistributing some work to automation for the mechanical parts of the workload, or deliberately reducing scope, cutting a service tier or response commitment that's no longer sustainable at current staffing. Choosing none of these and hoping the team absorbs it indefinitely is how burnout-driven attrition happens.

Whichever option you choose, communicate the decision to the team, not just the number. A team that sees leadership actively responding to a documented gap tolerates a temporarily tight quarter far better than one left to assume nobody's paying attention to how stretched they are.

When a gap persists, test each option against the numbers before choosing. Hiring closes the gap fully but takes time to pay off. Automation helps only if a meaningful share of the demand hours are mechanical, so tag a sample of recent work as mechanical or judgment before promising savings. Reducing scope, such as relaxing a response commitment, closes the gap fastest but changes what customers receive. A common mistake is choosing whichever option feels easiest to approve. The decision rule is to pick the option whose effect you can measure against the demand figure next quarter, then rerun the calculation to confirm the gap actually shrank.

Rerun the calculation quarterly, or any time headcount or ticket volume shifts meaningfully. A capacity model built once during a hiring push and never updated stops reflecting reality within a couple of quarters, especially as a team's average ticket complexity changes with the product or customer base.

MeetMyCOO's AI COO, Olivia, can pull the updated ticket-volume and time-tracking numbers into a refreshed calculation each quarter, though the staffing decision that follows from a persistent gap still needs a person who owns the budget and the team relationship.