Utilization rate (also spelled utilisation) is the share of a person’s available working hours spent on client work: client hours divided by available hours, times 100. A consultant with 152 available hours who records 96 on client projects has a utilization rate of 63%.
Utilization is the number agencies quote to each other at conferences and almost never define the same way twice. One agency counts every hour recorded against a client. Another counts only hours that ended up on an invoice. A third counts hours against a target of 40 a week, while its team actually works 45. All three say "we run at 70%" and mean three different things.
The number is worth having. It is not worth comparing with anyone else’s until you know what went into it.
What utilization actually measures
Utilization is the share of available time that reaches client work:
client hours ÷ available hours
Both sides need a decision before the number means anything.
- Available hours. Contracted hours, minus public holidays and leave. If you leave holidays in the denominator, August always looks like a bad month.
- Client hours. Time recorded against a client project. Whether unbilled client work counts is your call, but make it once and keep it: a scope change you absorbed is still client work, even if nobody paid for it.
- Everything else. Internal projects, sales calls, recruitment, the weekly team meeting. These are not waste, and treating them as such is how a team learns to record them as client work.
A worked example
A developer is contracted for 168 hours this month. Two days of leave take 16 hours out, leaving 152 available. Of those, 96 are recorded on client projects, 24 on an internal product, 16 on meetings and 16 on recruitment interviews.
96 ÷ 152 is 63%. Two things follow. First, the month was not idle: the other 56 hours went somewhere identifiable. Second, if next month’s target is 75%, someone has to decide which of those 56 hours stops happening, because the hours will not free themselves.
Utilization, billable utilization and realization
Three ratios sit close together and answer different questions. Take the same developer: of the 96 client hours, 84 were billed at a standard rate of 40, and 3,000 was actually invoiced.
| Ratio | Formula | Example |
|---|---|---|
| Utilization | client hours ÷ available hours | 96 ÷ 152 = 63% |
| Billable utilization | billed hours ÷ available hours | 84 ÷ 152 = 55% |
| Realization | amount invoiced ÷ (billed hours × standard rate) | 3,000 ÷ 3,360 = 89% |
The gap between the first two is client work nobody paid for: 12 hours here. What realization loses is discounts and written-off time. A team can raise its utilization and lose money at the same time, if the extra hours land in that first gap.
What a high number hides
- No slack. A team at 90% has no capacity for the urgent request that always arrives, so the urgent request turns into overtime or a missed date.
- The wrong work. Utilization does not care whether the hours were profitable. A team can be fully utilized on a project that loses money, which is why it belongs next to margin, not instead of it.
- Quality and turnover. Sustained high utilization is paid for later, in rework and in people leaving.
- Averages. A team at 65% can be two people at 95% and two at 35%. The average hides the problem you can actually fix.
What the average hides: a four-person example
| Person | Available hours | Client hours | Utilization |
|---|---|---|---|
| A | 152 | 144 | 95% |
| B | 152 | 137 | 90% |
| C | 152 | 61 | 40% |
| D | 152 | 53 | 35% |
| Team | 608 | 395 | 65% |
“65%” sounds healthy. Behind it, two people have no room for the next urgent request and two are waiting for work. Moving 40 hours of this month’s client work from A and B to C and D leaves the team average exactly where it was, and it is the change that prevents the next missed deadline.
Utilization rate by role
One target for the whole company is where most utilization figures go wrong. Roles carry different amounts of work that is necessary but not client work, so each role needs its own ceiling. The quickest way to set one is to subtract the non-client hours a role genuinely needs from its available hours.
| Role (example) | Available hours a month | Non-client hours the role needs | Realistic ceiling |
|---|---|---|---|
| Designer or developer | 152 | 24: team meetings, reviews, learning | 128 ÷ 152 = 84% |
| Consultant | 152 | 40: proposals, sales calls, reviews | 112 ÷ 152 = 74% |
| Account or project manager | 152 | 56: planning, internal coordination, reporting | 96 ÷ 152 = 63% |
| Founder or managing director | 152 | 100: sales, hiring, finance, management | 52 ÷ 152 = 34% |
The figures are an example, not a benchmark: replace the third column with the hours your own roles need. The point is the method. A target set this way leaves room for the non-client work that keeps the company running, and a consultant at 74% is on target instead of “behind” a company-wide 80%.
Utilization rate is not capacity utilization
Searches for “utilization rate” also return a number from economics: capacity utilization, the share of an economy’s or a factory’s production capacity in use. The idea is similar, but the inputs are machines and output, not people and hours. In a service business, utilization rate means the people version: recorded client hours against available hours.
The closest neighbour is billable utilization, covered above, which counts only the hours that end up on an invoice. When someone quotes “utilization”, ask which of the three they mean.
How to measure it without fooling yourself
- Write the definition down. One paragraph: what counts as available, what counts as client work, whether unbilled client work is included.
- Record all time, not only billable time. A team that records only client hours cannot produce a denominator, and the number becomes whatever the spreadsheet assumes.
- Look at the distribution, not the average. Per person, per week. That is where the overloaded designer and the underused developer show up.
- Read it next to margin. Utilization tells you how much of the week reached clients; margin tells you whether that week was worth having.
- Compare with yourself. Your definition, your trend, quarter over quarter. Somebody else’s 78% is a number without a method.
Where PLYNTUM fits
time tracking keeps recorded hours attached to the project they belong to, and internal work stays visible instead of disappearing. people and workload shows committed work per person for the weeks ahead, which is the distribution the average hides. Read together with finance and costs, the week’s hours and the week’s margin sit on the same records.
The free business scan asks how much of your team’s recorded time is linked to a project — the question underneath every utilization figure.
To run the numbers for your own team, use the free utilization rate calculator: it shows your rate, the billable hours a target needs and what the gap is worth.
Utilization is one of the numbers PSA software is built to report; see how PLYNTUM plans it in resource management and capacity planning.
To plan the hours ahead instead of measuring them afterwards, read capacity planning for service teams. For the hours themselves, see billable hours.
