How to Calculate Utilization Rate (Formula + Examples)
Utilization rate is one of the most quoted numbers in professional services and one of the most quietly misreported. It looks simple — a ratio of two hour totals — but almost every part of it is a judgement call: which hours count, which hours are “available”, and where the numbers come from in the first place.
This guide covers the formula, worked examples for both billable and internal teams, the benchmark ranges that actually matter, and the mistakes that make the number lie.
The utilization rate formula
At its most basic:
Utilization rate = (Hours worked toward an objective ÷ Available hours) × 100
The two inputs are where all the nuance lives.
Available hours is not “hours in the week”. Start from scheduled hours and subtract holidays, PTO, sick leave and any time that was never plannable. A full-time employee with 40 scheduled hours and one public holiday has 32 available hours that week, not 40.
Hours worked toward an objective is the part that changes by team:
- Billable utilization counts only client-chargeable hours.
- Productive / internal utilization counts all hours spent on planned work — delivery, internal projects, roadmapped tasks — billable or not.
Pick one definition and hold it constant. Most reporting problems come from mixing the two between people or between weeks.
Worked example 1 — a billable consultant
- Scheduled: 40 hours
- PTO / holiday that week: 0
- Available hours: 40
- Billable client work: 30 hours
- Internal meetings, admin, training: 10 hours
Billable utilization = (30 ÷ 40) × 100 = 75%
75% sits right in the healthy band for billable work. The other 25% isn’t waste — it’s the admin and overhead that a sustainable services business budgets for.
Worked example 2 — an internal product team
- Team of 5, scheduled 200 hours
- One person on 2 days PTO: −16 hours
- Available hours: 184
- Hours on roadmapped delivery work: 147
- Hours on unplanned interrupts, support, context-switching: 37
Productive utilization = (147 ÷ 184) × 100 ≈ 80%
80% planned-work utilization is a solid number for an internal team. The 20% going to unplanned work is the figure worth watching over time — if it climbs to 35–40%, the roadmap will keep slipping no matter how many hours people put in.
Benchmark ranges
| Team type | Typical target | Watch above |
|---|---|---|
| Billable services / agency | 70–80% | ~85% |
| Internal product / engineering | 70–85% | ~90% |
| Support / operations (reactive) | 60–75% | ~85% |
Two rules of thumb apply across all of them:
- 100% is not the goal. A team planned at 100% utilization has no capacity for the unexpected, and the unexpected always arrives.
- Sustained high utilization is a risk indicator. Weeks above 90% are fine occasionally. Quarters above 90% predict burnout, quality problems and attrition.
Why the number often lies
The formula is trivial. The inputs are where it breaks.
Self-reported hours smooth over reality
A timesheet filled in on Friday afternoon is a reconstruction, not a record. It rounds, it forgets the 40-minute detour into someone else’s problem, and it rarely captures how fragmented the week actually was. Utilization built on that data tends to look calmer and higher than the week felt.
“Available hours” gets set once and never updated
If your denominator is a static 40 hours per person, every holiday, sick day and half-day of onboarding inflates apparent idle time and drags utilization down for reasons that have nothing to do with the work.
One number hides the distribution
A team at 78% average utilization can be five people all near 78%, or two people at 95% and three at 65%. The average looks healthy; half the team is heading for burnout. Always look at the spread, not just the mean.
Measuring it accurately
The fix for most of the above is to calculate utilization from passively measured activity data rather than memory:
- Available hours derived from the actual schedule, with PTO and holidays already netted out
- Worked hours from real active time in delivery tools and projects, not a timer someone forgot to stop
- The full per-person distribution, not just the team average
- The same definition applied consistently every week
That’s the model Optimetrix uses: activity metadata — active application, project, focused vs idle time — rolled up into utilization by person, team and week, so the number reflects what actually happened instead of what someone remembered on Friday.
The bottom line
Utilization rate is only as good as the two numbers you divide. Fix “available hours” so it tracks the real schedule, pick one definition of “worked hours” and keep it, look at the distribution instead of the average, and — wherever you can — feed the formula from measured activity rather than self-reported timesheets. Do that and utilization stops being a number people argue about and starts being one you can plan with.