Guide

Technician Productivity:Formulas, Billable and Paid Hours, Efficiency, Drive-Time Share, First-Time Fix Rate and a Sample Week

Technician productivity as billable over paid hours, jobs per day, first-time fix rate and revenue per technician, with a sample week and drive-time share.

By Published Updated

13 min read

Technician productivity is the share of a field technician's paid time spent on billable work: billable hours divided by paid hours, times 100. It is read beside three companion measures, jobs completed per day, first-time fix rate and revenue per technician, because a technician can post a high ratio on long jobs that fix nothing on the first visit.

The measure goes wrong in ways an owner can see on the board. Two technicians each work a 40-hour week and one invoices twice the other, and nobody can say whether the gap is territory, skill, parts or paperwork. A drive across town between two calls is recorded as part of the first job, so the report shows no drive time at all. A return visit for the same leak is entered as a new job and counted as productive. This guide belongs to the running and managing guides from FieldRanger. It starts with the productivity formula and its difference from efficiency, then the companion measures, the drive-time share and a sample week for five technicians, and closes with tracking methods, the levers that raise the ratio, measurement errors, a checklist and the reports in FieldRanger.

Three kinds of hours carry the calculation. Paid hours are every hour the technician is paid for, from the first clock-in to the last clock-out. Billable hours are the hours spent working on a job the customer is charged for. Unbilled hours are the remainder: driving between jobs, loading the van and picking up parts, paperwork, meetings, and return visits that are not charged.

Technician productivity formula: billable hours over paid hours

The technician productivity formula is billable hours ÷ paid hours × 100. A technician paid for 40 hours who spends 26 of them working on billable jobs has a productivity of 65%. The calculation is made per technician and for the team, over a stated period of at least a week, because a single day swings with one long job or one cancelled call.

Both inputs need a definition written down before the first report. Paid hours follow payroll, and federal rules decide what is in them: travel from job site to job site during the workday is hours worked, and so is the trip from a designated place where the employee must report to collect instructions or pick up tools (29 CFR 785.38, via Cornell LII, checked November 12, 2026). Drive time between jobs therefore sits in the denominator whether or not the business bills a trip charge. Billable hours follow the job records: time clocked against jobs that were invoiced, excluding any return visit for the same problem that was not charged.

Technician efficiency vs. productivity: clock hours and sold hours

Productivity and efficiency divide different hours: productivity compares job time with paid time and measures how much of the day reached a customer, while efficiency compares the hours sold with the hours taken and measures speed on the job. A flat-rate company that prices a capacitor replacement at a sample 1.0 book hour, done in 0.75 hours on site, records an efficiency of 133.3% on that job, whatever the technician's productivity for the day.

Dealership software uses the same split: Blackpurl, a dealership management system, documents productivity as hours clocked onto service jobs divided by hours the technician was clocked in for payroll, with an example of 5.36 job hours in a 7.59-hour day giving 70.62%, and efficiency as invoiced hours divided by job-clocked hours, which can exceed 100% (Blackpurl, Technician Productivity Reports, updated June 2, 2026). The terms are not standardized across vendors, so the formula behind any report is stated beside its figure.

A field service company needs both readings, and they answer different questions. Low productivity with high efficiency points at the schedule: the technician works fast and spends the day driving or waiting for parts. High productivity with low efficiency points at the job: the day is full and the work takes longer than it is priced for, which is a price book or training question.

Jobs per day, first-time fix rate and revenue per technician

The companion measures guard against a ratio that looks good for the wrong reason.

Technician productivity measures and their formulas
MeasureFormulaWhat it catches
ProductivityBillable hours ÷ paid hours × 100Time lost to driving, shop time and paperwork
EfficiencySold or book hours ÷ hours on the job × 100Jobs taking longer than they are priced for
Jobs completed per dayCompleted jobs ÷ days workedLong jobs that keep the ratio high and the board short
First-time fix rateJobs fixed on the first visit ÷ jobs that needed a fix × 100Return visits that look like productive hours
Revenue per technicianInvoiced revenue ÷ technicians, per week or yearFull days spent on low-value work
Drive-time shareDrive hours ÷ paid hours × 100Routes and territories that eat the day

First-time fix rate is defined, with its counting rules, in the glossary entry on first-time fix rate. Aquant, a service software vendor, reports a benchmark of 77% across 161 service organizations and nearly 30 million service events, with top performers at 88% and bottom performers at 60%, and puts failed visits at 25% of total service cost at the median (Aquant, 2026 Field Service Benchmark, February 2026). The sample is drawn from service organizations generally, and the post gives no breakdown for small residential trades, so the figure is a reference point rather than a target for a five-van company.

Revenue per technician turns hours into money and is the one measure that reflects price. Two technicians with the same 65% productivity can invoice very different amounts if one runs maintenance visits and the other runs replacements, so the comparison is made within a job type or across the whole year.

Drive-time share of the paid day

Drive-time share is drive hours divided by paid hours; in the sample week below it is the largest unbilled block, and it is set by dispatch as much as by the technician: the order of the stops, the size of the territory and whether a job is added across town at noon. Because job-to-job travel is hours worked under 29 CFR 785.38, every drive hour is a paid hour that no invoice covers unless the business charges for trips.

The share is measured from the gaps between job clock-ins rather than from the vehicle, because a technician who clocks in on leaving the previous job moves the drive into the job's time and hides it. The fix is a rule, written into the technician's onboarding: clock in on arrival at the address, clock out on leaving it. Vehicle GPS then provides a cross-check, since the van's moving time and the gaps between job clocks should roughly agree.

Sample week for a five-technician company

The week below is a sample: the five technicians, their hours by category, their job counts, their first-visit fixes and their revenue are sample inputs chosen to show the calculations, not measured results. The cost of an unbilled hour uses the BLS median wage for heating, air conditioning and refrigeration mechanics and installers, $29.33 an hour in May 2025 (BLS Occupational Outlook Handbook, modified October 29, 2026), loaded for benefits at the 70.0% wage share of private industry compensation in June 2026 (BLS, Employer Costs for Employee Compensation, released September 9, 2026): $41.90 an hour.

Sample week, hours by category for five technicians (all hours and counts are sample inputs)
TechnicianPaid hoursBillableDriveShop and partsUnbilled return visitsPaperwork and meetings
A40.027.08.52.00.02.5
B40.022.010.53.02.02.5
C40.025.59.02.51.02.0
D40.020.012.03.52.52.0
E40.026.08.02.01.52.5
Team200.0120.548.013.07.011.5
Sample week, measures by technician (computed from the sample inputs)
TechnicianProductivityDrive-time shareJobs per dayFirst-time fix rateRevenueRevenue per paid hour
A67.5%21.3%3.4100.0% (12 of 12)$7,480$187.00
B55.0%26.3%2.680.0% (8 of 10)$5,330$133.25
C63.8%22.5%3.090.9% (10 of 11)$6,450$161.25
D50.0%30.0%2.477.8% (7 of 9)$4,920$123.00
E65.0%20.0%3.291.7% (11 of 12)$6,880$172.00
Team60.25%24.0%2.9288.9% (48 of 54)$31,060$155.30

The team converts 120.5 of 200 paid hours into billable work. The other 79.5 hours cost $3,331.05 at $41.90 an hour, and drive time alone is 48 of them, or $2,011.20, six times the $293.30 spent on the seven hours of unbilled return visits. Drive is the largest single gap in this sample, which puts routing and territory ahead of training as the first lever.

Technician D shows how the measures read together: D's productivity is 50.0%, the lowest, but D's drive share is 30.0%, also the highest, and D's 2.5 return-visit hours sit beside a 77.8% first-time fix rate. A shorter territory that cut D's drive from 12.0 to 8.5 hours, the same as technician A's, would put D at 58.8% before any change in skill. The return visits are a separate question, answered from the parts records and the dispatch notes on each of D's two second trips.

The sample also prices the gap: the team earns $257.76 for each billable hour, so one more billable hour per technician per day, 25 hours across the week, is worth $6,443.98 of revenue at the sample's mix of work. The service technician software guide prices the paperwork share of the same unbilled time.

Technician productivity tracking methods

Each tracking method records a different slice of the day, and the formula can be computed only from the methods that record both job time and paid time.

Technician productivity tracking methods compared
MethodRecordsMisses
Paper or spreadsheet timesheetDaily paid hoursThe split between jobs, driving and shop time
Daily clock-in appPaid hours with start and finish timesTime per job
Job-level clock-insTime against each job; drive is the gap between jobsTime on the job before or after the clock event
Location-stamped clock eventsWhere the phone was at clock-in and clock-outMovement between clock events
Vehicle GPSMoving time, stops and idle timeWhich job the time belonged to
Flat-rate invoicesBook hours sold per jobHours actually taken, without a job clock

Job-level clock-ins are the minimum for the productivity formula, because they give billable hours and leave drive time visible in the gaps. Location stamps add evidence that the clock event happened at the job address, and vehicle GPS adds a cross-check on drive time. Flat-rate invoices add the sold hours that efficiency needs. A company that records only daily timesheets can compute revenue per technician and jobs per day, and nothing else on the list.

Increasing technician productivity: routing, parts, dispatch and paperwork

The levers follow the categories of unbilled time in the sample week, each with its own mechanism.

Routing and territory set the drive-time share. Stops sequenced by geography, technicians assigned to zones, and same-day additions placed with the technician nearest the address shorten the gaps between jobs.

Parts on the van set the return visits that come from missing stock. A job that needs a part not carried becomes two visits, and the second one is unbilled time. Stock counted where it sits, with low-stock warnings, keeps the van's shelves matched to the calls the technician runs.

Dispatch by skill sets the first-time fix rate on work that needs a certification or a specialty. A job sent to a technician who cannot finish it produces a second visit by someone who can.

Information at the door sets the time spent calling the office: the customer's history, the equipment on site, photos from the last visit and the gate code, on the work order before arrival.

Paperwork in the app sets the end-of-day office time: signatures, photos, notes and the invoice captured at the job rather than written up later.

The order of the levers differs by trade: a pest control route is a sequence of short, similar stops, while a repair call becomes two visits when a part or a diagnosis is missing on the first. The technician's phone app is described on the technician app page.

Measurement errors in productivity reports

Symptoms in a productivity report, the mechanism behind each, and the fix
SymptomCauseFix
Productivity above 100%Overlapping job clocks, or job time recorded without a matching payroll clockReject a job clock-in while another job is open
Drive-time share close to zeroTechnicians clock in on leaving the previous job, so the drive is counted as job timeClock in on arrival at the address; cross-check with vehicle GPS
High productivity, low revenue per technicianLong jobs priced below their hours, or one technician holding the low-ticket workCompare within a job type, then read efficiency on the same jobs
First-time fix rate near 100% with callbacks reported by phoneReturn visits entered as new jobs, or a counting window shorter than the callbacksLink a return visit to the original job and state the window
Productivity rises in a month when revenue fallsUnbilled warranty work clocked as billableMark warranty and return visits as non-billable at dispatch

Technician productivity checklist

  1. Write down the definitions of paid hours, billable hours and the first-time fix window before the first report.
  2. Record time against each job, with clock-in on arrival and clock-out on departure.
  3. Flag return visits for the same problem and link them to the original job.
  4. Compute productivity, drive-time share, jobs per day, first-time fix rate and revenue per technician weekly, per technician and for the team.
  5. Read productivity with efficiency on the same jobs before drawing a conclusion about a technician.
  6. Compare technicians within a job type or a territory, not across the whole board.
  7. Act on the largest unbilled category first, which in the sample week was drive time.
  8. Verify the week: billable, drive, shop, return and paperwork hours add up to paid hours for every technician.

Technician performance reports and time tracking in FieldRanger

FieldRanger records the job time the formula needs. Technicians clock in and out with time logged against each job, and each clock-in and clock-out records where the technician was, so hours match job sites; the GPS time tracking app page describes the clock events. The technician performance report shows completion rates, on-time arrivals and productivity by technician, the operations dashboard gives a live view of jobs, technicians and performance, and custom reports are built in a drag-and-drop report builder and can be emailed on a schedule. A first-time fix rate report is built in the custom report builder, and any report downloads as CSV or Excel for the weekly calculation above. The field service reporting software page lists each report.

The levers have matching features. FieldRanger builds each technician's route for the day automatically and sequences stops to cut drive time; skill-based assignment matches jobs to technicians by certification; technicians check parts out of a specific warehouse, with low-stock warnings; and customer notes and job photos sit on the work order. A won HubSpot deal becomes a job with its context carried over, so the technician arrives with what sales learned. Plans are listed on pricing, and Start free trial runs 14 days with no card.

Frequently asked questions

How to measure technician productivity?

Divide billable hours by paid hours for each technician over at least a week, and read the result beside jobs completed per day, first-time fix rate, revenue per technician and drive-time share. Job-level clock-ins are the minimum record the calculation needs.

How to calculate technician productivity?

Billable hours ÷ paid hours × 100, so a technician paid for 40 hours with 26 billable hours on jobs is 65% productive. Job-to-job travel counts as paid hours worked under 29 CFR 785.38, so drive time sits in the denominator.

What is the difference between technician efficiency and productivity?

Productivity divides job hours by paid hours and shows how much of the day reached customers. Efficiency divides sold or book hours by the hours the job took and shows speed: a 1.0-hour flat-rate task done in 0.75 hours is 133.3% efficient.

How to increase technician productivity?

Start with the largest unbilled category in the time records. In the sample week it was drive time, at 24% of paid hours, which routing and smaller territories reduce; return visits respond to parts on the van and dispatch by skill, and office time to paperwork done in the app.

How do dealerships measure technician productivity?

Blackpurl's dealership software documents productivity as hours clocked onto service jobs divided by hours clocked in for payroll, and efficiency as invoiced hours divided by job-clocked hours. Field service companies can use the same two ratios with job clock-ins and flat-rate book hours.

What tracking methods record technician productivity?

Job-level clock-ins record billable hours and leave drive time visible in the gaps between jobs; payroll clocks record paid hours; vehicle GPS cross-checks drive time; and flat-rate invoices record the sold hours that efficiency needs.

In the sample week, technician D's 50.0% is a territory figure before it is a skill figure: 12.0 hours of driving set the ceiling, and 3.5 hours less of it would move D to 58.8% without a single job done faster.

Run field service on HubSpot with FieldRanger

Estimates with e-signature, scheduling and dispatch, a technician mobile app and invoicing, synced to the HubSpot deals and contacts the business already keeps.

Book a demo