Team capacity utilisation

Team capacity utilization is the percentage of a team available working hours that is spent on planned, productive work over a given period. If a team of five has 800 available hours in a month and logs 640 hours against planned work, utilisation is 80 per cent. It is a measure of how fully a team capacity is being used, and unlike a raw output count, it accounts for the time the team actually had to spend.

The metric matters because both extremes are expensive. Low utilisation means available hours are going to waste, often on idle time, context switching, or work that was never planned. Very high utilisation means the team is running with no slack, so any sickness, urgent request, or estimation miss tips straight into missed commitments and overtime. The healthy zone sits below full, because a team booked to one hundred per cent has no capacity to absorb the unexpected, and the unexpected always arrives.

Utilisation is most useful read as a trend and a distribution, not a single headline. A team at 85 per cent on average can hide one person at 110 per cent and another at 60 per cent. The average looks fine while the load is badly balanced, which is exactly the situation a flat number conceals.

The calculation divides the hours spent on planned work by the total available hours in the period, then multiplies by 100. The judgement sits in how you define each input, because what counts as available and what counts as planned work shifts the number considerably. The components below are what you need to settle before the figure is reliable.

1. 1

   Hours spent on planned work

   Time logged against tasks that were planned and productive. Decide whether unplanned but valuable work, such as urgent fixes, counts. The most useful definition includes real work and excludes idle or admin time.

2. 2

   Total available hours

   Working hours genuinely available across the team after subtracting leave, holidays, and known overhead. Using gross contracted hours understates every team, so net the predictable non-task time out first.

3. 3

   The team boundary

   Who is counted in the team. Be consistent about part-time members, contractors, and people split across teams, since changing the population changes the denominator and breaks the trend.

4. 4

   Measurement window

   The period over which you measure, typically a sprint, month, or quarter. A consistent window is what makes utilisation comparable over time, so fix it once and hold it.

A worked example. A team of four works a standard month of 160 hours each, giving 640 gross hours. Subtracting 80 hours of leave and 60 hours of recurring meetings and admin leaves 500 available hours. The team logs 410 hours against planned work. Utilisation is (410 / 500) x 100, which is 82 per cent. Had you used the gross 640 hours as the denominator, the same effort would read 64 per cent, which would wrongly suggest a third of the capacity was idle.

A metric tree decomposes utilisation into the things that consume a team available hours, then traces each down to a specific cause. This turns a flat percentage into a diagnosis of where capacity is going and why the figure sits where it does.

The first level splits utilisation into planned work delivered, available hours after overhead, unplanned work absorbed, and how evenly the load is spread. Each branch decomposes further. Planned work breaks into throughput and estimation accuracy. Available hours breaks into leave, meeting load, and admin overhead. Unplanned work breaks into urgent requests and rework. Load balance breaks into the spread across individuals and the spread across the period. When utilisation drifts out of the healthy band, the tree tells you whether it is meetings eating the hours, unplanned work crowding out the plan, or load piling onto a few people.

This is the gap between a dashboard and a decision. A dashboard says the team is at 78 per cent. The tree shows that the headline hides one person running at 105 per cent while two sit near 60 per cent, which is a load-balancing decision, not a hiring one.

Utilisation benchmarks depend on the type of work, since predictable delivery teams can run higher than teams handling a stream of unplanned requests. The healthy target is almost never one hundred per cent, because a fully booked team has no room to absorb the unexpected. The bands below give a practical sense of where a team sits when measuring planned work against net available hours.

The figure worth watching is not just the team average but the distribution underneath it. A healthy mean can sit on top of a badly balanced load, with some people overloaded and others idle. The benchmark is a starting point, the decomposition across individuals and over the period is where the answer lives.

Improving utilisation means moving it towards the healthy band, which can mean raising a low figure or easing an overloaded one. The metric tree points at where the capacity is going, and each branch has a concrete lever.

The decomposition decides the lever. If utilisation is low because meetings eat the hours, cutting overhead beats adding tasks. If the average looks fine but one person is drowning, rebalancing beats hiring. Reading the headline alone risks pushing a stretched team harder when the real fix is moving work to the colleague sitting idle.

KPI Tree lets you model this by connecting utilisation to the people and work behind it. Each team and individual carries RACI ownership, so the accountable owner can see their own load against the team picture rather than a single blended number. When utilisation drifts out of the healthy band or one person tips into overload, the metric pushes to the accountable owner so the imbalance is caught before it becomes burnout or a missed commitment, not after the period has closed.

1. 1

   Using gross hours as the denominator

   Measuring planned work against contracted hours before subtracting leave, meetings, and overhead understates every team. Net the predictable non-task time out first so the denominator reflects real available capacity.

2. 2

   Treating one hundred per cent as the goal

   A fully booked team has no slack to absorb the unexpected, so it misses commitments the moment anything slips. The healthy target sits below full on purpose.

3. 3

   Reading the average without the spread

   A healthy team mean can hide one overloaded person and one idle one. The distribution across individuals, not the blended figure, is what tells you whether the load is balanced.

4. 4

   Ignoring unplanned work

   If urgent requests are not counted, a busy team can look underused while it has no spare time at all. Decide how unplanned work is captured so the figure reflects what the team actually does.

5. 5

   Chasing the number instead of the outcome

   Pushing utilisation up by filling every hour can raise the figure while delivery and quality fall. Pair utilisation with a check on whether planned work is actually finishing.