Field service workforce management
In a contact centre, the agent is at the desk and the work comes to them. In field service, the worker travels to the work — and travel time is unproductive, geography-dependent, and often the single largest non-productive part of the day. Capacity is jobs-per-day, not contacts-per-hour, and travel is what makes or breaks it.
Why travel time changes everything
A desk-based queuing model answers "how many seated workers handle work that arrives?". Field service answers a different question: "how many jobs fit into a day once you subtract travel between them?". Travel is unproductive, geography-dependent, and frequently 20–40% of the working day — and it is completely invisible in a naive "jobs × duration" capacity sum. Two engineers with identical skills and job mixes can have very different daily capacity simply because one works a dense urban patch and the other a sparse rural one. So field capacity is planned bottom-up from job duration plus inter-job travel, with territory design and routing as first-order levers — none of which a contact-centre queuing model addresses.
Five factors that drive field service capacity
Travel time
Why it matters
Unproductive time between jobs, often 20–40% of the working day. It is the single biggest determinant of how many jobs an engineer completes, and it is invisible in a naive 'jobs × duration' capacity calculation.
Planning lever
Cluster jobs geographically, sequence them to minimise total travel, and plan capacity on jobs-per-day net of realistic travel — never on job duration alone.
Territory & geography
Why it matters
A dense urban patch yields far more jobs-per-day than a sparse rural one for the same worker, because travel between jobs is shorter. Identical headcount produces very different capacity across territories.
Planning lever
Design territories to balance workload AND travel, not just job counts. Plan rural and urban capacity with different jobs-per-day assumptions — a single blended figure misstates both.
Job duration variability
Why it matters
Field jobs vary far more than contact AHT — a job booked for an hour may take 30 minutes or three hours depending on what's found on site. Overruns cascade through the day's schedule just like appointment overruns.
Planning lever
Use realistic duration distributions (not optimistic point estimates), build in buffer, and decide how overruns are handled (push later jobs, reassign, or roll to another day).
Skill & parts matching
Why it matters
A job needs the right-skilled engineer carrying the right parts. A mismatch means a wasted visit and a repeat trip — doubling the travel and halving effective capacity for that job.
Planning lever
Match skills and parts to jobs at planning time, not on the day. First-time-fix rate is the field-service equivalent of FCR — every failed first visit is roughly a doubling of cost for that job.
Demand type: booked vs. reactive
Why it matters
Planned/preventive jobs can be scheduled efficiently into routes; reactive/emergency jobs (breakdowns, SLAs) arrive unpredictably and must be slotted in, disrupting the planned route and adding travel.
Planning lever
Reserve buffer capacity for reactive work (the field equivalent of an intraday queue buffer), and plan the booked work around it rather than filling every slot — a fully-booked day cannot absorb an emergency.
Jobs-per-day capacity: a worked illustration
Jobs/day = productive hours/day ÷ (avg job duration + avg travel per job)
Same engineer, same job duration — but the urban territory yields ~35% more jobs per day than the rural one, purely from shorter travel. A capacity plan that ignores travel (7 ÷ 1.0 = 7 jobs/day) overstates capacity by 40–90% and guarantees a backlog. This is the field-service equivalent of staffing from talk time and forgetting wrap.
Field service WFM questions
Why can't you use contact centre staffing models for a field service workforce?
Because the defining constraint is different. In a contact centre the agent sits at a desk and work comes to them, so the model (Erlang C) is about handling arriving work. In field service the worker travels to the work, and travel time between jobs is unproductive and depends on geography, job density, and routing. A field day is 'how many jobs fit once you subtract travel', not 'how many per hour at a desk'. Two identically-skilled engineers can have very different daily capacity purely from urban vs rural travel. So field capacity is jobs-per-day, planned from job duration plus inter-job travel, with territory and routing as first-order levers — none of which a queuing model addresses. The closest contact-centre analogue is appointment-based planning (booking jobs into capacity), but with travel as a dominant extra cost between every job.
Related guides
Appointment-based demand WFM
Booking work into capacity — the nearest analogue
Staffing ratios
Ratio-based staffing across contexts
First call resolution
First-time-fix is the field equivalent
Capacity buffer planning
Reserving capacity for reactive work
Staffing models guide
Matching the model to the work type
Warehouse staffing
Another non-queue operational context
Headcount calculator
Total FTE from field service volume and job duration
Productive capacity calculator
Productive hours after travel, admin, and training time