Which Technician Completes Jobs Fastest? Tracking Performance Data

The Assumption That's Costing You Throughput#

When I had three technicians, I assumed they were roughly equivalent in speed. They'd all done the training, they all seemed competent, and I had no data suggesting otherwise. Then I started tracking job completion by technician in my job management system. The reality was startling: my senior tech, James, completed 23 jobs per day on average. My mid-level tech, Priya, completed 17. My newest tech, Marcus, completed 11. On screen replacements specifically, James averaged 28 minutes, Priya averaged 41 minutes, Marcus averaged 67 minutes. These weren't competence differences — Marcus was perfectly competent. They were experience and confidence differences. But without the data, I was scheduling all three techs on the same mix of jobs as if they had the same throughput. The result: I was underutilising James, overloading Marcus with complex jobs he wasn't ready for, and leaving revenue on the table every day.

What Metrics Actually Matter#

Technician performance in a repair shop should be measured on three dimensions, not one. First, throughput: jobs completed per day or per week, broken down by job type (screen replacements, battery swaps, diagnostic jobs). Second, quality: warranty returns attributable to specific technicians, customer complaints mentioning technician names, quality check fail rates. Third, complexity mix: are they handling jobs appropriate to their skill level, or are they being assigned above their capability? A technician who completes 25 jobs per day but generates 8% warranty returns is not a star performer — they're a liability. Conversely, a technician who completes 14 jobs per day but has zero warranty returns and handles the most complex motherboard repairs is highly valuable. The metrics need to tell a complete story, not just reward speed.

Tracking in AskBiz: How the Data Flows#

In AskBiz, every job is assigned to a technician at intake or when work begins. When the technician marks the job complete, the timestamp is recorded. At any point, you can run a report showing jobs completed per technician, average completion time per job type per technician, warranty returns by technician, and revenue attributed to each technician's output. The report doesn't require the technician to do anything extra — it's a natural output of the job management workflow. The key discipline is ensuring techs update job status themselves rather than having the front desk do it. When the tech marks their own jobs complete, the timestamp is meaningful. When a front desk person marks jobs complete at the end of the day in a batch, the data is useless for productivity analysis.

Using Data for Training, Not Blame#

The worst way to use technician productivity data is as a weapon: "Your numbers are bad, fix it." The best way is as a diagnostic: "Your battery replacement time is 45 minutes versus the team average of 28 minutes. Let's watch James do one and see if there's a technique you could adopt." Technician performance data should drive coaching conversations, not performance improvement plans. In most cases, slower techs are slower because of specific technique gaps that can be closed with targeted training. Once Marcus worked alongside James for two weeks specifically on screen replacements, his time dropped from 67 minutes to 44 minutes. That improvement, compounded across his weekly output, added three additional screen replacements per day — an extra £60-90 daily revenue from one coaching intervention.

Incentive Structures Based on Productivity Data#

With reliable productivity data, you can build meaningful incentive structures. A job-completion bonus tier: base salary plus £50 bonus per week for hitting 90+ jobs, £100 for 110+. A quality bonus: maintain warranty return rate below 1% for the month and earn an additional £75. A skill premium: technicians certified to handle motherboard-level repairs earn £2/hour more than those doing screen-only jobs. Without data, these structures are guesswork. With data, they're precision tools for driving the behaviours you want. The productivity data also makes promotion decisions objective: when a senior tech position opens up, the data shows clearly who has the throughput, quality, and complexity handling to deserve it.

Dealing with Gaming the Metrics#

Any measurement system creates incentives to game it. A tech who's measured on throughput might rush jobs, creating quality problems. A tech measured on warranty returns might refuse to take complex jobs where failures are more likely. Design your metric system to make gaming self-defeating: throughput matters AND quality matters AND complexity mix matters. A tech who games throughput will see their warranty rate rise and lose their quality bonus. A tech who avoids complex jobs will plateau in skill and income. The combination of metrics, reviewed monthly in a conversation rather than just reported, creates an honest picture that's hard to optimise through gaming.

The Monthly Performance Review#

Once per month, spend 20 minutes with each technician looking at their data. Not as a performance review in the formal HR sense, but as a coaching conversation. "Here's your throughput this month — up 8% from last month, which is great. Your battery replacement time is still a bit longer than James's; want to work on that? Your warranty rate is perfect — zero returns this month, well done." These conversations, grounded in data, are more valuable than any amount of vague positive feedback or generic criticism. Technicians who understand how they're performing and what improvement looks like will self-direct their development in ways that "try harder" never achieves. AskBiz manages repair jobs end-to-end including technician performance tracking. Try free at askbiz.co

• In most repair shops, the fastest technician completes 40-60% more jobs per day than the slowest — but owners rarely know this because they don't measure it.
• Tracking technician performance by job type reveals training needs, staffing inefficiencies, and incentive opportunities.