What Should Technician Utilization Be?

What Utilization Means Inside an MSP

Technician utilization is the share of a technician's paid hours that is logged against client work. In an MSP that bills a flat monthly fee, most of that time is never invoiced line by line, so the useful definition is time recorded on client tickets, projects and scheduled maintenance in your PSA, whether or not a separate invoice follows. The site's billable utilization entry covers the general term; this answer is about what number an MSP owner should expect from each person.

Utilization matters because labor is the largest cost in delivering managed services. When a technician logs too little client time, the managed services gross margin falls even if every agreement is priced correctly. When a technician logs too much, tickets age, documentation stops, and the best people start looking elsewhere.

There is no single right figure for the whole team. A desk technician, a project engineer and a service manager do different jobs, and one blended target hides the problem you actually have.

A Published Benchmark and What It Assumes

One of the few benchmarks with its working shown comes from Sea-Level Consulting, as reported by Auvik in 2022: a yearly billable percentage of 76% for technicians. The same article points out the catch. Vacation, sick days, holidays and training are all zero percent billable, so to average 76% across the year a technician has to log nearly 83% on the days they actually work.

That gap is why many owners believe their team is underperforming when it is not. If you compare a single busy week against an annual benchmark, the week will look fine. If you compare a year that includes a long vacation and a certification course against a working-day target, it will look poor. Pick one basis, say which one it is on the dashboard, and keep it.

Treat any published figure as a ceiling that a well-run desk can reach, not a floor every person must hit. It assumes clean ticket hygiene, a dispatcher keeping queues full, and technicians who log time as they go. If those are missing, the number measures your process, not your people.

Targets by Role

The table below sets expectations by role rather than by percentage, because the right number depends on how you define billable and how your team is structured. Use it to set the order of targets, then calibrate the actual figures against a year of your own data.

Two roles are often measured wrongly. A vCIO doing quarterly reviews is doing client work even though no ticket was raised, so log that time against the client. And a technician who spends a morning on internal RMM scripting that saves hours across every client is doing valuable work that will never show as utilization. Track it separately so it is not punished.

Why the Number Is Too Low

Low utilization is rarely laziness. When a technician's number drops, look at these causes first:

• Time is worked but not logged. Technicians who reconstruct their day at five o'clock forget the short fixes, and short fixes are most of a desk's volume.
• The queue is empty. You have more technicians than the current client base needs, which is a sales or staffing question, not a performance one. The endpoints per technician KPI shows it quickly.
• Internal work has crept in. Tool migrations, internal IT for your own office and unplanned meetings all pull from the same hours.
• Work is going to the wrong tier. Senior people doing password resets log client time but at a cost the agreement was never priced for.
• Travel is heavy. Field routes that zigzag between clients can consume a large part of the day without any of it being client work.

Fix logging first. Until time is captured as it happens, every other diagnosis is guesswork.

Why the Number Is Too High

A technician who logs client time on nearly every paid hour for months is not a success story. It usually means they are skipping documentation, training, and the internal work that stops the same issue recurring. The result shows up later as rising ticket reopen rate, longer mean time to resolve, and eventually a resignation.

Watch your employee turnover rate and eNPS beside utilization. If utilization climbs while those worsen, you are borrowing against next quarter. Losing an experienced technician costs recruiting time, onboarding time and the client knowledge that walked out with them, which is far more than the margin gained by keeping them fully booked.

Signs the Team Is Overloaded

• Documentation in your PSA or IT documentation tool has not been updated in weeks.
• Training time is always the first thing canceled.
• The same technician is on after-hours rotation more often than planned because nobody else knows the client.
• Tickets are closed quickly and reopened by the client a few days later.

How to Measure It Without Gaming It

A utilization target changes behavior, and not always the way you want. Technicians who are measured on logged client hours will round up, pad short tickets, and avoid internal work. Build the measurement so the honest answer is the easy one:

1. Define billable in writing: which ticket types, projects and client meetings count, and which internal categories do not.
2. Require time entry on the ticket as work is done, and review untimed tickets weekly rather than at month end.
3. Report utilization monthly and trailing twelve months side by side, so a vacation month does not trigger a conversation.
4. Show it with the quality measures next to it: first contact resolution, reopen rate and client satisfaction.
5. Discuss the team number in public and the individual number in one-to-ones.

Utilization is also one input to your effective hourly rate. Low utilization on an agreement that still pays well is less urgent than high utilization on an agreement that pays poorly, so read the two together before acting.

Using Utilization to Decide When to Hire

The most practical use of this metric is timing a hire. When the desk runs at the top of its target range for a sustained period and quality measures start to slip, the team is full. Adding clients past that point means either hiring or accepting worse service.

Hiring too early is the opposite mistake. A new technician takes time to learn your clients and tools, so for a while utilization across the desk will fall, not rise. Plan for that dip, and model the hire with the staffing calculator before you post the role. If you are weighing what the new person should cost, the entry-level technician pay answer covers the salary side, and the service multiple of wages KPI shows whether your pricing supports the payroll you are building.

The goal is a desk that is busy, documented and stable. Utilization tells you whether it is busy; the other measures tell you whether it is the other two.