Understanding utilisation for service-based teams

Ask ten people at a service business to explain their utilisation rate and you will likely get ten different answers. Some will quote a number without being entirely sure how it was calculated. Others will admit the data comes from timesheets that are weeks out of date. A few will say they track it in a spreadsheet but have not opened it since last quarter.

That is not a criticism. Utilisation is genuinely more complicated than it first appears, and for teams focused on delivering client work, it can feel like an afterthought. The problem is that ignoring it tends to be expensive, in ways that show up quietly: projects that run over budget, people quietly running at capacity without anyone noticing, or revenue that does not quite match the hours being worked.

This article explains what utilisation actually means in a service-based business, how to calculate it and how to use it practically.

What utilisation means in a service-based business 

Utilisation measures how much of a team's available working time is spent on productive work. Billable utilisation looks specifically at the proportion spent on work that can be charged to clients. In a service business, where the primary thing being sold is people's time and expertise, that proportion has a direct relationship to revenue and margin.

If your team has 400 available hours in a week and 280 of those hours end up on client work, your utilisation rate for the week is 70%. The other 30% has gone somewhere: internal meetings, business development, admin, training, non-client work, or simply time that was not captured.

The question is not whether that 30% should exist. Some of it always will, and some of it is necessary. The question is whether you know where it is going and whether it is higher than it needs to be.

Billable utilisation vs total utilisation 

These two terms are related but not the same, and conflating them creates confusion.

Billable utilisation looks only at time charged directly to a client in a way that generates revenue. It excludes internal meetings, internal projects, proposals, training and anything else that does not appear on an invoice.

Total utilisation (sometimes called resource utilisation) looks at all productive work, including internal time. A consultant might be at 90% total utilisation but only 65% billable utilisation if a significant chunk of their week is going to internal meetings, pitches and non-client work.

Both metrics are useful, but for profitability purposes, billable utilisation is usually the number that matters most. A team can be extremely busy without generating much revenue, and understanding the gap between busyness and billability is one of the most useful things utilisation data can tell you.

Why utilisation matters

For service-based teams, utilisation sits at the intersection of capacity, profitability and wellbeing. It affects all three.

On the commercial side, billable hours that go uncaptured are revenue that is permanently lost. Unlike product businesses, service businesses cannot recover unused time. If a consultant had eight available hours on Tuesday and spent six of them on client work but only logged four, two billable hours may go unrecorded and therefore risk never being invoiced. Multiply that across a team of 20 people over a year and the numbers become significant.

On the planning side, utilisation data tells you whether you have capacity to take on new work or whether you are already close to your limits. Without it, sales and operations tend to operate in different directions, with sales promising delivery capacity that the team does not actually have.

How to calculate utilisation rate

The most common formula is:

Utilisation rate = billable hours / available working hours x 100

So if a consultant works a 40-hour week and logs 32 hours of billable client work, their billable utilisation rate is 80%.

In practice, the exact formula varies depending on what a business treats as "available hours." Some firms exclude leave, public holidays and training days from the denominator, making the resulting rate look higher. Others include everything, which gives a truer picture of how time is distributed across the business.

Neither approach is wrong as long as it is consistent. The more important thing is that everyone in the business understands what the number means and how it was calculated, so you are all interpreting the same data.

A few variations worth being aware of:

• Some businesses track billable and non-billable client work separately, since non-billable client time (scope creep, unbilled courtesy calls, rework) still costs time without generating revenue.
• Some track utilisation by person, by team, by practice area and at a whole-of-business level, since each view tells you something different.
• Targets often vary by role. Senior leaders and business development-heavy staff will naturally have lower billable utilisation than delivery consultants. Setting a single target across the whole business is rarely useful.

What good utilisation looks like

There is no universal number that works for every service business. The right target depends on the business model, the role mix, the kind of work being delivered and how "billable" is defined.

That said, many professional services and consulting firms use 70–80% as a practical reference point for healthy billable utilisation, though the right target depends on role mix, pricing model and how the business defines billable time. Sustained utilisation below that range may indicate excess capacity, a weaker pipeline or more non-billable activity than expected. Above it, particularly at 85-90% sustained, there is a real risk of quality issues and staff strain.

What matters more than hitting a specific number is understanding the trend. If utilisation has been sitting at 75% for three months and then drops to 58%, something has changed and it is worth finding out what.

Common utilisation problems

The team that looks busy but bills lightly. A team can be fully occupied with meetings, internal projects, escalations and client calls that never make it onto an invoice. On the surface, everyone seems stretched. In the data, billable utilisation is low. The fix usually involves auditing where non-billable time is going and making clearer decisions about what gets prioritised.

Uncaptured scope creep. A consultant completes additional work that falls outside the original project scope. They do not log it separately or raise it for billing. That time disappears. In isolation it is small. At scale, across a team, across multiple projects, it is a steady leak that compounds over time.

Imbalanced distribution. Some team members are consistently at or beyond capacity while others have room. The work is not well-matched to the people, often because the team lead is allocating from memory rather than data.

Why utilisation data is often unreliable

Utilisation data is only as good as the timesheet data behind it. This is the point where many businesses quietly lose confidence in their numbers.

If people are logging time weekly rather than daily, entries become estimates. If the timesheet tool is friction-heavy, people log less than they should. If there is no clear distinction between billable and non-billable work in the system, data gets assigned inconsistently. And if the team does not trust that the data will be used fairly, they may be selective about what they record.

None of this is unusual. It is simply what happens when time tracking is treated as an administrative task rather than a business intelligence tool. Getting the data right requires that the tool itself be easy to use and that people understand what the data is used for.

How utilisation connects to profitability

In a service business, revenue is primarily a function of the hours billed at the rates charged. Utilisation is the multiplier on that equation.

If you raise rates without improving utilisation, the benefit is limited by the number of hours being billed. If you improve utilisation without reviewing rates, you work more hours for the same margin. The two levers work together.

More practically: a team that understands its utilisation rate can make smarter decisions about when to take on new work, how to price it and whether existing workloads need to be restructured before new projects can be absorbed cleanly.

How utilisation connects to team wellbeing

High billable utilisation is not the same as a healthy, sustainable workplace. There is a range where utilisation supports both business performance and team wellbeing, and outside that range, problems tend to emerge in both directions.

Sustained high utilisation, particularly above 85-90%, leaves little room for the work that supports quality: thinking time, professional development, peer review, mentoring and recovery. Over time, quality tends to decline and staff tend to leave.

Low utilisation has its own problems. When people feel underutilised or unclear on their purpose, motivation and morale can drop. There is also the question of whether the business can afford to maintain headcount at lower productivity levels for an extended period.

The goal is not to push utilisation as high as possible. It is to understand where it sits, what is driving it and whether the current balance is sustainable.

How to improve utilisation without overloading people

Improving billable utilisation is not simply about working more hours. The more productive approaches tend to focus on where time is going rather than how much of it is being used.

A few practical starting points:

Audit non-billable time. What is actually happening in that 20-30%? Internal meetings, business development and training are expected. But excessive admin, avoidable rework and poorly defined internal projects all represent time that could be redirected.

Improve timesheet accuracy. Make time entry quick and consistent, and encourage people to log time while the work is still fresh. Better inputs produce more reliable utilisation data.

Match work to the right people. Mismatched allocations mean work takes longer than it should. A senior consultant doing work that a junior consultant could handle is a utilisation problem as much as a cost problem.

Build pipeline visibility. Knowing what is coming in the next four to eight weeks means you can balance project demand against available capacity before it becomes a problem rather than after.

How better tools help

For growing service teams, spreadsheets tend to break down at a certain point. They require constant manual maintenance, they do not connect timesheet data to project data and they give a picture of where things were rather than where things are.

Tools like Ponyrider connect timesheets, resourcing and forecasting in one view, helping service teams see current utilisation alongside upcoming capacity. Instead of relying on manually updated spreadsheets, managers can identify workload imbalances and capacity gaps while there is still time to act.

The goal is better visibility, not a higher number

Utilisation is one of the most practical measures available to a service business. It is not a complicated concept, but it requires consistent data to be meaningful, and it requires the right context to be interpreted correctly.

The most common mistake is treating a utilisation rate as a target to push rather than a signal to understand. The goal is not 80% because 80% sounds right. The goal is to understand what your current rate means, what is driving it, and whether the mix of billable and non-billable work across your team is sustainable and commercially sound.

Start there, and the number becomes genuinely useful.

Ponyrider gives service-based teams real-time visibility across utilisation, capacity and future workload. Explore the platform with a 30-day free trial, with no credit card required.