What does the technician benchmark actually measure?
Ask what appears in the numerator, who counts in the denominator and when each item is recorded. Revenue per person, completed jobs per technician and sales credited to an advisor describe different parts of your operation. Your buyer or seller cannot interpret a gap until both sides can reproduce the measure.
A residential installer can complete high-dollar changeouts sourced by someone else. A service technician may spend a full day restoring heat at four older properties and identify two systems likely to need future replacement. A junior helper may be essential to installation capacity while receiving no sales credit. Ranking all three people by undifferentiated revenue can create the illusion that one person contributes little and another can take on unlimited work.
Write down the proposed benchmark in a sentence a dispatcher can challenge. For example, your comparison might cover completed service-invoice revenue per active diagnostic technician in one territory in July. That wording tells the team to exclude install crews or at least show their separately allocated work. If nobody can say whether warranty work, maintenance visits or unpaid invoices appear in the measure, obtain the definition before comparing the shop with a published percentile.
Which published peer group belongs beside your shop?
Match the shop to the source’s trade, company size, work type, geography and time period as closely as the source permits. Where a match remains imperfect, record the difference and explain its likely direction. A heating-heavy commercial service route in winter has little reason to resemble peak-season residential replacements in another climate.
ServiceTitan’s industry benchmark report describes available filters and peer groups, reporting periods and metric definitions. Its documentation distinguishes market-wide reporting from comparison of an individual tenant. For its completed jobs per technician measure, it describes an active technician population and company-level calculation before percentile comparison. Preserve the date the report was refreshed and the exact group you selected.
| Dimension | Question for your shop | Evidence to retain |
|---|---|---|
| Job mix | Do the same departments and job classes enter both figures? | Business-unit mapping and exclusions |
| Technician population | Are helpers, owners, new hires and inactive staff treated consistently? | Roster, assignments and active-period rule |
| Revenue basis | Are the values completed, invoiced, sold or collected? | Report definition and reconciliation |
| Peer group | Do climate, size, trade and calendar months fit? | Dated source, selected filters and known differences |
Read what the percentile ranks. Suppose the source calculates one ratio per company and then ranks companies. A large shop does not automatically contribute one observation for each of its technicians. Pooling every employee from your target and comparing that employee distribution to a distribution of company results can produce a persuasive-looking chart with mismatched units. Keep the source’s statistical population in your supporting notes.
How do you rebuild your own number?
Choose one closed period, classify the jobs and reconcile company-level revenue before distributing anything across technicians. Your aggregate should be reproducible from unique invoices and credits. Then reconcile the participating workers with the actual roster for the same period, including owners who worked in the field.
- Select a closed period and export job identifiers, completion dates, job class and net invoice lines.
- Identify employee assignments, helpers and selling technicians separately from the revenue record.
- Apply the source’s eligibility rule and preserve each exclusion and reason.
- Reconcile the company total, then allocate shared work under documented split rules.
- Compare the result with paid hours, active days and the technician roster for the period.
Consider a shop that reports $240,000 of monthly job revenue and eight technicians. The simple average is $30,000 per person. Now suppose two people are install helpers whose work is credited entirely to two leads. Removing the helpers from the denominator without changing revenue yields $40,000 across six people. Nothing in the shop improved. The entire difference comes from changing the denominator. Choose the treatment that matches your business question and display both populations when relevant.
The same problem appears in the other direction. A technician who began on the last day of the month may count as active if they completed one job. That is appropriate for a particular published metric and unhelpful for estimating full-time capacity without qualification. Use a second internal view based on paid or available hours. Your technician productivity tool can explore hours without changing the published source’s definition.
Review one shared replacement job by hand. Match the company invoice to the splits credited to the salesperson, lead and helper. Record what happens to the metric if a second technician joins halfway through the job. If the dashboard and payroll disagree about who worked the installation, fix the assignment before asking why one person’s reported productivity appears weak.
What can a median hide about your technicians?
A midpoint can describe a peer group while concealing the shape of your own work. Look at individual cohorts, distribution and role before making a staffing decision. A single specialist, unusual project or unusually busy week can move the mean even when most technicians work at their usual pace.
Imagine five technicians with illustrative comparable monthly revenue of $18,000, $21,000, $22,000, $23,000 and $66,000. Their median is $22,000 and their average is $30,000. Before assuming the lower four should match the fifth, inspect the $66,000 technician’s projects, helpers, lead source and route. A single complex replacement credited to that employee might explain the spread. The shop might also depend dangerously on that person’s skill or customer relationships.
Now look for a genuine operating opportunity. Comparable service calls in one branch may take longer because technicians repeatedly return to the warehouse. If job-level records show a recurring missing part, better van stocking could release billable hours. Estimate the parts investment, training and number of avoidable trips. Check whether there are customer calls ready to fill the released capacity. Time saved produces cash only when it reduces cost or supports profitable work.
Service quality belongs beside output. Read callbacks, credits, financed-job cancellations and customer complaints by job type. A short appointment may look efficient until the same technician returns two days later without a second invoice. Combine the visits for that service episode when you evaluate contribution. Your technician underwriting guide connects the resulting pattern with retention, training and owner dependence.
How do you turn a benchmark into a defensible operating decision?
Use the gap to select an observable process change and define the test before assuming any earnings improvement. Assign an owner, identify the affected crew and measure the full cost. A useful benchmark can guide the first ninety days without becoming an unsupported adjustment to historical earnings.
If you are selling, include the metric definition, monthly history and evidence of any improvement already achieved. A dashboard showing a recent high point deserves less weight than a sustained result after travel and callbacks are included. Give the buyer the original reports and let them reproduce the selected months. Your technician roster download can identify who was active and whether they are expected to stay.
If you are buying, compare the opportunity with the current dispatch calendar. Which lead, vehicle and qualified technician will perform the additional work? Who pays for training or an added helper? Would more jobs worsen overdue maintenance visits? If the proposed improvement relies on changing several constraints at once, stage the changes and model the period before the benefit arrives.
Keep a control period or a comparable route when possible. One branch may report higher technician revenue after a price increase even though completed work and labor productivity did not change. Separate the effects of price, work mix, hours and repeat visits. Recalculate the estimate using contribution as well as revenue so you can tell whether increased output improves earnings after expenses.
At the next operating review, show the original source, the shop’s comparable result and the result after any tested change. Identify what the technician could influence and what dispatch, marketing or purchasing controlled. Your operations hub can help the team assign the next action. The number should help your people explain a real process and improve it, without mistaking a change of report settings for progress.
When two branches use different pricing systems, run a same-job comparison before concluding their technicians perform differently. Select several common repairs with comparable equipment, access and travel. Compare the recorded time, price, cost of the component, return visits and amount collected. A branch with higher revenue per technician may simply charge more for the same repair. That finding can still lead to a pricing decision, but it should lead to a different conversation from a training or scheduling problem.
Use the same discipline on a new-hire cohort. Mark the first date each technician independently handled the job class you are measuring. A month spent riding with a trainer does valuable work for the shop and can reduce the trainer’s near-term output. Identify both effects before presenting lower revenue as evidence of waste. When your buyer plans to grow by hiring several technicians at once, model the trainer hours and ramp period alongside the planned output of each new hire.
Retain the original report definition when the vendor updates its dashboard. If results jump after a software change, rerun one historical month using both definitions when possible. An apparent improvement is difficult to defend if your team cannot distinguish better field performance from a changed allocation rule.
Where can you go next?
What else should you know?
Is there one defensible revenue-per-technician target for all HVAC companies?
Use a source that defines the jobs, personnel and period included, then decide whether your shop belongs in that population. A residential replacement crew, maintenance technician and commercial project team perform different work. Compare them separately before you combine their contributions in a company-wide operating or acquisition model.
What is the difference between a median and my average technician result?
A median is the middle observation in an ordered group, while an average adds the observations and divides by their number. A published median of company results may summarize companies rather than individual technicians. Ask what each observation represents before you compare it with your own fleet-wide average.
Can I use a benchmark gap as an EBITDA add-back?
A gap identifies a question about future performance. It does not establish that historical earnings omitted profit. Quantify the operational change, labor, training, leads, parts and timing required to improve results. Put the opportunity in a separate operating case and preserve the documented historical cost structure in your earnings reconciliation.
What if the company has no enterprise reporting software?
Use the records it has. Match invoices, completed work orders, technician assignments, timecards and credits for a representative period. Document any assumptions about shared jobs and missing hours. A smaller, reproducible comparison can support a better decision than a sophisticated report whose definitions the seller cannot explain.
Which sources informed this page?
- Industry benchmark report in Benchmark+ · ServiceTitan, November 21, 2026
- Technician performance report template · ServiceTitan, November 21, 2026
- Dashboard business metrics · ServiceTitan, November 21, 2026
