Ask five people on a services team what "good utilization" looks like and you'll usually get five different numbers, and at least two different definitions of what's even in the calculation. That gap matters, because utilization rate drives staffing decisions, bonus structures, and hiring plans. Get the formula or the benchmark wrong and you'll either burn out a team that looks fine on paper, or hire ahead of demand that was never really there. This guide covers the exact formula, what realistic ranges look like by role, and the pitfalls that make the number lie.
In this guide
The utilization rate formula Benchmark ranges by role Utilization vs profitability What utilization trends tell you about staffing Common pitfalls in measuring utilization Frequently asked questions
The Utilization Rate Formula
Utilization rate is calculated as billable hours divided by available hours, expressed as a percentage:
Utilization rate = (Billable hours ÷ Available hours) × 100
The numerator is straightforward in theory: the hours a person spent on work a client is actually being billed for. The denominator is where most of the confusion lives. Available hours means the total working hours in the period, minus time off, holidays, and any other paid non-working time. It is not simply "40 hours a week times the number of weeks."
Say someone works a standard 40-hour week over a four-week month, giving 160 total working hours. If they took one paid holiday (8 hours) and no other time off, their available hours for that month are 152, not 160. If they logged 118 billable hours against client work in that same period, their utilization rate is 118 ÷ 152, which comes out to about 78%. Swap in the wrong denominator, say the full 160 hours instead of 152, and the same 118 billable hours produces a rate of roughly 74% instead, a difference that looks small until you're applying it across a 30-person team every month.
Benchmark Ranges by Role
There's no single "correct" utilization target across every service business, targets should reflect your own cost structure, contract mix, and margin goals. That said, a few patterns show up consistently across agencies, consulting firms, and IT services providers, because the amount of non-billable work built into a role tends to scale with seniority and responsibility:
- Individual contributors focused mainly on delivery commonly run in the 70%–85% range
- Team leads and project managers splitting time between delivery and coordination often land closer to 50%–65%
- Partners, principals, and account leads with heavy business development duties are frequently much lower, sometimes 30%–45%
- New hires and juniors in ramp-up periods usually sit below their eventual steady-state target for a quarter or two
- Fixed-fee heavy teams tend to run lower reported utilization than pure time-and-materials teams, even at similar effort levels
Treat these as common industry patterns rather than a scorecard to hit exactly. A firm with lean overhead and low billing rates might need higher utilization to hit its margin goals than a firm charging premium rates with a smaller team.
Utilization vs Profitability, Two Different Numbers
It's tempting to treat a high utilization rate as proof that a team, or a firm, is doing well. It isn't, not on its own. Utilization only tells you how much of someone's time got billed, it says nothing about whether the rate charged for that time actually covers what the person costs to employ, plus overhead, plus a margin.
A consultant running at 90% utilization but billed out at a rate that barely covers their loaded salary is busy, not profitable. Flip it around, and a team running at a modest 60% utilization but billing premium rates on every hour can post a healthier margin than the "fully booked" team next door. Utilization measures activity. Profitability measures whether that activity was worth what it cost.
A fully utilized team can still lose money. Utilization tells you how much time got billed, not whether the rate on that time covers cost and margin. Always read utilization alongside realized rate and project margin, never on its own.
What Utilization Trends Tell You About Staffing
A single utilization number for one week rarely means much, holidays, one big project wrapping up, or a slow onboarding period can swing it in either direction. The useful signal is the trend over several months, tracked consistently across the same roles.
Utilization that climbs steadily across a team over two or three months, without a corresponding drop in quality or a spike in overtime, is usually an early hiring signal, demand is outpacing current capacity, and the team will hit a ceiling on delivery before you notice it in revenue. Utilization that drifts downward over the same window points the other way, either the pipeline has slowed, or the team is staffed ahead of the work actually in hand. Neither read is reliable from a single snapshot, which is why the trend line matters more than any one week's number.
Seeing that trend clearly requires time data that's consistent and centralized rather than scattered across individual spreadsheets. This is one of the areas where a connected platform like Autovella pays for itself, utilization rolls up automatically from logged time by role, team, and project, so a staffing conversation starts from the same numbers everyone trusts instead of a reconciliation exercise. You can see how time tracking and analytics connect on the features page.
Common Pitfalls in Measuring Utilization
Most utilization numbers that get questioned later turn out to have one of a small number of measurement problems baked in from the start:
Counting time off as available hours. If a public holiday or approved vacation day still counts toward the denominator, the resulting rate understates how utilized someone actually was during the hours they were working, and comparisons across months with different holiday counts stop being fair.
Not distinguishing billable from non-billable hours in the numerator. Internal meetings, training, and admin work logged under a client project code can inflate the "billable hours" figure even though none of it will ever appear on an invoice. If a team's time tracking doesn't tag each entry as billable or non-billable at the point of entry, the utilization number is really just an activity number wearing a utilization label.
Inconsistent definitions across teams. One team counting internal project work as billable and another excluding it entirely will produce numbers that look comparable on a dashboard but aren't measuring the same thing.
Autovella's time tracking flags each logged entry as billable or non-billable at the moment it's recorded, and factors approved time off out of the available-hours calculation automatically, so the number teams see is already built on a consistent definition rather than a manual cleanup job at month end.
See utilization roll up automatically from logged time
Get a live walkthrough of time tracking, analytics, and staffing views mapped to your team.
Frequently asked
It depends on the role. Individual contributors doing mostly delivery work commonly run between 70% and 85%, team leads with mixed delivery and management duties often land between 50% and 65%, and partners or principals with heavy business development responsibilities are frequently much lower, sometimes 30% to 45%. These are common industry patterns, not fixed rules, so the right target for your firm depends on your cost structure and margin goals.
No, and it's often a warning sign rather than a good one. Utilization only measures how much time got billed, not whether the rate charged covers cost and margin, and a team pinned at or near 100% for long stretches usually has no slack for scope changes, internal work, or time off, which tends to show up later as burnout or quality problems.
Weekly for individual course-correction and monthly for staffing and hiring decisions works well for most firms. A single week can be noisy because of holidays or one large project ending, so look at rolling averages over four to eight weeks before treating a shift in utilization as a real trend rather than noise.