Why Technician Productivity Is a Revenue Problem, Not Just an Efficiency Problem
Most field service business owners track revenue, expenses, and maybe job count. Very few track what drives those numbers: how much of each technician's day is actually generating revenue, and what's eating the rest. The gap between a technician who generates $800/day and one who generates $1,100/day — same wages, same tools, same market — is almost entirely explained by measurable productivity factors you can identify and improve.
The Core Productivity Metrics
| Metric | What It Measures | How to Calculate | Target |
|---|---|---|---|
| Jobs per day | Throughput | Total jobs completed ÷ days worked | 4–7 for small jobs; 2–3 for large jobs |
| Billable utilization | Revenue-generating time % | Billable hours ÷ total work hours | 70–80% target |
| Revenue per technician per day | Direct revenue generation | Total revenue ÷ technician days | Benchmark against your highest performer |
| First-time fix rate | Job quality / callbacks | Jobs fixed first visit ÷ total jobs | 90%+ is best-in-class |
| Drive time % | Non-billable time | Drive hours ÷ total work hours | Under 20% is strong; over 30% is a routing issue |
The Billable Utilization Gap
In a typical 8-hour workday for a field technician, here's where time often goes:
- Actual billable work: 4.5–5.5 hours
- Drive time between jobs: 1–2 hours
- Admin tasks (paper invoices, text-based communication, finding addresses): 30–60 minutes
- Parts runs or supplier trips: 30–90 minutes on days it happens
- Miscellaneous delays (no-shows, late customers, equipment issues): 30–60 minutes
The biggest leverage points are almost always admin time (solved by mobile software) and parts runs (solved by better stocking and planning the night before).
How to Improve Productivity Without Micromanaging
- Optimize routing the evening before: Group jobs by geography so drive time is minimized — this alone can add 1–2 billable jobs per week per tech
- Pre-load the truck the night before: Common parts on the truck means no supplier runs during working hours
- Mobile job management: Tech completes job notes, photos, and invoice on-site so there's no end-of-day admin backlog
- Clear job scope before dispatch: A well-scoped job takes less time than one where the tech has to gather information on arrival
- Track and share results transparently: Show each technician their own performance metrics weekly — most people naturally compete with their own previous performance when they can see it
First-Time Fix Rate: The Hidden Margin Killer
A callback costs you roughly 1–2× the original job in labor: travel time back, diagnostic time, and repair time — without additional revenue. Most callbacks trace back to a handful of root causes:
- Incomplete diagnosis on first visit
- Wrong part ordered due to insufficient notes
- Repair covered a symptom without addressing the root cause
- Inadequate post-repair testing
Build a pre-departure checklist for each service type: what to verify before leaving a job. This single process improvement consistently raises first-time fix rates.
Use Fieldbase to track jobs per technician, revenue per day, and first-time fix rates so you can identify where the gaps are — and have specific conversations rather than general ones.
Key Takeaways
- Track billable utilization — most service businesses are surprised how much non-billable time exists in a typical day
- Route optimization the night before is the highest-leverage single productivity improvement
- Admin time and parts runs are the most common non-billable time sinks — mobile software and pre-stocked trucks solve both
- High callback rates are a margin problem — build pre-departure checklists to raise first-time fix rates
- Share individual metrics with each technician — transparent performance data is a natural motivator