How to calculate your team's utilization rate (without the average lying to you)

Knowing how to calculate your team's utilization rate is the easy part; using the number well is where teams struggle. Most guides hand you a one-line formula and a single team percentage, then wish you luck. That single percentage is the one number most likely to mislead you. This guide walks through the correct team-level method, the denominator choices nobody explains, realistic benchmarks, and how to read the number so it protects your people and your margin.

What is your utilization rate actually telling you?

I spent nine years in agencies before I joined Teamwork.com, and utilization was the number everyone quoted and almost nobody trusted. At its simplest, utilization rate is the share of a person's available time that goes to billable or productive work. Billable hours sit on top, available hours sit underneath, and the result is a percentage that tells you how much of the capacity you pay for is actually earning.

That definition is settled, and we have covered the basic single-person formula and the wider resource view in depth already. If you want the ground-level walkthrough, start with the utilization rate formula and definition and the broader resource utilization guide.

The rest of this piece assumes you know that formula. The problem is not the equation. The problem is what happens the moment you apply it to a whole team. Real teams do not all work the same hours, in the same roles, at the same time. That is where the tidy percentage starts to mislead, and where most reporting quietly goes wrong.

Why a single utilization average hides your real problem

Leaders trust one average that hides who is overloaded and who is coasting. The team average looks like an answer. It is really a hiding place.

An average is a single point that erases the distribution behind it. A team sitting at 75% can be five people all at 75%, or it can be one person at 95%, one at 90%, and three hovering near 63%. Those are completely different businesses, and the headline number treats them as identical.

The math is doing exactly what math does. Averaging is designed to smooth out variation, and variation is the entire signal you need here. Using the mean to manage a team's workload is like judging a river safe to cross by its average depth. The number is accurate. The person who drowns is standing in the deep bit.

That distribution is where the damage lives. In my agency years, the burnout driver was never the total workload; it was the imbalance. The same two people stayed late every week while two others left on time, and the team average stayed reassuringly healthy. Averages hide exactly the problem that costs you people.

There is a second cost, too, and it is commercial. When you only see the mean, you cannot tell the difference between a team that needs a hire and a team that just needs its work redistributed. So you either over-hire into hidden idle capacity, or you push a stretched team harder because the number looks fine. Both decisions come from the same blind spot.

So the fix is not a better formula. It is a habit: never look at the average without also looking at the range underneath it. I call that range the Utilization Spread, and it is the number I check first. If your report only gives you one figure, you are not managing badly, you are flying with one instrument.

A tight spread around a healthy mean is a good sign: the load is shared and the number is real. A wide spread around the same mean is a warning dressed up as a pass. Once you start reading the two together, you stop treating utilization as a scoreboard and start treating it as a diagnostic, which is the only thing it was ever good for.

How do you calculate your team's utilization rate the right way?

Teams average percentages because spreadsheets make it easy. The correct team calculation is not "work out everyone's percentage, then average them." That is the version most spreadsheets default to, and it is subtly wrong. The right way sums the raw hours first, then divides once. Here is the formula:

$$\text{Team utilization (\%)} = \frac{\text{Total billable hours}}{\text{Total available hours}} \times 100$$

I think of it as a three-step method, the Weighted Team Utilization Method. Do the steps in order and the number comes out honest.

Step 1: Total up available hours, deliberately

Start underneath the line, not on top of it. Available hours are the denominator, and they decide everything the percentage means. Add up each person's real working hours for the period, then decide, on purpose, what to subtract.

Public holidays, booked leave, and known standing commitments come out if you want a working-time rate. If you leave them in, a person on a week of annual leave looks like a coasting employee rather than someone who was simply not there. That single error can drag a team rate down five or six points and send you chasing a problem that does not exist. Most teams get this wrong in the opposite direction, too, by using a flat 40-hour week for everyone, including part-timers and contractors on shorter commitments.

A practical rule: subtract only the time nobody could have billed anyway, and nothing else. Optional admin and context-switching stay in, because those are the hours you actually want the number to expose. Cut too much and every rate flatters you; cut too little and real availability disappears.

The denominator is a choice, and I will come back to it, because it is the single most common reason two people calculate "the same" rate and get different answers.

Step 2: Total up billable hours

Now the numerator. Add up the hours that actually earned revenue across the whole team, not the hours that merely felt busy. Logged time is not the same as billable time, and treating them as equal is how a fully booked team still misses its targets.

Step 3: Divide once, then read the spread

Divide total billable by total available, times 100. That single division gives you the true team rate. Then, and this is the part that matters, calculate the Utilization Spread: the gap between your highest and lowest individual.

For example, take a five-person team over one week, and notice how the two methods disagree.

Add the raw hours: 118 billable across 168 available. The weighted team rate is 70%. Now average the five individual percentages instead: you get 75%, because Person E's 100% from a single eight-hour day counts for exactly as much as Person A's full week. The averaged method flatters you by five points and quietly overweights your smallest contributor.

Both numbers sail past the real story anyway. Among the full-timers, Person A is at 95% and Person D is at 50%, a 45-point spread inside a team that reads as healthy at a glance. Person A is one bad week from burnout while Person D has capacity nobody is using. The average erased both facts; the weighted rate plus the spread put them back where you can act on them.

Run this weekly, not monthly. A spread you spot on Monday is a reassignment. The same spread spotted at month-end is a resignation letter and an unhappy client. If you would rather not rebuild this every week, the Teamwork.com utilization rate calculator gives the weighted number fast; check it against the by-person view.

Billable, resource, or productive: which utilization are you measuring?

Before anyone argues about whether 70% is good, I ask a duller question: 70% of what? The word "utilization" hides at least three different metrics, and teams conflate them constantly. The variant you pick changes the denominator, and the denominator changes the answer.

Billable utilization measures revenue-earning time against available time. Resource, or total, utilization measures all productive work, billable or not, against capacity. Productive utilization sits in between, counting useful internal work like enablement or pitching that is not billed but is not waste either. None of these is the "correct" one; they answer different questions, and a mature team tracks more than one.

The gap between these is not academic. Take one consultant with 30 billable hours in a week. Against a fixed 40-hour capacity she is at 75%, against 32 net working hours she is at 94%, and against 34 recorded hours she is at 88%. Same person, same week, three defensible numbers, and only one of them should drive your decision.

Pick one denominator, write it down, and hold everyone to it. Teams that argue about whether their rate is good are usually two people using two different denominators without realizing it. The number is only comparable when the bottom of the fraction is agreed. For the availability side of this, team availability management is a useful companion.

What does a good team utilization rate look like?

The honest answer to "what is a good rate" is that it depends on the seat, not the person. I have watched leaders set one blanket target across a whole team and then wonder why their senior people quietly resented it.

In my agency experience, billable targets for delivery teams usually land around 70% to 80%. That headline masks big differences by role. A delivery specialist whose whole job is billable can sit high. A team lead who also runs resourcing, reviews work, and joins pitches cannot, and should not, hit the same figure. Judge them against the same target and you punish the person doing the work that keeps the rest of the team billable.

Set the target against the seat, then watch the trend rather than the single reading. A number climbing week on week toward the ceiling tells you more than a number that looks fine today. A person who jumps from 70% to 90% and stays there is not a win to celebrate; they are a risk to check on. Direction matters more than the snapshot.

Industry benchmarks are a useful sanity check, but your own history is the better yardstick. Say your delivery team has held 78% for a year and this quarter it is drifting to 68%. That ten-point drop tells you something specific about your pipeline or your scoping. A generic industry average never will.

The move that matters is what you do with the trend. A steady climb means it is time to hire or push back on intake, before the overload lands on your best people. A steady fall means the pipeline needs attention now, while there is still slack to redeploy. Either way, the number earns its keep only when it changes a decision. Use the outside number to set the rough zone, then manage against your own baseline and your own spread.

Why chasing 100% utilization can quietly erode margin

Teams chase 100% as if it were a profit target, then pay for it later. A healthy rate has a floor, but it also has a ceiling. The instinct is that higher utilization means more profit. Past a point, the opposite is true, and the point arrives earlier than most leaders expect.

A team at 100% has no slack for rework, no room to pitch the next piece of work, and no capacity for the unbillable admin that keeps clients happy. The first curveball, a sick day, a scope change, a delayed approval, has nowhere to go except overtime and dropped quality. And it lands on the same two people every time, the ones the average never flagged.

Over-utilization does not raise margin; it raises delivery cost while burning the people you most need to keep. Eagle Hill's 2024 workforce research found workload is the leading reported driver of employee burnout.

Think about what a fully booked week actually removes. It removes the hour to fix the deliverable properly instead of patching it, the hour to scope the renewal, the hour to write the case study that wins the next client. Those hours are not billable, but they are the ones that compound. A team run at 85% with real slack often out-earns a team pushed to 100%, because the slack is where next quarter's revenue gets built.

The commercial pressure is only getting sharper. In Teamwork.com's 6 Strategic Shifts for 2026 research, 66% of services leaders said clients are now more demanding but less willing to pay. As AI compresses the hours a deliverable takes, every billable hour you lose to a burned-out, badly balanced team comes straight off margin, not off cost base. That is why utilization is a financial metric, not just a productivity one, and why it belongs next to your profitability reporting.

Data point: When Community Link Consulting replaced fragmented spreadsheets with connected resource management, they increased billable hours and reduced team burnout at once. The two are not a trade-off once you can see the spread.

There is a forward-looking payoff, too. Once you calculate utilization weekly and accurately, the trend becomes a forecasting signal. A team creeping from 75% to 88% over a month is telling you a hire is coming, whether you planned one or not. A team sliding the other way is telling you the pipeline needs attention now, not next quarter. Utilization calculated properly stops being a rear-view report and starts being an early read on capacity and revenue.

The target, then, is not "as high as possible." It is "as high as you can hold without the spread blowing out." That is a very different management goal, and it is the one the average will never give you.

Which mistakes make your utilization numbers unreliable?

Most broken utilization reporting is not a tooling failure. It is a handful of small, repeatable errors that quietly corrupt the number until nobody believes it. I have made most of these myself.

The five errors that do the damage are simple:

• Averaging percentages instead of summing hours, which distorts the team rate.

• Counting all logged time as billable, so the numerator inflates and targets look met when they are not.

• Leaving holidays and leave in the denominator, which drags healthy people into a false problem.

• Reporting monthly, so you learn about an imbalance weeks too late to rebalance it.

• Holding every role to one target, which penalizes people doing essential non-billable work.

Any one of these turns a decision-grade number into a vanity metric. Together, they are why so many leaders shrug and say their utilization report is not really accurate. It could be; it is just being calculated in a way that guarantees it will not be.

The pattern underneath all five is the same: each one trades a little accuracy for a little convenience, and the errors compound until the number and reality quietly part ways. That is why the fix is a discipline, not a dashboard. Agree the method once, apply it the same way every week, and the report earns back the trust it needs to actually drive a decision.

Every one of these is fixable, and most disappear the moment the calculation stops living in a spreadsheet. For a running head start, the team utilization tracker template sets up the weekly view. For the wider improvement playbook, we go deeper in how to track and improve team utilization.

How Teamwork.com keeps team utilization honest

Picture opening your resourcing view on a Monday and seeing, in one screen, not a single team percentage but who is over, who is under, and by how much. That is the difference between a number you report and a number you can act on, and it is the gap most spreadsheets never close.

Spreadsheets fail quietly here: one missed timesheet, one stale formula, and the number everyone trusted was wrong for a week before anyone noticed. A connected platform removes the manual steps where that rot sets in, against the same three-step method we just walked through.

That is why Teamwork.com is built as an agentic PSA (professional services automation) platform. Project tools track the work but cannot manage the money. Traditional PSAs manage the money, but teams resist using them, so the hours going in are unreliable. Teamwork.com does both, in a platform teams actually want to use, so the hours behind your utilization rate are real.

See the spread without a manual sort: the Utilization Report shows the weighted team rate and every individual behind it, so the distribution is obvious at a glance.

Spot who is stretched before it becomes burnout: the AI Utilization Summary reads the floor for you and flags who is over or under capacity, so you are not hunting across tabs to find the two people the average hid.

Rebalance in a few drags: the Workload Planner lets you shift work off the person at 95% and onto the one at 50%, which is the intervention the spread was telling you to make.

Get a reliable denominator at the source: built-in time tracking captures billable versus non-billable time as it happens, so the bottom of your fraction is real rather than remembered.

Set realistic targets for different roles: utilization targets can be set per person, so a director and a delivery specialist both show as on track against different goals, and nobody games a number that was never fair to them.

None of this changes the math. It just makes the honest version of the math the one you see by default, every week, without a spreadsheet quietly lying to you in the background. The formula was never the hard part. Seeing the truth it points to, in time to do something about it, is the whole job, and that is the part worth building a system around.

Frequently asked questions