What service leaders should track before adding technicians

Before adding technicians, service leaders should establish how much of their current technician time goes to productive work. Travel, repeat visits, jobs that weren’t ready to dispatch and slow manual planning all consume capacity, yet on a dispatch board they look like demand. If those losses are high, hiring adds cost without removing the bottleneck. 

That doesn’t make hiring the wrong call. It means the decision should rest on operational data, not on how full the schedule looks this month. This article covers four measures that show whether you have a real capacity gap, and when more technicians or contractors are the right answer.

Does a full schedule mean you need more technicians? 

Not necessarily. A full schedule shows booked time, not productive time. Field service capacity planning is the process of matching available technician hours, skills and locations to the work that needs doing within agreed SLAs. 

Two kinds of demand fill a technician’s day. Productive demand is the work customers actually need: installations, genuine faults, planned maintenance and onsite incidents. Failure demand is work the operation creates for itself: return visits, missed appointments and jobs reopened because a part, approval or piece of information was missing. Both take up slots in the same way, so hiring against a full board can mean hiring people to make avoidable trips. 

That matters because skilled field staff are hard to find. The European Labour Authority’s report on labour shortages and surpluses in Europe found that shortages are most common in trades and other roles needing occupation-specific skills. 

Four measures to review before approving new headcount 

1. How much technician time is spent on productive work? 

Productive utilization is the share of paid technician hours spent working on site. Unlike a blended utilization rate, it doesn’t count travel, waiting, admin or idle time as “busy”. 

An 80% utilization rate that includes 30% driving is not an 80% productive workforce. When travel per completed job rises, the usual causes are outdated territories, appointments booked without regard to location or urgent jobs pulling technicians across regions. Another hire in the same area splits the driving; it doesn’t remove it. 

2. How much of the workload is repeat or failed visits? 

Count every visit that didn’t close the job, then group it by cause: wrong skill, missing part, no site access, customer not present or incomplete ticket information. Each cause has a different owner and a different fix. We cover those fixes in how to reduce repeat visits and improve first-time fix rates. 

3. How much of the backlog is ready to dispatch? 

Backlog size says little on its own. Split it into three groups: 

• Ready: information, parts and approvals are in place. 

• Blocked: waiting on parts, customer confirmation, site permissions or an upstream handoff. 

• Stale or duplicate: tickets that should be closed, merged or re-qualified. 

If a large share is blocked, more technicians won’t move it. The constraint sits in procurement, customer contact or the systems that create the work order in the first place, such as the service desk or order management. 

4. Were SLA breaches caused by missing people or late planning? 

For each breached job, ask whether a qualified technician was available within reasonable range but wasn’t assigned in time. If so, the capacity existed and the gap was in planning. If breaches cluster in one region or around one certification, a targeted hire or cross-training fits better than general headcount. 

Dispatcher workload is often the hidden cause. A technician who finishes at 13:30 and waits for a call because nobody had time to refill the afternoon is lost capacity that no hire will recover. Similarly, when an IT service provider’s tickets reach dispatch without the device model or part number, assignment waits for a call back to the service desk. Fixing that handoff closes more breaches than another engineer would. 

What each measure usually tells you 

When is hiring more technicians the right decision? 

Hiring is the right decision when productive demand consistently exceeds productive capacity after avoidable losses have been addressed. That usually means demand has grown steadily for several quarters, travel and rework are already under control, or the team lacks a skill or certification that SLA breaches keep pointing to. 

For a defined peak, such as a rollout project or a new managed-services contract, contractors often fit better than permanent hires. The trade-off is coordination: without visibility of contractor availability, skills and job status, a partner network can add dispatcher workload rather than relieve it. Global IT service provider Hemmersbach addressed this by planning its partner network in the same system as its own engineers, and reports a productivity increase of around 30%. 

How FSM software helps separate a capacity gap from a planning gap 

Field service management software records status timestamps, visit outcomes and failure reasons as work happens, so the four measures come from job records rather than estimates. 

It also acts on them. Fieldcode’s automated scheduling and dispatching assigns jobs based on skills, location, availability and SLA deadlines, so when a technician finishes early, the next eligible job can be assigned without a dispatcher rebuilding the board. Published customer results show the effect. HP reduced drive time by 30%, eliminated technician overbookings and, by making better use of its own engineers, relied less on external partners, cutting annual spending by 10%, around $4 million. IT infrastructure provider Braeriach reduced travel and idle time by 20% and improved its first-time fix rate by 25%. 

Automation depends on accurate skills, parts and SLA data, and it doesn’t decide whether to hire. That stays a leadership decision; the software makes the evidence clearer. 

Hire for the gap you can prove 

A busy schedule is a reason to look closer, not a hiring decision on its own. Once you know how much technician time goes to travel, rework, blocked jobs and late assignment, you can tell whether you’re short of people or short of planning, and hire for the skills and areas that genuinely need it. 

To see how Fieldcode helps you plan capacity around the team you already have, book a personalized demo.