How to Calculate Utilization for Better Capacity
A project can look fully staffed on paper and still miss its delivery date because the team’s real capacity was never measured. Knowing how to calculate utilization gives leaders a clearer view of whether people are overloaded, underused, or assigned to work that cannot realistically fit into the schedule.
Utilization is more than a performance metric. Used well, it is a planning signal. It helps operations leaders protect delivery commitments, project managers assign work with confidence, and finance teams understand how much productive capacity the business is actually using.
What utilization measures
Utilization measures the share of a person’s available working time assigned to a specific type of work. In professional services, that often means billable client work. In product, engineering, and internal teams, it may mean time allocated to planned project work, whether or not it generates direct revenue.
The right definition depends on how your organization operates. A consulting firm may focus on billable utilization because it connects directly to revenue. A software company may track planned utilization to see whether product roadmaps and customer commitments exceed available engineering capacity.
The common mistake is treating all scheduled hours as productive capacity without considering the work that makes delivery possible. Meetings, planning, quality reviews, support, training, and time off all affect what a team can reasonably take on.
How to calculate utilization
The basic utilization formula is:
Utilization rate = Productive or assigned hours / Available working hours x 100
For example, assume a designer has 160 working hours in a four-week month. They have 24 hours of approved vacation and 8 hours reserved for internal team meetings. That leaves 128 available hours for planned work.
If the designer is assigned 102 hours to client projects, their utilization is:
102 / 128 x 100 = 79.7% utilization
That percentage is useful because it reflects actual capacity, not an idealized 40-hour workweek. If you divide 102 by 160 instead, you get 63.8%, which may make a healthy workload look underutilized and lead managers to add work the person cannot absorb.
Start with the right available-hours number
Available hours should represent the time a person can genuinely spend on the work you are measuring. Begin with standard work hours, then subtract known non-working time such as vacation, holidays, parental leave, or reduced schedules.
Next, decide whether recurring internal work belongs in the denominator or should be excluded before utilization is calculated. There is no universal answer. If leadership meetings and coaching are expected parts of a manager’s role, excluding them can create an unrealistic expectation that the manager should be scheduled like an individual contributor.
Consistency matters more than forcing every role into one formula. Document the rules your organization uses so utilization comparisons remain meaningful across teams and reporting periods.
Define what counts as productive hours
The numerator must match the decision you want the metric to support. For delivery forecasting, use scheduled project hours. For service profitability, use billable hours. For workforce planning, you may also want to track strategic internal work separately, including product development, sales support, hiring, and process improvement.
Avoid combining all categories into one number if they lead to different actions. A team might have low billable utilization while still being fully committed to a strategic product launch. That is not necessarily a resourcing failure, but it should be visible to the people making budget and delivery decisions.
Planned utilization vs. actual utilization
The most useful organizations track two versions of utilization: planned and actual.
Planned utilization uses scheduled future hours. It shows whether upcoming work fits within available capacity before the team starts. This is the metric that protects project timelines and prevents overbooking.
Actual utilization uses completed or logged hours. It shows how time was really spent and reveals where estimates, schedules, or project scope diverged from reality.
Consider a developer with 120 available hours next month. If 114 hours are assigned across product work and customer requests, planned utilization is 95%. That may look efficient, but it leaves little room for urgent bugs, coordination, or estimation error. If actual utilization later reaches 108%, the issue is not simply that the developer worked hard. It is evidence that the plan lacked enough buffer.
Comparing planned and actual utilization creates a feedback loop. If actual effort regularly exceeds planned hours, investigate estimation quality, project scope, meeting load, or unplanned support work. If actual utilization is consistently far below plan, ask whether project work is being delayed, priorities are changing too often, or schedules are not being maintained.
Set targets that support delivery, not burnout
A 100% utilization target is rarely a practical operating target. It assumes every available hour can be assigned and completed exactly as planned, with no interruptions, context switching, or changes in priority. Fast-moving teams do not work that way.
A healthy target depends on role, work type, and predictability. Client-facing specialists with stable project work may operate effectively at a higher rate than engineering leaders who spend significant time on architecture, mentoring, recruiting, and incident response. Teams with frequent requests from customers or executives need more protected capacity than teams working through a stable backlog.
As a starting point, many teams plan individual contributors below full capacity and reserve time for coordination and unplanned work. Managers and cross-functional leads often need substantially more room. The goal is not to maximize the percentage. The goal is to make commitments the team can keep without relying on sustained overtime.
Utilization should also be reviewed at the team level. One person at 110% and another at 60% may indicate a skills mismatch, unclear ownership, or assignments that have not been rebalanced. An average team utilization of 85% can hide both overload and idle capacity if you only look at the aggregate number.
Common utilization calculation mistakes
The first mistake is using nominal work hours instead of real availability. A calendar month may contain 160 work hours, but that is not the same as 160 hours available for delivery work.
The second is measuring only after the fact. Historical reporting can explain why a deadline slipped, but it cannot prevent the next one. Schedule-based utilization gives teams time to redistribute work before risk becomes a problem.
The third is treating utilization as an individual scorecard. When people feel monitored by a single percentage, they may over-report project time, avoid necessary internal work, or hesitate to help other teams. Use utilization to improve planning decisions, not to reward people for appearing busy.
Finally, do not ignore skills and timing. A team can have 30% unallocated capacity overall and still be unable to start a project because the only qualified person is fully booked for the next six weeks. Capacity is not interchangeable. Good planning shows who is available, what they can do, and when their time opens up.
Turn utilization into a capacity planning habit
The calculation is simple. Keeping it accurate requires a reliable operating rhythm. Review upcoming availability when new work enters the pipeline, update schedules when priorities shift, and look ahead far enough to see bottlenecks before they become delivery escalations.
A centralized scheduling system makes this easier by placing projects, assignments, time off, and role-based capacity in the same view. TeamBuilt helps teams replace disconnected spreadsheets with a real-time view of planned utilization, so resource decisions are based on current availability rather than outdated assumptions.
Use weekly reviews for near-term adjustments and monthly reviews to identify larger patterns. Are specific roles consistently over capacity? Are teams losing too much time to unplanned requests? Are project estimates missing the same kind of work? These questions turn utilization from a static report into a practical management tool.
The most valuable utilization number is the one that helps your team make a better decision before work becomes late. Keep the formula consistent, account for real availability, and leave enough capacity for the work you know will arrive unexpectedly.
