Metric Definition
Utilization
Track from
Resource utilization rate
Resource utilization rate is the proportion of available working time or capacity that is actually spent on productive, value-generating work. It tells you how much of what you are paying for is being used. Watched alone it can mislead, so it is best read alongside the work it produces.
7 min read
What is resource utilization rate?
Resource utilization rate is the proportion of available working time or capacity that is actually spent on productive, value-generating work, expressed as a percentage. If an analyst has 40 available hours in a week and spends 32 of them on client or project work, their utilization rate is 80 percent. The metric turns a vague sense of how busy a team is into a number you can track and compare.
Utilization matters because capacity is the largest cost in most service and operations teams. Idle capacity is money already spent on salaries and tools that produced nothing. Over-full capacity is a different risk, because people with no slack cannot absorb new work, train, or recover. The rate gives you a single comparable number across people, teams and weeks, which is why it sits at the centre of staffing and pricing decisions.
What counts as productive
Resource utilization rate should only count time on work that creates value, such as billable project hours or core delivery. Admin, internal meetings, training and time off belong in available hours, not productive hours. Counting everything as productive pushes the rate towards 100 percent and hides the fact that little real output is being created.
How to calculate resource utilization rate
The core formula divides productive hours by total available hours over the same period, then multiplies by 100. The hard part is not the arithmetic, it is deciding what goes in each input. Be explicit about whether available hours mean contracted hours, hours net of holiday, or some target capacity, because the same team can show very different rates depending on that choice.
Work the example through. A consultant is available for 160 hours in a month. They log 120 hours against client projects and 40 hours on internal work and admin. Their resource utilization rate is 120 divided by 160, which is 75 percent. If you instead measured against a 140-hour target capacity, the same 120 hours would read as 86 percent. Pick one definition and apply it consistently.
- 1
Define the period
Choose a consistent window such as a week, sprint or month so rates compare like for like.
- 2
Count productive hours
Sum the time logged against billable or value-generating work in that period.
- 3
Count total available hours
Sum the working capacity available, deciding upfront whether to subtract holiday and planned leave.
- 4
Divide and express as a percentage
Divide productive hours by available hours and multiply by 100 to get the rate.
Resource utilization rate in a metric tree
A single utilization number tells you the rate moved but not why. A metric tree decomposes resource utilization rate into the drivers beneath it, so a dip becomes a specific cause rather than a vague worry. Utilization rises or falls because of the work that comes in, the capacity available to do it, and how cleanly that work is scheduled against people.
The tree below breaks the rate into demand, capacity and scheduling. Read top down, it shows that a falling rate could be soft pipeline, unplanned absence, or time lost to bench gaps between projects, and each of those points to a different team and a different fix.
Metric tree insight
When utilization slips, the tree shows whether the cause sits in demand, capacity or scheduling. In KPI Tree you can attach RACI ownership to each branch, so the accountable owner for pipeline coverage and the owner for bench time both see their node move and act on it, rather than the whole leadership team staring at one blended percentage.
Resource utilization rate benchmarks
Healthy utilization depends on the role and the model. Billable consultants and agencies often target the high range, while engineering and product teams deliberately run lower to leave room for unplanned work, learning and quality. Use these as starting ranges, not hard targets, and remember that a rate above 90 percent sustained over many weeks usually signals burnout risk rather than excellence.
| Range | Utilization rate | What it usually means |
|---|---|---|
| Underused | Below 60 percent | Idle capacity, soft demand or bench gaps eroding margin |
| Healthy | 70 to 85 percent | Productive with slack for training, admin and recovery |
| Stretched | 85 to 90 percent | High output but little room to absorb new or urgent work |
| Overloaded | Above 90 percent | Sustained overload, rising burnout and quality risk |
How to improve resource utilization rate
Improving utilization is rarely about asking people to work more. It is about matching capacity to demand more tightly, cutting the gaps between pieces of work, and removing low-value load. The aim is a healthy band, not the highest possible number.
Reduce bench time
Shorten the gaps between project assignments with clearer forward staffing and earlier pipeline visibility.
Match skills to work
Assign people to work that fits their strengths so fewer hours are lost to ramp-up and rework.
Smooth demand peaks
Stagger project starts and sequence intake so capacity is not feast or famine across the team.
Cut low-value load
Trim internal meetings and manual admin so available hours convert into productive hours.
Common mistakes when tracking resource utilization rate
- 1
Chasing 100 percent
Targeting full utilization removes the slack people need for learning and recovery and drives burnout.
- 2
Inconsistent available hours
Mixing contracted hours and target capacity across teams makes rates impossible to compare.
- 3
Counting all time as productive
Logging admin and meetings as productive inflates the rate and hides real idle capacity.
- 4
Reading the rate without output
High utilization on low-value work looks healthy but produces little, so pair it with delivered results.
Related metrics
Cycle time
Process speed
Operations Metrics
Metric Definition
Cycle Time = Process End Time − Process Start Time
Cycle time measures the total elapsed time from the start to the end of a process. It is a fundamental operations metric used in manufacturing, software development, service delivery, and any context where the speed of a process directly affects throughput, cost, and customer satisfaction.
Sprint velocity
Agile planning metric
Operations MetricsMetric Definition
Sprint Velocity = Sum of Story Points Completed in a Sprint
Sprint velocity measures the amount of work a team completes during a sprint, typically expressed in story points, ideal days, or another unit of estimation. It is a planning tool that helps agile teams forecast how much work they can commit to in future sprints based on their historical completion rate. Velocity is one of the most widely used and most frequently misunderstood metrics in agile software development.
Quota attainment
Sales Metrics
Metric Definition
Quota Attainment = (Actual Revenue Closed / Quota Target) × 100
Quota attainment measures the percentage of a sales target that a rep or team achieves in a given period. It is the primary performance metric for sales organisations, connecting individual and team output to revenue goals.
Metric trees for operations teams
Metric Definition
Shows operations teams how to place resource utilization rate within a wider tree of throughput and capacity drivers they own.
Metric decomposition
Metric Definition
Explains how to break resource utilization rate into its underlying capacity and demand components so you can see what is moving it.
Build resource utilization rate as a metric tree
Model utilization as a tree of demand, capacity and scheduling drivers, then put a RACI owner on every branch. When the rate moves, KPI Tree pushes the change to the accountable owner so the right team acts before margin or morale slips.
