The benchmark for residential field service is 4-8 jobs per technician per day, with wide variation by trade and job type. HVAC maintenance tune-ups average 6-8 jobs per day. Plumbing repair averages 4-6. Electrical installations and new construction run 1-2 per day (or multi-day projects). Route efficiency and job mix significantly affect where your team lands.
Jobs-per-day is one of the most commonly tracked field service metrics — and one of the most easily misused. Comparing a plumber doing complex drain replacements to one doing simple faucet swaps, or an HVAC tech doing tune-ups versus compressor replacements, produces meaningless numbers. The right benchmark is jobs-per-day within the same job category.
Jobs Per Day Benchmarks by Trade and Job Type
| Trade / Job Type | Jobs/Day Range | Notes |
|---|---|---|
| HVAC maintenance (tune-up) | 6-8 | High volume, predictable duration |
| HVAC repair (diagnostic + repair) | 4-6 | Variable duration, parts dependency |
| Plumbing service (drain, faucet, toilet) | 4-6 | Moderate complexity |
| Plumbing emergency (pipe burst, leak) | 2-4 | Higher complexity, longer on-site time |
| Electrical service (outlets, panels, fixtures) | 4-7 | Varies widely by job |
| Electrical new construction | 1-2 | Multi-day jobs counted differently |
| Appliance repair | 5-8 | Short jobs, high volume |
| Commercial HVAC service | 2-4 | Larger systems, longer diagnostic |
What Limits Jobs Per Day
Drive time is the biggest variable outside of job complexity. A technician spending 2.5 hours per day driving is doing 28% of their working day non-billable. Route optimization that cuts drive time to 1.5 hours frees 45-60 minutes — roughly one additional job per day.
Job duration variability — when a repair unexpectedly takes 3 hours instead of 1, it compresses the rest of the day. Better pre-visit information (equipment details, symptom history) reduces diagnostic time and narrows duration uncertainty.
Parts and return visits — a technician who needs to make a parts run or schedule a return visit has permanently lost productive capacity for that slot.
Admin and paperwork — manual invoicing, paper job cards, and phone calls to dispatch consume 30-60 minutes per technician per day for teams without a mobile app. Digitizing these recovers that time directly.
Using Jobs-Per-Day Correctly
Jobs-per-day should be tracked alongside:
- Average ticket value — a tech doing 8 jobs at $125 average generates $1,000/day. A tech doing 5 jobs at $350 average generates $1,750/day. Revenue per tech is the real metric.
- First-time fix rate — high jobs-per-day with low FTFR means a lot of return visits hiding in the numbers.
- Technician utilization rate — percentage of scheduled hours that are billable (see the related guide).
A tech consistently below the benchmark warrants investigation: is it routing, job type mix, skill gaps, or performance?
FAQ
Should I set jobs-per-day targets for technicians?
Targets are useful as benchmarks, not as quotas. Pressure to hit job counts drives techs to rush, skip thorough diagnosis, and make premature repairs — all of which increase callbacks and damage customer relationships. Use jobs-per-day as a team average to identify scheduling and routing inefficiencies, not as individual performance pressure.
How does seasonal demand affect jobs-per-day benchmarks?
Significantly. During peak HVAC season (summer cooling, winter heating), job count per day may actually drop because each job takes longer — systems under heavy use fail in more complex ways, and demand creates longer time windows between calls as techs navigate heavy traffic and back-to-back emergencies. Peak season productivity is better measured in revenue per day than job count.
See the technician utilization rate guide for a complementary performance metric, or learn how route optimization reduces drive time to add capacity without adding headcount.