A technician can run as many calls as fit in the paid day after fixed non-job time, divided by the average time on site plus the average drive between calls. For a typical residential service day with an hour or more on site per call, that usually works out to a small single-digit number, and the drive is what separates four from six.
Published "calls per day" figures vary because trades, territories and job types vary. A drain tech in a dense city and an HVAC tech covering a rural county will never match. Use your own inputs.
The formula
With paid hours per day H, fixed non-job time N (morning load-out, supply house, lunch, end-of-day paperwork), average time on site per call T and average drive between calls D:
Calls per day = (H − N) ÷ (T + D)
Round down. A fraction of a call is a call that runs into overtime or slips to tomorrow.
Cutting the average drive from 36 to 18 minutes adds a whole call per day without adding an hour or rushing the work. The jobs per day calculator runs this with your numbers.
Measuring the three inputs
Time on site, T. Take arrival and completion timestamps from your job records for a few weeks. Use the median by job type, not the overall average, since a tune-up and a diagnosis are different jobs. See job duration estimate.
Drive between calls, D. Take the gap from one call's completion to the next call's arrival. That gap is drive plus idle. Compare it to a realistic drive for those two addresses at that time of day; the rest is slack. The windshield time post shows how.
Fixed non-job time, N. The parts of the day that happen no matter how many calls there are. Supply house runs are often the largest piece, and the easiest to cut with better truck stock.
What changes the answer by trade and job type
Long jobs. Installs, replacements and repipes often take half a day or more. A tech on installs runs one or two jobs a day and that's correct.
Short, repeatable jobs. Maintenance visits, pest control and some drain work run short. D becomes a large share of each call, so density matters even more.
Diagnosis. Diagnostic calls vary a lot. A tech who sometimes finds a quick fix and sometimes a full afternoon problem needs slack in the day, or the calls after it run late.
Emergencies. A same-day emergency slotted into a full day knocks the rest of the day back. Holding some room for them lowers the planned count but keeps the day on time.
Why booking order decides the drive
Most of D is decided when jobs are booked, not when the day is dispatched. If calls are booked in the order the phone rings, the truck zig-zags. Reordering the route afterward helps a little, but it can't fix a 9:00 call downtown and a 10:00 call across the county. That is why planning the dispatch day around drive time starts at booking.
CrewLink's booking page offers only start times a qualified tech can actually make, computed from where the truck will be at that hour, the previous job, rather than from the shop. Over time that keeps D lower without anyone hand-sorting the board.
Don't plan to the maximum
If the formula says five, planning five every day leaves no room for a job that runs long or a part that isn't on the truck. Most shops plan below the maximum and use the room for same-day work. The gap between what is booked and what a tech actually does is covered in jobs per day per technician.
What to take away
- Calls per day = (paid hours − fixed non-job time) ÷ (time on site + drive between calls).
- Measure each input from job timestamps, by job type, not from the schedule.
- Cutting the average drive between calls often adds a full call per day.
- Plan below the maximum so long jobs and emergencies don't wreck the afternoon.
Common questions
How many service calls should an HVAC tech run per day?
It depends on the mix. Maintenance and repair days often fit several calls, install days one or two. Run the formula with your own time on site and drive for each job type.
How do I increase calls per day without overworking techs?
Cut the drive between calls by grouping work by area, reduce supply house runs with better truck stock, and shorten setup with clear job notes. Each one adds time for calls without lengthening the day.
Is calls per day a good KPI for technicians?
On its own it rewards rushing and cherry-picking short jobs. Pair it with first-time fix rate, callback rate and revenue per tech so a high count isn't hiding repeat visits.
Why do my techs run fewer calls than the schedule shows?
Usually because the schedule counts blocks, not drive. A two-hour block can hold 40 minutes of driving. Measure arrival and completion times to see the real split.