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.
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.
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.