Field service technician in hi-vis recording a job on a rugged tablet beside an orange forklift in a workshop

By ten past seven the service manager’s whiteboard is full. Six technicians, eighteen jobs and three breakdowns that came in overnight. Everyone is going to be busy today. That part is never in doubt.

By four o’clock, one technician has spent most of the afternoon in traffic between two sites on opposite sides of town. Another waited an hour and a half at a gatehouse for a permit to work. A third finished early, then drove back to the workshop to collect a part that could have gone out with him that morning.

All six were busy all day. Only some of that day went into fixing forklifts, and by Friday nobody will be able to say how much.

Technician utilisation is about where the hours go

Technician utilisation is often treated as a single number: hours worked against hours available. That number tends to look healthy, because good technicians are rarely idle. The more useful question is what the hours were actually spent on.

A field service day usually breaks down into a handful of buckets: travel, waiting on site, the repair or service itself (often called wrench time), admin and the trips nobody planned, such as collecting parts or going back for a second visit. Each one is a normal part of the job. The trouble starts when the buckets that are not repair work quietly grow and nobody notices.

Busy hides the problem

A technician who spends the day rushing between jobs looks committed, and usually is. But a full day is not proof of a productive one. If two hours went to traffic and another hour to waiting for a supervisor to sign a permit, the customer experienced a slow response and the technician went home tired with less to show for it.

The opposite happens too. A technician who appears to close fewer jobs may simply be the one sent to the difficult ones: the far sites, the awkward access and the machines with a history. Judging people on job counts alone tends to punish the wrong person and reward whoever drew the easy routes.

Travel is a planning decision, not a fact of life

Some travel is unavoidable. A good deal of it is the result of how jobs are handed out. When work is allocated in the order it arrives, technicians crisscross the same area several times a week and pass each other on the highway.

Small changes help. Group planned services by area and by customer, so one visit covers several machines. Leave a little room in each area’s day for breakdowns, rather than pulling someone from the far side of the region. Check whether services due later in the month can be lined up with a site visit that is already booked.

None of this needs anything clever. It needs planned work and outstanding work to be visible in one place when the schedule is drawn up, instead of spread across a whiteboard, a spreadsheet and three inboxes.

Waiting time is usually somebody else’s process

Waiting is the bucket technicians find most frustrating and managers see least. Gate access, inductions, permits, a machine still in use, a supervisor who has to sign before work can start, a part that has not been confirmed.

Recording it changes the conversation. When arrival and start times are captured on each job, patterns appear: the site where the technician always waits at the gate, the customer whose machine is never released on time. That gives the service team something specific to raise with the customer, rather than a general feeling that “that site is slow”.

Admin should happen once, at the job

Paperwork finished at the end of the day, or the end of the week, is time spent twice. The technician recalls the job and writes it up, then someone in the office types it in again. Details go missing on the way, and so does the true picture of how long things took.

Capturing the record on site, while the machine is still in front of the technician, keeps admin short and accurate. It also means the times and work recorded reflect what actually happened, not what someone remembered on Friday afternoon.

Fair workloads need a shared picture

Utilisation conversations go wrong when they feel like surveillance. The aim is not to time every minute of a technician’s day. It is to see where the process is losing them time, and then fix the process.

That works best when technicians and managers look at the same information. If a technician can show that a week of long-distance breakdowns left no room for planned work, the discussion becomes about allocation rather than effort. Workloads can be balanced across the team, and the people who always get the difficult jobs get credit for it.

Where FMC helps show where the day went

FMC is built to make field activity visible without turning technicians into administrators.

The FMC Technician Mobile App gives technicians a clear view of their assigned jobs, priorities and sites, and lets them capture attendance, work completed, time, parts, notes and outstanding actions from the field. FMC Service Management shows which jobs are planned, allocated, in progress, delayed, awaiting action or completed, so planners can see what needs attention before the schedule is set.

For service providers, FMC gives managers greater visibility of technician workloads, assignments, activity and completed work, which makes it easier to share the load fairly. The platform keeps the record. The planning decisions still belong to the people who know the region, the customers and the team.

A simple week-long check

If you want to know where your technicians’ time goes, start small. For one week:

  • Record arrival, start and finish times on every job
  • Note any waiting on site, and the reason for it
  • Flag every unplanned trip, such as fetching parts or a return visit
  • Compare each area’s planned services with the breakdowns that pulled people across the region
  • Sit down with the team at the end of the week and look at the results together

You will probably find one or two sites, habits or scheduling rules that account for a surprising share of the lost hours. Fix those first. Much of the rest tends to sort itself out once everyone can see it.

The whiteboard will still be full at ten past seven. The difference is that more of the day will go into the machines on it.

Measure where the day goes, then plan so more of it goes into the machines.