Workforce and Labor

How to Size a Field Service Team From Ticket Volume

Ticket count divided by tickets per technician is the calculation everyone runs and it is wrong in a specific way. Demand arrives unevenly, and staffing to the average guarantees failing the peak.

Sizing a service team looks like a division problem and behaves like a queueing problem. The division gives you a floor: total demand hours divided by productive hours per technician. What it cannot give you is the answer, because service demand does not arrive smoothly and a team staffed to the monthly average will miss its response commitments in every above-average week while sitting idle in the others.

The floor calculation

Take 420 tickets a month at an average of 3.2 hours each including travel and write-up, which is 1,344 demand hours. Against roughly 110 genuinely productive hours per technician per month, that is 12.2 technicians as an absolute floor. Apply a peak factor of 1.2 to cover arrival variability and the honest figure is nearer 14.7, which rounds to 15. The productive-hours figure is the one to derive from your own utilization decomposition rather than assume.

Average handle time hides three different jobs

A single average handle time across all ticket types produces a plausible model that fails in practice, because a preventive maintenance visit, an emergency breakdown, and an installation are different jobs with different durations and different travel patterns. Segment by ticket type, compute demand hours per segment, and sum. The extra effort is an afternoon and it surfaces the case where a small number of long emergency jobs consume the capacity the model allocated to routine work.

Staffing to the average is staffing to a month that never actually occurs. Demand arrives in weeks, and the weeks are not alike.

Skills constrain more than headcount does

Total capacity assumes any technician can take any ticket. In practice certifications, product training, and security clearances partition the team, and a ticket that only two people can serve is constrained by those two regardless of how many technicians are idle. Model capacity by skill group, and the answer usually shifts from hiring to cross-training, which is faster and cheaper. This is also where the ramp cost of a new hire matters most: adding a body does not add capacity for months on the tickets that need the scarce skill.

First-time fix is a capacity multiplier

Every ticket that requires a return visit consumes its handle time twice and its travel twice. Improving first-time fix therefore raises effective capacity without touching headcount, and it does so on the most expensive tickets. Before approving an additional technician, check the return-visit rate: if a meaningful share of tickets are repeats caused by parts availability or diagnostic gaps, the cheaper capacity is in the van stock or the diagnostic process rather than on the payroll.

Use the first time fix rate calculator to see how much capacity repeat visits are consuming. Check first-time fix

Published 2026-08-08.