Why It ExistsHow It WorksLeak DetectionPricingOperator Blog Get Diagnosed Free
Home/Operator Blog/Delivery
Delivery

HVAC Technician Efficiency: What to Measure, What's Normal, and What's Costing You Money

May 4, 2026 11 min read MarginPlug Operator Intelligence

Most HVAC owners evaluate their technicians based on feel — who complains less, who customers like, who's been around longest. The problem with feel is that it doesn't tell you whether a technician is producing enough revenue to justify their fully-loaded cost. And in a business where each technician represents $65,000–$95,000 per year in fully-loaded labor expense, the gap between a high-efficiency tech and a low-efficiency tech is the difference between margin and loss on that seat.

This article covers the five metrics that actually measure technician efficiency, the 2025 benchmarks for each, the four operational reasons techs fall below those benchmarks, and a simple framework for knowing — before payroll runs — whether each technician on your roster is covering their cost.

$180K–$280K
Revenue per tech per year — top-quartile HVAC operators
$120K–$160K
Industry average revenue per technician — residential HVAC
Under $100K
Below this threshold, a tech is unlikely to cover fully-loaded cost at market wages

Revenue Per Technician Is Not the Only Metric — But It's the Starting Point

Revenue per technician per year is the number Google will return if you search "hvac revenue per technician benchmark." It's a useful starting metric, but it's incomplete on its own. A technician generating $200K in revenue at a 35% gross margin is worth less to the business than one generating $160K at a 55% gross margin. The revenue number tells you about volume. The margin number tells you about quality.

More precisely: you want to know gross profit per technician — not just revenue. But revenue per tech is the right place to start because if a technician isn't generating enough revenue, there's no margin math that saves the economics. Think of it as the floor check before you go deeper.

Here's how the math works on a technician fully-loaded at $75,000 per year (including wages, payroll taxes, benefits, workers' comp, and tool allowance — see the labor burden article for the full calculation). To cover that cost at a 50% gross margin, the technician needs to generate at least $150,000 in revenue annually. At 45% gross margin, the breakeven is $167,000. Anything below that level means the seat is margin-negative — you're paying more to have that technician than they're producing in gross profit.

"I thought all my guys were performing similarly. When I actually ran revenue per tech by individual, I had one guy doing $240K and one doing $88K — both full-time. The one at $88K had been with us four years. I had no idea we were losing money on him every month." — HVAC owner, 5 trucks, $1.4M revenue

The 5 Metrics That Actually Measure Technician Efficiency

Revenue per tech per year is a trailing metric — it tells you what already happened. The five metrics below tell you what's happening now and give you enough lead time to intervene before the P&L catches up.

1 Revenue per tech per day (RPTD)
The daily version of annual revenue per tech — your fastest feedback signal. Calculate by dividing total revenue booked by each technician by the number of days they ran calls. Review weekly.
2025 benchmark
Top quartile: $1,800–$3,200/day · Average: $900–$1,400/day · Below $700/day = active leak
2 Jobs completed per day
How many calls a tech completes per shift. Lower than benchmark typically signals route problems, job cycle time bloat, or dispatch inefficiency — not tech skill. High job count with low RPTD signals ticket mix or close rate issues.
2025 benchmark
Service/repair: 4–7 jobs/day · Replacement/install: 1–2 jobs/day · Mixed: 3–5 jobs/day
3 Close rate on repair recommendations
Of the repair or replacement recommendations a tech presents, what percentage does the customer accept? This is the metric most owners skip tracking per-tech — but it's the clearest signal of presentation effectiveness and trust built on the call.
2025 benchmark
Top quartile: 82–90% · Average: 65–75% · Below 55% = presentation or pricing problem
4 Average ticket size
The average invoice amount per completed job. Best tracked by call type (service vs. repair vs. replacement) so you're comparing apples to apples across techs. A tech with a low average ticket on repair calls is leaving options on the table, not closing the full scope.
2025 benchmark
Residential service: $180–$320 · Repair: $380–$620 · Replacement: $4,500–$9,000
5 Callback rate
The percentage of jobs that require a return visit within 30 days due to the same issue. The most directly controllable quality metric. High callback rate means rework cost — you're paying twice to fix one problem, with zero additional revenue from the second visit.
2025 benchmark
Top quartile: under 3% · Average: 4–7% · Above 8% = training or diagnostic quality issue
+ Agreement conversion rate
What percentage of eligible customers does each tech convert to a service agreement? Often ignored per-tech, but the highest-LTV outcome from a service call. Top techs have a natural enrollment pitch — others don't mention it at all.
2025 benchmark
Repair calls: 25–40% conversion · First-time service calls: 15–25% · Replacement: 50–65%
Delivery pillar diagnostic

Know which technician efficiency metric is your primary leak — before it shows up in your P&L.

MarginPlug's Delivery pillar benchmarks your revenue per tech, callback rate, and jobs-per-day against operators at your revenue level — and identifies the specific operational failure driving below-benchmark numbers.

Run the free diagnostic Free during beta · No credit card · 8 minutes

2025 Revenue Per Technician Benchmarks by Business Type

Revenue per technician varies significantly based on service mix, market, and fleet size. A replacement-heavy business will show higher revenue per tech than a service-heavy one — not because their techs are more efficient, but because the ticket size is structurally larger. Compare yourself against your own service mix first, then against the broader benchmark.

Business type Below average Average Top quartile Best in class
Residential service / repair Under $95K $110K–$155K $160K–$210K $220K+
Residential replacement-focused Under $140K $160K–$220K $230K–$310K $320K+
Mixed service + replacement Under $120K $135K–$185K $190K–$260K $270K+
Light commercial Under $160K $180K–$260K $270K–$370K $380K+

The compounding revenue impact of a 1-tech efficiency gap

Revenue gap by efficiency tier — 5-tech team, residential mixed service
Best in class ($270K/tech)
$1.35M
Top quartile ($230K/tech)
$1.15M
Average ($160K/tech)
$800K
Below average ($110K/tech)
$550K
Margin-negative (<$95K/tech)
<$475K

Same 5 technicians. Same payroll cost. The gap between average efficiency and top-quartile efficiency is $350,000 in annual revenue — on identical headcount. At a 52% gross margin, that's $182,000 in additional gross profit. That's not a hiring problem. That's an efficiency problem — and efficiency problems are fixable.

The 4 Operational Reasons Technicians Underperform Benchmarks

1
Dispatch misalignment — wrong tech on the wrong job
Primary driver of low RPTD and jobs-per-day · affects every efficiency metric downstream

The most common efficiency leak isn't the technician — it's the dispatch decision that put them on the wrong type of call. A senior technician dispatched to a routine maintenance visit that a junior tech could handle costs you the senior tech's capacity on higher-complexity, higher-revenue calls. Conversely, a junior tech dispatched to a complex commercial diagnostic will run long, generate a callback, and may miss the full repair scope. Both are dispatch failures, not technician failures.

Dispatch by skill match is the single highest-leverage operational lever in HVAC delivery efficiency. Every mismatch either wastes senior capacity on low-value calls or generates rework costs from junior techs on calls beyond their skill level. Most owners dispatch by availability, not skill — because availability is visible in real time and skill match requires a more deliberate dispatch process.

The fix
Build a simple call-type tier system — three levels is enough (routine maintenance/simple repair, standard diagnostic repair, complex diagnostic/replacement). Assign each technician a tier rating. Require dispatchers to match call type to tech tier before any other factor. This single change consistently produces a 15–25% improvement in senior tech RPTD within 60 days, because senior techs start spending more time on calls that generate $800–$2,000 tickets instead of $180 maintenance visits.
2
Job cycle time bloat — jobs taking 40% longer than they should
Reduces jobs-per-day directly · primary driver of below-benchmark annual revenue per tech

A standard residential service call should take 60–90 minutes from arrival to departure — including diagnosis, repair, system check, and customer communication. When that same call takes 2.5 hours because the tech didn't have the right part on the truck, had to make a supply run, or spent 40 minutes on phone calls during the job, you've lost the capacity for at least one additional call that day. Across a team of 5 techs running 220 days per year, 30 minutes of cycle time bloat per call eliminates roughly 2 calls per tech per week — that's over 500 jobs per year you never ran.

The most common causes of cycle time bloat are preventable: incomplete truck stocking (wrong or insufficient parts inventory), no pre-call job briefing (tech shows up without knowing the equipment history), and CSR intake that doesn't capture enough detail to stage the call properly. None of these require new software to fix.

The fix
Implement a daily truck stock checklist for the top 20 most-used parts — reviewed each morning before the first call. Require CSRs to capture equipment make, model, age, and symptom description on every incoming call, and include that information in the job brief to the technician. Set a target completion time for each call type and track actual vs. target by tech weekly. Cycle time variance by tech is almost always a stocking or preparation problem — not a skill problem — and it responds quickly to process intervention.
3
Incomplete repair scope presentation — not showing the full picture
Primary driver of below-average ticket size and close rate · directly tied to revenue per tech

The technician who arrives at a no-cooling call, replaces the failed capacitor, collects $280, and leaves has done the job requested. But they may have found a contactor showing pitting and wear, a low refrigerant charge, and a blower wheel with debris buildup — and said nothing. Not because they're dishonest, but because they didn't have a structured process for presenting a full system evaluation with tiered recommendations. The customer never had the opportunity to approve additional work because it was never offered.

This is the most reversible of the four efficiency gaps because it's a behavior change, not a skill change. The technician already identified the other findings — they just didn't present them. Structured presentation training has consistently produced 20–35% average ticket increases for HVAC companies in the $750K–$3M range, with zero change in customer satisfaction scores.

The fix
Implement a mandatory multi-option presentation on every repair call: Option A (fix the immediate failure), Option B (fix the failure plus address the two most critical secondary findings), Option C (full system restoration or replacement consideration). The customer chooses. Most will choose B. Techs who present this format consistently run 25–40% higher average tickets than those presenting a single-option quote — and customer satisfaction scores are equal or higher because customers feel informed, not sold. Introduce this in a 2-hour training session with role play, then track average ticket by tech weekly for the next 90 days.
4
No individual performance visibility — techs don't know their own numbers
The root cause multiplier — every other problem persists longer when techs can't see their metrics

In most HVAC businesses, technicians have no idea what their individual revenue per day, average ticket, or close rate is. They know whether the day felt busy. They don't know whether the day was actually productive. This isn't laziness — it's a management system failure. When people can't see their own performance, they can't self-correct. The same behavior that's producing a $900/day RPTD continues because there's no signal that $900/day is below where it needs to be.

The inverse is also true: when technicians can see their own numbers weekly, most of them improve — not because you told them to, but because humans respond to legible feedback. The technician who sees their average ticket at $310 against a team benchmark of $480 doesn't need a coaching conversation. They need the number. The coaching conversation is more productive because there's something specific to discuss.

The fix
Build a simple weekly tech scorecard — one page, five numbers: jobs completed, RPTD, average ticket, close rate, and callback rate. Share it individually with each technician at the start of each week. Include a team benchmark line so each tech can see where they stand relative to the team without public shaming. This takes 30 minutes per week to produce from your service software data and typically produces a 10–18% average efficiency improvement within 90 days — across the whole team, not just the underperformers.

How to Calculate Your Revenue Per Technician Right Now

You need two numbers from your service software or QuickBooks: total revenue generated by each technician over the last 12 months, and the number of days each technician ran calls over the same period. Divide the first by the second for RPTD. Multiply RPTD by 220 working days for an annualized comparison to the benchmarks above.

If your service software doesn't attribute revenue to individual technicians, you have a visibility problem that's costing you money independently of the efficiency problem. Every major HVAC service platform — ServiceTitan, Housecall Pro, Jobber, FieldEdge — can generate this report. If you're on a system that can't, the inability to see tech-level performance is itself a margin leak worth addressing before almost anything else.

Once you have the numbers by tech, rank them. The gap between your highest and lowest performer tells you the efficiency range your team currently operates in. The difference between your lowest performer's current RPTD and the average benchmark, multiplied by their days worked, is the revenue you're leaving on the table from that seat alone — before you've changed a single process. That number, for most 4–6 tech operations, is between $40,000 and $120,000 per underperforming technician per year.

Delivery pillar diagnostic

Find out what your technician efficiency gap is actually costing you — in dollars, not feelings.

MarginPlug's Delivery pillar scores your revenue per tech, callback rate, jobs-per-day, and close rate against operators at your revenue level. It tells you which metric is your primary leak and what closing the gap is worth annually. Free during beta.

Run the free diagnostic Free during beta · No credit card · Results in minutes