What Is Technician Utilization? The MSP Metric That Governs Margin
Technician utilization is the single metric that connects your MSP's staffing cost to your margin. Here's the definition, the target, and where owners quietly get it wrong.
George Fassett, Jr. · July 13, 2026
Technician utilization is the percentage of a technician's paid hours spent on billable or SLA-covered client work — not admin, not internal projects, not training, not meetings. It's the single metric that governs whether your service delivery makes money.
The Formula
Utilization = billable or SLA-covered client hours ÷ total paid hours.
Both sides matter. Total paid hours includes PTO, holidays, sick, training — everything you write a check for. Billable / covered hours is what actually generates revenue or draws down MRR.
The Target
- Tier-1 (dispatch / help desk): 65-75% utilization is healthy. Higher usually means missed process time.
- Tier-2 (project / escalation): 70-80% utilization on the recurring book, higher on project engagements.
- Tier-3 (senior engineer): 55-70% — the 30-45% off-utilization is architecture, escalations, mentoring, and vendor management, which is exactly what a senior engineer should be doing.
Where MSP Owners Quietly Get It Wrong
- Counting project work as recurring utilization. A tech billing 80% of the week to a one-time migration is not solving your recurring margin problem.
- Excluding PTO from the denominator. Utilization on "available hours only" flatters the number. Buyers and CFOs recompute on total paid hours.
- No SLA-covered category. If a tech spends four hours on a covered ticket that doesn't generate an invoice, that time still has to count as utilized — otherwise you'll fire techs who are actually earning their keep.
- Managers who don't have a utilization target of their own. If service managers aren't measured on team utilization, nobody owns the number.
How to Fix It Fast
- Rebuild the timekeeping categories so every hour rolls up cleanly: billable, SLA-covered, admin, training, PTO.
- Pull four weeks of data. Compute utilization on total paid hours. Post the number by tech, by team, by week.
- Set a target. Fix the process, not the person, when the number is low.
Utilization discipline is baked into Mebuis Fractional COO and MSP Growth engagements. Book an operator alignment call if the P&L keeps flattening while headcount grows.
Frequently Asked Questions
- What is technician utilization in an MSP?
- Technician utilization is the percentage of a technician's total paid hours spent on billable or SLA-covered client work. It is the single metric that ties MSP staffing cost to margin.
- What is a good technician utilization target?
- Tier-1 dispatch: 65-75%. Tier-2 project and escalation: 70-80% on the recurring book. Tier-3 senior engineer: 55-70%. Lower is expected for senior seats; the 30-45% off-utilization should be architecture, escalation, and vendor management.
- Should PTO count in the utilization denominator?
- Yes. Utilization measured on 'available hours only' flatters the number and hides real staffing cost. Every dollar you write a check for belongs in the denominator — PTO, holiday, training, and sick included.
- How is technician utilization different from billable utilization?
- Billable utilization only counts hours you invoice. Technician utilization on an MSP recurring book must also include SLA-covered work — hours that don't generate a new invoice but draw down MRR you already collect.