What is your tech team actually doing with their time and how much of it are you billing for?
Most MSP owners have a rough sense of whether their technicians are busy. What they don’t have is a precise, weekly measurement of how many available labor hours are converting into billable work. That gap between “feels busy” and “actually billing” is where one of the most significant and recoverable revenue leaks in the MSP business model lives.
Utilization is not a complex metric. The math takes ten seconds. But managing it understanding what drives it down, who owns it week to week, and what levers actually move the number is where the operational discipline lives. This article breaks down what 75% utilization means in practice, why it’s the right target, and what it takes to get there and stay there.
Utilization Defined: The Math and What It Actually Means
Billable utilization is the percentage of a technician’s available working hours that are applied to billable work, whether against a managed service agreement, a break/fix ticket, a project, or any other client-facing deliverable.
The formula is straightforward:
Billable Utilization = Billable Hours Logged ÷ Total Available Hours
If a technician works 160 hours in a month and logs 120 hours of billable time, their utilization is 75%.
The “total available hours” denominator matters. It should reflect actual working hours — typically 8 hours per day, minus approved PTO and company holidays. It should not be inflated by assuming technicians are productive for every minute of every scheduled shift, and it should not be artificially deflated by excluding reasonable administrative time.
At 75% utilization, a full-time technician is delivering approximately 6 billable hours per 8-hour day. The remaining 25% covers internal meetings, training, administrative tasks, travel time, and the natural rhythm of a workday. It’s a realistic, sustainable, high-performance standard not a theoretical ceiling.
Industry Benchmarks: The Zone of Healthy Utilization
Not all utilization levels are created equal, and the goal isn’t simply to maximize the number.
Below 55%: Active Revenue Leak A technician running at 55% utilization is billing for just over four hours of an eight-hour day. At a blended billing rate of $125/hour, that’s roughly 24 hours of unbilled labor per month, per technician approximately $3,000 per tech per month in potential revenue that isn’t being captured. Across a five-person technical team, that’s $180,000 per year in recoverable billing that’s currently invisible.
The cause is almost never that the work isn’t there. It’s that the work isn’t being logged, scheduled, or assigned efficiently enough to show up in the utilization number.
55%–70%: Operational Inefficiency This is where most MSPs without structured utilization management end up. The team is busy everyone feels busy but a meaningful portion of available hours is being absorbed by non-billable activity, unlogged time, and scheduling gaps. Owners in this zone often believe their service team is running well because client complaints are manageable. What they don’t see is the margin sitting uncaptured in the gap between where utilization is and where it should be.
70%–80%: The Target Zone This range represents sustainable high performance. Technicians are consistently applying the majority of their time to client-facing work. There’s enough buffer for training, internal projects, and the inevitable unproductive time that comes with any service role. The team can absorb workload fluctuations without burning out, and the utilization data is reliable enough to support meaningful management decisions.
Above 85%: Burnout Territory Sustained utilization above 85% signals one of two things: either technicians are under-logging time and real utilization is lower than it appears, or the team is genuinely overextended. Both scenarios are dangerous. Overextended technicians make more mistakes, deliver worse client experiences, and leave — which is considerably more expensive than the short-term billing gains from running hot.
The 3 Drivers of Low Utilization
Understanding why utilization is low is prerequisite to fixing it. The cause is almost never technician laziness or insufficient work. It’s almost always one of three structural problems:
1. Poor Scheduling and Assignment When ticket assignment is ad hoc whoever grabs it first, whoever’s nearby, whoever the client asks for available capacity doesn’t get matched to available work efficiently. One technician is buried while another has three hours with nothing assigned. The queue has work; the scheduler doesn’t have visibility into the mismatch. Hours go unbilled not because work was absent but because it was never optimally assigned.
2. Unlogged Time A technician who resolves a 45-minute issue and never logs the time has just given that service away for free. This happens constantly not out of bad intent, but out of the natural momentum of a busy service day. The ticket gets closed, the tech moves to the next call, and the time entry never happens. At the individual ticket level, it’s minor. Aggregated across a team and a month, it represents a meaningful portion of missing utilization.
3. Non-Billable Busywork Internal meetings with no defined agenda, ad hoc requests from ownership, repetitive administrative tasks that could be systematized, these absorb technician time without generating client value. When non-billable overhead isn’t tracked and managed, it grows by default. No one decides to have too many internal meetings. It just happens when nobody is watching the utilization impact.
How a Service Manager Monitors and Moves Utilization Week by Week
Utilization improvement isn’t a one-time initiative. It’s a weekly discipline and it belongs to the MSP Service Manager.
The Service Manager’s utilization workflow runs on a consistent cycle. Weekly, they pull utilization data by technician, identify who is running below target, and investigate the cause before it compounds into a monthly shortfall. Is the low number driven by unlogged time? By scheduling gaps? By a high volume of non-billable internal work this week? The answer determines the response.
Where unlogged time is the driver, the Service Manager takes it to the individual technician in their next 1:1 not as a disciplinary conversation, but as a coaching one. “You had 14 hours unaccounted for last week. Let’s talk about what was happening and how we capture it going forward.” Done consistently and without blame, this conversation changes behavior over time.
Where scheduling is the driver, the Service Manager coordinates with the dispatcher to tighten assignment practices and close the gap between available capacity and active work. Where non-billable overhead is the driver, the Service Manager reviews what internal time is consuming and works with ownership to reduce or restructure it.
The Service Manager also tracks utilization trends, not just the current week’s number but the direction of travel over the quarter. A technician whose utilization has drifted from 74% to 61% over six weeks has a story behind that number. Finding and addressing that story early is considerably less expensive than finding it in an annual performance review.
Timesheet Review: The Accountability Lever Most MSPs Aren’t Pulling
Every MSP knows time entry matters. Very few have someone formally reviewing it on a regular cadence and holding technicians accountable for gaps.
The Service Manager reviews timesheet compliance weekly not to police technicians but to catch data loss before it becomes permanent. Time that isn’t logged within 24–48 hours of the work being done is time that’s increasingly unlikely to be recovered. Memory fades, tickets close, and the billing window passes.
Weekly timesheet review creates a consistent accountability loop. Technicians know their time entries will be reviewed. That knowledge alone changes behavior not through fear but through the natural human tendency to be more careful when someone is paying attention. The standard becomes real because it’s consistently enforced, and consistently enforced standards produce consistently better data.
Scheduling as a Utilization Strategy: How Dispatchers and Service Managers Coordinate
Utilization is jointly owned by the dispatcher and the Service Manager and the coordination between those two roles is what allows consistent performance at the 75% target.
The dispatcher’s contribution is real-time: matching available technician hours to available tickets, preventing gaps in productive assignment, and ensuring the queue is structured so no technician runs dry on assigned work during peak availability hours. A dispatcher operating with full visibility into each technician’s current workload and the day’s incoming volume can front-load assignment to protect utilization from morning through mid-afternoon the window where most billable hours are generated.
The Service Manager’s contribution is structural: identifying systemic scheduling patterns that consistently produce utilization gaps, adjusting team capacity against forecasted ticket volume, and flagging to ownership when the team is consistently over- or under-resourced relative to demand. The dispatcher solves today’s assignment problem. The Service Manager solves next month’s capacity problem.
Together, these two functions operational dispatch and strategic service management produce utilization performance that neither role could achieve independently. The 75% target isn’t aspirational in MSPs where both roles are filled and coordinated. It’s the expected floor.
What the BMK Ops Dashboard Shows Ownership Every Month
When an MSP engages BMK Ops for Service Manager services, ownership receives a monthly service department report that includes utilization data at both the team and individual level.
The report shows: average billable utilization by technician for the month, utilization trend versus the prior two months, identification of technicians running materially above or below target, and the Service Manager’s analysis of what’s driving any significant variance. It’s not a spreadsheet dump, it’s an interpreted view of the data, with the Service Manager’s observations and the actions already in progress to address any gaps.
Most MSP owners receiving this report for the first time discover that their actual utilization is 8–15 percentage points lower than their intuition suggested. The team felt busy. The data tells a more precise story and a more actionable one.
The Revenue Is Already in Your Team. You Just Have to Capture It.
The technicians are already on payroll. The hours are already being worked. The question is what percentage of those hours are being captured as billable value to your business and whether anyone is actively managing that percentage week over week.
At a five-person technical team with an average billing rate of $125/hour, the difference between 58% utilization and 75% utilization is approximately $212,000 in annualized billable revenue. That number doesn’t require hiring anyone, raising rates, or acquiring new clients. It requires knowing where the hours are going and having the right people in place to manage them.
Book a free consultation with the BMK Ops team to see what your service team’s current utilization picture looks like and what a Service Manager with 10+ years of MSP experience would do with it starting in month one.
BMK Ops provides outsourced bookkeeping, dispatcher, and service manager services built exclusively for MSPs. Based in Washington, DC serving MSPs across the United States.
