Skip to content

Field technician routing

Send the wrong technician, and you lose the travel time, the customer’s patience and the fix. Field technician routing sends the right one.

  • Free 30-minute call
  • No commitment
  • You own the code
Typical industries
Field service management, Energy and utilities
Problem type
Routing
You receive
A documented model, run on your data

In short: A field technician scheduling optimisation decides which technician takes which job, when and in what order. It matches each job to the right skills and parts, keeps travel short and meets the response times promised to customers.

The problem

At half past eight, a fault on a gas meter comes in from across town. The nearest technician isn’t certified for gas. The certified one is an hour away, and his van doesn’t carry the spare part the meter needs. You have ten minutes to choose, and the contract says a technician must be on site by noon.

Why the wrong technician costs you three times

A field technician job is a stop with a skill requirement attached. Only a certified gas engineer can touch the meter, and the van has to carry the right part to complete the fix. The arrival also has to meet the SLA, the service-level agreement that sets how fast you must respond. Send the wrong person, and you pay the travel twice, lose goodwill and still haven’t done the job.

Why generic tools send the wrong person

Field technician routing is routing and workforce planning in one problem, and generic tools are built for one or the other. So the usual setup splits the job. A workforce system picks an eligible technician, then a mapping tool plans the route without knowing about certificates or stock. The job goes to a certified technician an hour away. A colleague with the same certificate and the right part in the van is ten minutes from the customer.

What changes

Today, you check certificates in one system, stock in another and the map in a third, then decide. Our model checks skill, stock and SLA for every technician at once and plans the routes in the same step. When an urgent job comes in at ten, the model shows who can take the job without missing another SLA deadline. You confirm the choice and the day carries on.

Field technician scheduling optimisation: what you get

We combine vehicle routing optimisation and replanning during the day with workforce scheduling, the planning of who works when. The model knows your technicians and their certifications, the tools and spare parts in each van, your SLA deadlines and what each job needs. You judge the result on first-time-fix rate, the share of jobs closed on the first visit. Travel time per job, SLAs met and jobs per technician per day count too. We test it on your own jobs and your worst days first, like a storm that cuts power across a region or a morning full of sick calls.

  • A model written around your own field technician routing rules.
  • Results measured in the numbers you already track.
  • It slots into how you already work, and you can check every answer it gives.

A plan that survives the long job

The tightest plan on paper is often the first that no longer works. Job times are estimates, and one repair that runs long pushes every later visit back. So we plan with the times your jobs have taken in the past, for each type of job. Where an SLA deadline is close, we add spare time. Say a boiler service is booked at sixty minutes, but your records show it usually takes eighty. The model plans for eighty.

Working-time rules go in as hard limits too. A technician who’s free on the calendar may already be close to their maximum weekly hours. The model knows that before it assigns the job, so you don’t find out at five o’clock. What you get is a plan that still works at three in the afternoon.

How it works

We write your depots, your customers, your fleet and your rules into one model. You get the routes that cost the least and keep every rule. You still have the last word: you check the result and send it out.

Skill-matched dispatch

The most important rule: the technician has to match the job. Every job lists the certifications it needs. Gas work needs a registered gas engineer. Other jobs need an electrician or training for work in confined spaces. Every job also lists its tools, such as an analyser, a crane or a pressure tester. And it lists the exact spare part the van has to carry.

A technician is only eligible if they meet all three. Skill matched dispatch optimisation checks eligibility before it plans any route. A route can look efficient in kilometres and still be impossible because the van lacks one part. So the model checks who is eligible and plans the routes in the same step.

SLA routing: travel time versus promises

Once the model knows who is eligible, it balances two things. The first is travel time: the model gives jobs to eligible technicians nearby and puts the jobs in an order that keeps driving short. The second is the SLA window, the measure your service is judged on. That can be a same-day repair promise, a site that only allows maintenance at night, or a priority fault due within four hours. The model treats each SLA as a hard time window and will trade a few kilometres for an on-time arrival.

Emergencies and multi-day jobs

During the day, a priority job lands, another overruns, and a technician calls in sick mid-morning. The model then replans the routes that are already running. It checks which eligible technician still has the time and the spare parts for the new job. The rest of the plan stays unchanged.

Not every job fits in one day, either. Some need several visits: first a survey, then the installation, then commissioning. Commissioning is the first start-up and the handover to the customer. Multi-day planning spreads them across consecutive days and keeps the same technician where continuity matters.

Field service, energy and utilities

Field service management, the planning of engineers who work at customer sites, is the core case. The certificate and the spare part decide whether the job is done on the first visit or needs a second one. Energy and utility companies depend on this most. For meter work, grid maintenance and outages, a technician must be on site within the SLA deadline. And that technician must be trained to work on equipment that is under power. Heating and air conditioning (HVAC) teams and telecoms crews need the same mix of skill, stock and schedule.

Common questions.

Something else? Ask us directly.

Plan with realistic job times, and put spare time where a delay would hurt most. Take the time each type of job took in the past, not the time that was booked. Put the spare time before visits with a tight SLA, the response time you promised the customer. Don’t spread it evenly across the day. When a job still overruns, emergency replanning moves the later visits to colleagues who can take them, and the rest of the plan stays put.

It has to, or the plan won’t work on the first morning. Each job needs a set of skills. Each technician has working hours, holidays and a weekly limit of hours, part of which is already used. A good model holds all of it as hard rules and plans routes inside them. Being free on the calendar isn’t the same as being allowed to work another four hours.

From your own records. Job durations vary by job type, by site and sometimes by technician. We estimate them from past jobs and update them as new data comes in. Correct job times often matter more than a slightly shorter route. A perfect sequence with wrong job times is already late by mid-morning.

Sometimes it can, and if that’s the case, we’ll tell you. Standard software is built for an average operation, though. Yours runs on its own rules: your contracts, your exceptions, the things you know by heart. A custom model writes those rules in, and that’s where the better plan comes from.

You don’t need either to start. We build the model from the data you’ve already got, even if it lives in three spreadsheets and one person’s head. You get a system you run yourself. We train your team until they no longer need us.

You see a first result with the prototype, before you commit to anything bigger. We start with a free 30-minute call about your operation and the model that would fit it. Then we build a working prototype and run it on your numbers.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go