Team utilisation rate

Team utilisation rate is the share of a team total available working hours that goes into productive or billable work. If a team of five people has 1,000 available hours in a month and logs 750 hours against client projects, the team utilisation rate is 75%. It answers a simple question: of the capacity we are paying for, how much is actually doing the work that earns revenue or moves the product forward.

Utilisation matters because payroll is usually the largest cost in a services business, and that cost is fixed whether or not the hours are billable. A consultancy with 60% utilisation is paying for the same people as one at 80% utilisation, but it is converting far less of that spend into client value. Even small swings compound. Lifting average utilisation from 70% to 78% across a 50 person team frees the equivalent of four full-time people without a single new hire.

Utilisation is not a number to maximise to 100%. Time spent on internal training, sales support, recruiting, and recovery is what keeps the team capable and retained over the long run. The goal is a sustainable target that captures most of the available capacity while leaving room for the non-billable work that keeps the business healthy. Read alongside average resolution time and delivery quality, utilisation tells you whether you are working efficiently or simply working people harder.

Team utilisation rate divides the productive hours a team logs by the total hours it had available, then multiplies by 100. The calculation is straightforward, but the result is only as good as the inputs. Define each input precisely and apply the same definition every period, otherwise the trend becomes unreadable.

1. 1

   Productive hours

   The numerator. Hours spent on billable client work or, for internal teams, on directly value-creating delivery. Be explicit about whether activities like client calls, scoping, and revisions count, and apply that rule consistently across everyone on the team.

2. 2

   Total available hours

   The denominator. Contracted working hours for the period, with approved leave and public holidays removed when you want billable efficiency rather than raw capacity utilisation. Keep part-time and contractor hours pro-rated so the base is accurate.

3. 3

   Non-billable hours

   Time spent on internal work that is not waste but is not directly productive either: training, recruiting, sales support, and admin. Tracking this separately explains the gap between 100% and the utilisation you actually hit.

4. 4

   Bench or idle hours

   Available time with no work assigned. This is the recoverable portion of the gap. High bench hours point to a pipeline or resourcing problem rather than a delivery one, and they are usually the fastest lever to move.

A worked example makes the inputs concrete. A team of four has 640 contracted hours in a month. Two people take a week of leave, removing 80 hours, so total available hours are 560. The team logs 420 productive hours, with 90 hours on internal work and 50 hours on the bench. Team utilisation rate is 420 divided by 560, or 75%. The decomposition tells you the rest of the story: most of the missing 25% is non-billable internal work rather than the bench, so that is where you would look first to recover capacity.

A metric tree takes team utilisation rate from a single percentage to a diagnosis. Instead of reporting that utilisation fell three points, the tree shows you whether the cause was more bench time, more non-billable work, or fewer available hours, and which team or role drove the move.

The first level splits the available hours into productive, non-billable, and bench time. Each branch then decomposes into the operational drivers that a specific team controls. Bench time decomposes into pipeline gaps, slow project ramp, and over-hiring ahead of demand. Non-billable time decomposes into training, internal projects, and sales support. Productive time decomposes into the number of active engagements and the average hours each one absorbs.

This structure lets you act with precision. If utilisation drops because the bench grew, the intervention sits with sales and resourcing. If it drops because non-billable work climbed, the question is whether that investment was deliberate. The tree turns a vague efficiency concern into a specific, owned action.

Utilisation benchmarks depend heavily on the type of work and the role. Senior people who sell and lead carry lower targets because their non-billable time creates future revenue, while delivery-focused roles run higher. The ranges below are typical targets for professional services and agency teams rather than hard rules.

Treat the blended average as a health check, not a target every individual must hit. A team running at 90% sustained is often a warning rather than a triumph: there is no buffer for absence, no time for development, and quality tends to slip as people rush. The most resilient teams hold a steady utilisation in the healthy band and protect a deliberate slice of non-billable time.

Improving utilisation is rarely about asking people to bill more hours. It is about closing the gap between available capacity and productive work, which usually means fixing the pipeline, the resourcing process, or the amount of avoidable non-billable work. Start with the branch of the tree that has the largest recoverable gap.

The metric tree approach starts by finding the branch with the biggest gap between current and achievable utilisation, then assigns that branch to the team that can actually move it. KPI Tree lets you connect each branch to its owner using RACI, so the bench branch sits with resourcing and sales, the ramp-up branch with delivery leads, and the non-billable branch with the people who set the development budget. When utilisation moves outside its target band, the change is pushed to the accountable owner rather than buried in a monthly report, and the verified impact loop checks whether the action you took actually moved the number back.

1. 1

   Treating 100% as the goal

   Full utilisation leaves no buffer for absence, development, or selling. Teams pushed to maximum utilisation burn out, lose quality, and stop feeding their own pipeline. Set a sustainable target in the healthy band instead.

2. 2

   Leaving leave in the denominator

   Counting holiday and approved leave as available hours makes a well-run team look underused simply because it took the time it was owed. Decide whether you are measuring billable efficiency or raw capacity and apply that definition consistently.

3. 3

   Reporting only the blended average

   A healthy team average can hide a few people who are badly overloaded and a few who are idle. Without segmenting by person, role, and team, you miss both the burnout risk and the recoverable bench.

4. 4

   Confusing busy with productive

   High logged hours do not always mean high value. If a large share of productive time is rework or avoidable scope creep, utilisation looks healthy while margins suffer. Read utilisation alongside delivery quality and project profitability.

5. 5

   Tracking utilisation without decomposing it

   A single percentage tells you that capacity is or is not being used, but not why. Without splitting the gap into bench, non-billable, and available hours, you cannot tell whether the fix belongs to sales, resourcing, or delivery.