Found search results for ""

Read Time — 10 minutes

The Best Tech Isn't Always the Busiest Tech

A technician works on electrical equipment beside coiled cables and a diagnostic device

Summary

The busiest technician isn't always the most profitable one. Jobs per week and customer ratings measure effort, not outcome. Four KPIs show which technicians really make money: first-time fix rate, callback rate, parts cost accuracy and true work-order margin.  

Field service companies that track all four in one system, such as ECI's Vision or GlobalEdge, can catch callbacks and margin leaks before month-end and recover technician capacity without hiring. 


Ask any dispatcher who the best tech on the team is, and the answer is the same from every corner of the country: the one who closes the most calls. The one who knocks out 20 jobs a week, moves fast, and never lets the board back up. On a scoreboard built around volume, that tech wins. Every time. 

Then the callbacks roll in. 

Leaders at small and midsize commercial field service companies make dispatch and staffing calls every day based on what they can see: jobs completed, hours logged, customer ratings. Those numbers feel like performance.  

They often aren't. The metrics that decide whether a job made money, things like first-time fix rate, callback rate, parts accuracy and true work-order margin, tend to live in spreadsheets, if they live anywhere at all. By the time someone reconciles them at month-end, the margin's already gone. 

Your scoreboard has a blind spot 

Most service companies grade technicians on whatever's easiest to count. Jobs per week come straight off the dispatch board. Hours come off the timesheet. Customer ratings come from the survey. None of those numbers needs a system that connects the field to the books, so they become the scoreboard by default. 

The trouble is what they leave out. A tech who closes 20 calls a week looks like a star right up until someone asks how many of those calls turned into a second truck roll, how many parts came back as returns or overages, and what each job earned after labor and travel. Those answers live in different places: the inventory system, the accounting package, a dispatcher's memory.  

We've written about the hidden costs of running a service business across too many systems and about how incomplete service histories set techs up to miss on the first visit. Both problems hide nicely behind a healthy number of jobs per week. 

Speed and volume measure effort. They don't measure outcomes, and the gap between the two is where the margin slips out of a service business without anyone noticing. Hustle doesn't scale. It can carry a shop to a certain size, but it's the KPIs that will carry it past that point. 

Two techs, one week 

Picture two techs wrapping up a Friday. The first logged six quick calls. The second logged four and took his time on each one: he checked the equipment history before he rolled up, made sure the parts on his truck matched the work order and tested the repair before he left. 

On Friday, the first tech looks like the better bet. By the following Thursday, three of his six jobs have come back as callbacks. Each one pulls a tech off a billable appointment, burns another trip and another set of parts, and lands on a customer who thought the problem was already fixed. The second tech's four jobs? Still closed. Every one of them held its margin. 

Stretch that pattern over a quarter and the rankings flip. That "workhorse" who runs 20 jobs a week with a 4.7 customer rating may wind up finishing last on the metrics that drive profit with a 71% first-time fix rate, a 22% callback rate, 65% parts cost accuracy and $145 in margin per job. 

On the contrary, the "steady hand" who runs 13 jobs a week  may finish first, with an 89% first-time fix rate, a 7% callback rate, 94% parts cost accuracy and $248 per job. Fewer jobs on the board but a lot more money in the bank. 

Four numbers that decide whether a job made money 

None of these shows up on a jobs-per-week report. Together, they explain almost every gap between a tech who looks productive and a tech who's profitable. 

First-time fix rate. The share of jobs closed in one visit. It's the biggest lever you've got on technician capacity, because every job that misses the first time eats a second slot that could've gone to new, billable work. ECI's "The First-Time Fix Framework" breaks down the usual suspects: skill mismatch, missing parts, incomplete job history and thin work-order information. 

Callback rate. The share of completed jobs that bring a tech back for the same issue. It's the lagging indicator of a weak first-time fix rate, and it usually shows up in the schedule weeks before it shows up in the financials. 

Parts cost accuracy. How closely the parts a job consumed match what was quoted, stocked and billed. Overages, unreturned cores and parts pulled off the wrong truck chip away at margin a few dollars at a time. "Good enough" inventory accuracy costs more than it looks like. 

True work-order margin. Revenue on the job minus every hour of labor, every part and every mile of travel it took, second trip included. That number only exists when service activity ties to receivables, payables and the general ledger, which is the whole point of job costing visibility in a field service ERP. ECI's "From Field to Finance" covers how that connection works. 

Industry benchmarks show just how wide the spread between techs can get. Aquant benchmark data puts avoidable dispatch rates at 24% for lower-performing teams and 3% for top performers. The same research estimates that service costs could drop 23% if every tech performed like the top 20%. 

The callback tax 

The technician shortage gets most of the attention, and it's earned it. Humanly puts the cost of a single unfilled tech role at $4,500 to $7,500 a day in lost revenue capacity, based on three to five missed service calls per empty seat. A JLL report cited by SynchronApp estimates 2.1 million skilled trades jobs in the U.S. could go unfilled by 2030.  

But the shortage is only half the problem. Aquant's benchmark data, finds that roughly 14% of service visits are unnecessary. A company with 10 techs and a 14% avoidable-visit rate is paying 1.4 full-time technicians to run work that shouldn't exist.  

Hiring can't solve every problem. Every callback a busy tech generates lands on a full schedule, bumping a new, billable job to next week. Which then sends a frustrated customer shopping around. Recruiting a replacement takes weeks, and the new hire walks into the same system that tripped up the last one.  

ECI's "Overcoming Field Service Challenges" looks at this squeeze from the operator's side: the fastest path to more capacity is getting more from the team that's already on the payroll. 

Fix the system, not the technician 

None of this is an argument for a technician leaderboard. The fast tech in the example above is doing exactly what the scoreboard rewards. On the jobs that came back, odds are he showed up without the equipment history, with the wrong part on the truck or with a work order missing the one detail that would've told him what was wrong. Those are system failures, and they land on whoever gets dispatched. 

The useful question for a service leader is what the organization puts around the technician. Does the dispatcher see skills and certifications when assigning a job, or just who's closest? Does the tech see the site's service history on a tablet before walking in the door? Does the truck stock match the jobs on the board? ECI's RemoteField Service+ mobile app exists to answer that second question, by putting history, parts and work-order details in the tech's hands on site. 

Measured this way, first-time fix and callback data by technician, job type and site gives a manager something better than a ranking. It shows where the system is letting the field down: an equipment line that keeps generating return visits, a dispatch habit that sends the wrong skill set to the hardest jobs, a parts category that's always running short. Technicians can tell the difference between a tool that judges them and one that gets the obstacles out of their way. 

What it looks like when the numbers live in one place 

ECI Software Solutions builds field service software for commercial HVAC and refrigeration, commercial food equipment, petroleum equipment and other commercial trades through two platforms. Vision is an all-in-one field service management platform, that connects scheduling, dispatch, mobile technician workflows, parts, inventory, purchasing, billing and reporting. GlobalEdge is the field service ERP for larger or more complex operations that want service, inventory, job costing and financials in one system, with multi-location control included. 

Because both platforms record the work order, the parts, the labor and the invoice in one place, the data behind those four metrics lives in one system instead of four. Reporting on it stops being a month-end reconciliation project. A manager can compare what a job quoted against what it consumed, trace a callback to the original visit and read work-order margin while there's still time to do something about it. ECI's Unlock Cashflow page walks through how invoicing, margins and parts reordering connect, and the Simplify Operations page has a short quiz on whether Vision or GlobalEdge fits your operation. 

So, which tech would you bet on? 

The 2-Minute KPI Scorecard asks a short series of questions about how clearly you can see first-time fix performance, callback trends, technician effectiveness, work-order profitability and contract performance. It returns a result that identifies your blind spots and recommends next steps. 

And when you're ready to see how Vision or GlobalEdge would surface these numbers for your business, talk with ECI's field service team. You can also read customer stories from service companies that made the switch, browse upcoming webinars and events or keep reading on the ECI field service blog. 

Recap

  • Volume metrics such as jobs per week, hours logged and customer ratings measure effort, not outcome. They hide callbacks, parts overages and margin loss. 
  • In the Pick Your Best Tech scenario, the 20-jobs-a-week "workhorse" nets $145 per job. The 13-jobs-a-week "steady hand" nets $248. 
  • Four KPIs decide whether a job made money: first-time fix rate, callback rate, parts cost accuracy and true work-order margin. 
  • Roughly 14% of service visits are unnecessary, per Aquant benchmark data. On a 10-tech team, that's 1.4 technicians running work that shouldn't exist. 
  • Use the data to fix the system around the technician (dispatch, parts, job history), not to rank people. 
  • Next steps: take the Pick Your Best Tech quiz then run the 2-Minute KPI Scorecard. 

FAQs

Why isn't the busiest technician always the most profitable?

Because jobs per week counts effort, not outcome. A tech who closes 20 calls a week but gets called back on a fifth of them burns a second trip, a second set of parts and a billable slot every time. Subtract that labor, travel and parts waste, and the slower tech with the higher first-time fix rate often earns more per job. 

What is first-time fix rate in field service?

First-time fix rate is the share of service jobs resolved in a single visit. It's the biggest lever on technician capacity, because every miss eats a second appointment slot that could've gone to new, billable work. Benchmark data cites first-time fix rates as high as 81% among top-performing teams. 

How is callback rate different from first-time fix rate?

Callback rate is the share of completed jobs that bring a technician back for the same issue. First-time fix rate tells you how often a job closed on the first visit; callback rate tells you how often a "closed" job came back. They move together, but callbacks show up in the schedule weeks before the margin damage shows up in the financials. 

How much capacity do callbacks cost a service team?

Aquant benchmark data finds roughly 14% of service visits are unnecessary, and a failed first attempt can add about 14 days and two more visits to a case. For a 10-technician team, a 14% avoidable-visit rate equals 1.4 full-time techs working jobs that shouldn't exist. 

How do I measure technician performance without creating a leaderboard?

Track first-time fix rate, callback rate, parts cost accuracy and work-order margin by job type and site, not just by technician. Then read the results as a diagnostic for the system around the tech: Did dispatch have skills data? Did the truck have the part? Did the work order carry the equipment history? Those are gaps a technician can't close on site, and they drive callbacks no matter who gets dispatched. 

What software tracks field service KPIs like first-time fix rate and work-order margin?

Platforms that record the work order, parts, labor and invoice in one system can report these KPIs without spreadsheet reconciliation. ECI's Vision is an all-in-one field service management platform covering scheduling, dispatch, mobile technicians, parts, inventory, purchasing, billing and reporting. GlobalEdge is a field service ERP that adds integrated job costing, accounting and multi-location control for more complex operations.