Resource utilization is the percentage of a person's available time that is spent doing work, calculated as time worked divided by time available. If someone has 40 available hours in a week and logs 32 hours against projects, their utilization is 80 percent. It is the fastest read on whether a team is busy, idle, or overloaded, and at the portfolio level it tells you whether capacity is going to the work that matters.
The metric is simple to compute and easy to misuse. Push it toward 100 percent and you remove all the slack a team needs to absorb variation, which is how portfolios end up late everywhere at once. This page gives the formula, honest target ranges, the billable versus productive distinction, and the difference between utilization, capacity, and allocation, which get confused constantly.
Key takeaways
- Resource utilization = time worked divided by time available, expressed as a percentage.
- Higher is not better past a point. Sustained utilization above roughly 85 percent removes the slack teams need and makes delays contagious across the portfolio.
- Billable utilization counts only client chargeable time; productive utilization counts all useful work. They answer different questions.
- Utilization is a rate, capacity is a supply, and allocation is a plan. Confusing them leads to bad staffing decisions.
- You improve utilization by fixing the causes of idle and wasted time, not by loading people to 100 percent.
What is resource utilization?
Resource utilization is a ratio that shows how much of someone's available working time is actually used on work. It is usually measured per person, per team, or per role, over a week, month, or quarter, and reported as a percentage. Higher utilization means less idle time; very high utilization means no buffer at all.
It matters because people are the constraint in most portfolios. Money can be moved faster than skilled people can be hired, so knowing how fully your existing people are used, and on what, is the difference between a realistic plan and a wish. Utilization is the read on that. It feeds directly into resource and capacity planning, where the question becomes whether the portfolio's demand fits the supply of people you have.
How do you calculate resource utilization?
Divide the time a person spent working by the time they had available, then multiply by 100. The formula is: utilization = (hours worked / hours available) x 100. The only judgment call is what counts in each number, which is why two teams can report very different utilization from the same reality.
| Person | Available hours | Hours worked | Utilization |
|---|---|---|---|
| Analyst A | 40 | 36 | 90% |
| Analyst B | 40 | 30 | 75% |
| Analyst C | 32 (part time) | 24 | 75% |
Available hours should reflect reality, not a theoretical 40. Subtract holidays, planned leave, and known non project commitments first, or you will understate utilization and think people are idle when they are not. The figures above are illustrative; use your own timesheet or capacity data to compute real rates.
What is a good resource utilization rate?
For most delivery roles a healthy target sits around 70 to 85 percent, leaving room for meetings, admin, learning, and the inevitable variation in project work. Client billable roles in consulting are often targeted higher, in the 75 to 90 percent range, while roles that include heavy planning, management, or support are deliberately lower. There is no single correct number; it depends on the role and how much unplanned work it must absorb.
| Role type | Typical healthy range | Why |
|---|---|---|
| Billable consultant or contractor | 75 to 90% | Chargeable time is the business model. |
| Project delivery staff | 70 to 85% | Needs slack for variation and coordination. |
| Roles with management or support duties | 50 to 70% | Much useful time is not project logged. |
Treat sustained utilization above roughly 85 percent as a warning, not a win. A portfolio run at full utilization has no buffer, so a single slipped task cascades because there is no one free to catch it. This is the same logic behind resource leveling and smoothing: deliberately leaving headroom makes the whole system more reliable, not less productive.
What is the difference between billable and productive utilization?
Billable utilization counts only the hours a client can be charged for, so internal work, training, and business development all lower it. Productive utilization counts every hour spent on useful work, billable or not. A consultant coaching a colleague scores zero on billable utilization and full marks on productive utilization for the same hour. Use billable utilization to manage a services P and L, and productive utilization to understand whether people are genuinely occupied.
Reporting one when you mean the other causes real damage. Managing an internal PMO to a billable style target punishes exactly the planning and improvement work that keeps a portfolio healthy, because none of it is chargeable.
Resource utilization vs capacity vs allocation: what is the difference?
These three get used interchangeably and mean different things. Utilization is a rate that looks backward at how fully time was used. Capacity is a supply that looks at how much work people could take. Allocation is a plan that assigns specific people to specific work ahead of time. You need all three, and mixing them up produces bad decisions.
| Term | What it is | Question it answers |
|---|---|---|
| Utilization | A rate (time used / time available) | How busy were they? |
| Capacity | A supply of available time or skills | How much can they take on? |
| Allocation | A plan assigning people to work | Who is doing what, and when? |
Capacity is covered in depth in the capacity planning template, and the mechanics of assigning people to work are covered in resource allocation in project management. Utilization is the feedback loop that tells you whether your capacity assumptions and allocations were right.
How do you improve resource utilization?
Improve utilization by removing the causes of wasted and idle time, not by piling on more work. Low utilization usually means one of a few things: too much time lost to context switching across projects, unclear priorities that leave people waiting, or a mismatch between the skills you have and the work in the pipeline. Each has a different fix.
- Reduce the number of projects a person is split across. Splitting one person over five initiatives loses hours to switching that never show up on any timesheet.
- Fix the intake and prioritization queue so people are not idle waiting for decisions. A clear prioritized portfolio keeps the next piece of work ready.
- Match skills to demand. Utilization stays low when the available people cannot do the work that is waiting.
- Protect a planned buffer instead of chasing 100 percent. Aiming for the high nineties guarantees burnout and hidden delay.
How is resource utilization used at the portfolio level?
Rolled up across teams, utilization tells portfolio leaders whether the organization has the capacity to take on more work or is already at its limit. If most teams are running in the high eighties, approving another initiative will not add output; it will just make everything late. That roll up is one of the standard measures in portfolio KPIs and metrics and a recurring line in PMO reporting and portfolio dashboards.
Frequently asked questions
What is the resource utilization formula?
Utilization equals hours worked divided by hours available, multiplied by 100. If a person has 40 available hours and works 34 on projects, utilization is 85 percent. The key is defining available hours realistically by first removing leave, holidays, and known non project time.
What is a good resource utilization rate?
For most delivery roles, 70 to 85 percent is healthy, leaving slack for variation and coordination. Billable consulting roles are often targeted at 75 to 90 percent. Sustained rates above about 85 percent are a warning sign because they remove the buffer a portfolio needs to stay reliable.
What is the difference between resource utilization and resource capacity?
Utilization is a rate that measures how much of available time was used. Capacity is the supply of time or skills a person or team can offer. Utilization looks backward at what happened; capacity looks forward at what is possible. You plan with capacity and check yourself with utilization.
Can resource utilization be too high?
Yes. Utilization above roughly 85 to 90 percent sustained means there is no slack to absorb variation, so a single delay cascades and there is no one free to recover it. High utilization also drives burnout. A deliberately planned buffer makes the whole portfolio more reliable, not less efficient.
What is the difference between utilization and billable utilization?
Plain utilization counts all work against available time. Billable utilization counts only client chargeable hours, so internal and improvement work lowers it. Use billable utilization to run a services business and total or productive utilization to understand whether people are genuinely occupied.