Resource utilization: the formula and fair targets

Meet Monica, who leads a consulting team at a fictional IT services firm. Arjun and Sara are two of her consultants. Their weeks are made up, but they will feel familiar. We'll follow Monica as she builds her first utilization report, and we'll check what Arjun and Sara see from their side.

What is resource utilization?

Resource utilization is the share of your available time or capacity that people spend on real work. IBM calls it a KPI that measures performance and effort over an amount of available time. It answers one plain question: how much of what your people could do is going into work?

People also say utilization rate or capacity use. The words can describe machines and servers too, but this guide is about people and teams, counted in hours.

Leadership asks Monica whether her team is used well. She has a list of hours worked, but no number she can defend in a meeting.

In short: utilization turns "are we busy?" into a number you can question.

What is the resource utilization formula?

Divide the hours spent on work by the hours available, then show the result as a share. Float writes it as billable hours divided by available hours, times 100. Available hours are working hours minus time off and holidays. Use the same period for both numbers.

These numbers are made up to show the steps. They are not a benchmark. IBM adds that the result can be shown in hours, days or percentage, so pick one and keep it.

In this made-up month, three quarters of the available time went into work, and a quarter was open. That is a description, not a grade.

Two rates share the name, and they answer different questions.

Billable utilizationcounts hours charged to clients.

• Shows how much capacity earns revenue
• Ignores internal projects and admin

Total utilizationcounts all hours spent on work.

• Shows workload
• Does not show what earns revenue

Some teams also track forecast utilization, which ProSymmetry calculates as planned hours divided by capacity hours. Pick one rate for each report and label it every time.

Monica sends finance her team's report. Finance reads the number as billable utilization and builds a revenue plan on it. It was the total rate, so the plan comes out too high.

In short: a number without its label starts arguments, so name the rate each time.

How is utilization different from allocation and capacity?

These three words get mixed up, and each answers a different question. ProSymmetry describes allocation as assigning work, which happens before the work is done, while utilization looks at work after it is assigned and completed. Keep one meaning per word, and say which one you mean.

Sara is on several projects, so her allocation looks full on the plan. Her time records show that some of those projects have barely started.

An employee utilization rate is the same idea for one person. Resource utilization usually covers a team, a project or a pool of people.

In short: the plan shows intent, and utilization shows what happened.

What is a good utilization rate?

There is no single good rate, because the right level depends on the work. Float says the ideal rate depends on the context of a project and differs across teams and businesses. A fair target leaves room for meetings and surprises, and you set it from your own history.

Deltek, which sponsors the report, says SPI considers 75% the optimal level for billable work. Treat that as one view of professional services, not a rule for your team. Float warns that a percentage means nothing without context: one person at 100% can carry a light load while another at 50% is overloaded.

Some guides print a healthy range for every team. We found no primary source for one, so this guide leaves it out.

Monica's firm copies the benchmark into next year's plan as every consultant's target. By spring, projects are slipping, because the target left no room for sick days, training or urgent requests.

In short: a benchmark starts the conversation; it never ends it.

Why does 100% utilization hurt?

A team booked to the last hour has no room for the unexpected, so every new request waits in line. Queueing math says waits grow faster and faster as utilization climbs. The more uneven the work, the sooner it starts. A full calendar is not the same as quick delivery.

Linda Green of Columbia Business School writes that average delays increase at an increasing rate as utilization rises, and that the average delay approaches infinity as utilization approaches one, assuming the queue has no limit. She adds that the greater the variability in service time, the longer the delays at any given utilization level.

Float argues the other way, with a catch. It says 100% in its software should mean all of a person's time is accounted for, including meetings and training, not 100% project work. So define what 100% means before anyone argues about it.

IBM says overutilization can lead to employee burnout, and underutilization can lead to unplanned delays. The American Psychological Association's 2026 Work in America survey found that more workers felt tense or stressed during the workday than in 2025. It doesn't link that to how busy calendars are, but it is a reason to leave some slack.

Arjun is booked solid. When a client sends an urgent request, it waits behind everything else, and nobody can say who should drop what.

In short: slack is what lets a team respond, so define 100% before you chase it or ban it.

How do you track and report utilization?

A resource utilization report compares hours used with hours available for each person and team. Build it weekly from time records, pick the views that match the questions your managers ask, and review it with the people involved. Numbers read alone invite wrong guesses.

Green notes that determining bed capacity based on occupancy levels can result in very long waiting times for beds. For IT services teams, We360.ai has posts on reducing bench time and on workload analysis.

Monica's firm runs consulting work and a support desk. She watches a billable view for consulting and a workload view for support, because one number can't serve both.

In short: choose the measure that fits the work, then compare a team only with itself.

How do you improve utilization without burning people out?

A resource utilization plan improves the number by matching work to people, not by adding hours. Fill idle gaps by planning ahead, move work off overloaded people, and protect time for meetings and admin. Change one thing at a time, and watch the rate and the signs of overload together.

• Employersplan work two to four weeks ahead, so gaps show early.move work from overloaded people to people with spare time.leave room in every plan for meetings and surprises.
• Employeeslog your time daily and flag overload early.ask what your utilization number includes.

Sara has been over her usual hours for weeks, and she hasn't said a word. Monica spots it in the weekly report. She opens the talk by asking what is going on, not by quoting the number.

In short: ask first, then move the work.

Do utilization targets change what employers owe for hours worked?

No. A utilization rate is a planning number, and it does not replace time records. The US Department of Labor says covered employers must keep accurate records of hours worked each day and each workweek for non-exempt employees. Build the report from those records, not instead of them.

The same fact sheet says employers may use any timekeeping method if it is complete and accurate. We read it on October 21, 2026, and it was last revised in July 2008. This is general information, not legal advice. Whether someone is exempt, and what your state adds, can change the answer, so check with a lawyer. This guide covers US law only.

Arjun is paid by the hour. He works late to reach a billable target, and some of those hours go unlogged because his report only has billable rows. His rate looks healthy while his real week was longer.

In short: let the time record stand first, and let the utilization rate be built from it.

Which tools and templates help?

A resource utilization tool does one of three jobs: it records hours, plans who is booked where, or compares plan with actual. A spreadsheet template is a fine start. Pick the tool that answers your next question, and test it with one team before you roll it out.

We360.ai is our product, and it belongs in the timesheet and analytics groups. Its docs describe timesheets where employees log work by day, mark each entry billable or non-billable and submit it for manager review. A Capacity Planning module, part of its Advanced Analytics suite, compares planned with actual workload.

What it collectsfor utilization views.

• Timesheet rows employees log themselves
• Keyboard and mouse activity, not what was typed
• Screenshots at intervals admins set

Where you control itas an admin.

• Screenshots can be switched off for a team or person
• Blur level and manager downloads are adjustable
• Managers approve, reject or reopen timesheets

What it never collectsfrom employees.

• Individual typed characters
• Webcam feeds

Employees can see their own analytics, as the docs' privacy page explains. One honest limit: the docs pages we read don't describe an automatic utilization percentage, a matrix or a template, so build the layout below in a spreadsheet first. See also the timesheet feature and the capacity planning solution.

Monica builds this sheet and runs it for a month with her own team. She tells them what goes in and who sees it. Sara asks whether the sheet will be used in her review, and Monica doesn't know yet. She says so.

In short: start with the layout and the rules, then pick the tool. See the wider workforce analytics solution when the sheet stops being enough.

FAQ