Ask most field service owners where their profit disappears to and they'll say fuel, wages, or the eye-watering price of parts. Almost nobody says the real answer: the hours their engineers spend sat in the van, driving between jobs that were never sensibly grouped in the first place.

And that drive time? Nobody pays for it. The customer isn't paying, the engineer is still on the clock, and the van's still guzzling diesel and racking up the miles. It's one of the biggest costs in the whole business, and it's completely invisible, because it never shows up on an invoice. And unlike fuel prices or wages, which you can't do much about, this one is almost entirely in your hands.

The fix has a name: route density. It just means how tightly you pack the work into each engineer's day, so they spend more time actually doing paid jobs and less time getting to them. Tighten it up and you can get through more work with the same engineers, the same vans, and the same hours. There aren't many levers in this business that hand you extra capacity without costing you a penny more. This is one of them.

The tax nobody's counting

The reason this problem is so sneaky is that drive time hides in plain sight. It doesn't land on a bill anywhere, so it never gets the hard stare a big parts invoice would.

And it's a bigger number than you'd think. McKinsey has found that trimming travel time frees up field hours and lets technicians get through more jobs, and that shaving even an hour of daily drive time off can add one or two extra jobs to the schedule. Research from the Aberdeen Group and the TSIA goes further, reckoning that field service firms running on manual scheduling lose somewhere between 20 and 40 percent of their potential daily revenue to inefficiency, and a big chunk of that is engineers stuck behind the wheel instead of on the tools. That's a fifth to two-fifths of what you could be earning, gone, most of it dressed up as a perfectly normal working day.

Now flip it round. If drive time is costing you that much, clawing even a bit of it back is real money in your pocket. Get an hour a day back per engineer and you've potentially got another job or two done, per person, every day. No new hire. No second van. No longer hours. Same team, more work out the door. That's why route density isn't a nice-to-have bit of admin tidiness. It's a proper margin lever.

Your routes are made or broken before anyone starts the engine

This is the bit that flips how most people think about it. When engineers are clocking up daft miles, the instinct is to blame the driving, or the sat-nav, or the traffic. But most of those wasted miles were baked in the moment the day was planned. If the schedule fires someone to the far end of the patch at nine, drags them back past the yard at eleven, then sends them all the way out again at two, no sat-nav on earth is going to rescue that. The damage was done at the whiteboard.

Which is actually good news, because it means the fix lives in the office, not the cab. You don't need to nag anyone to drive faster or skip their lunch. You need to plan the day a bit smarter. And that's something any business can start doing tomorrow, whatever kit you've got.

What actually tightens up a route

A few simple habits do most of the heavy lifting here, and none of them needs a big spend to get going.

Start with grouping jobs by area. Instead of booking work in the order the phone rings, cluster it by location so an engineer spends the day working one tight patch rather than zig-zagging across the whole county. Even roughly carving your area into zones and trying to fill a day inside one zone will knock a serious dent in the driving.

Then think about the order you do them in. Once the jobs are grouped, the sequence still matters. A run that flows across an area, rather than doubling back on itself like a dog chasing its tail, saves miles on every single hop between jobs. Handy rule of thumb: well-run operations tend to keep travel under about twenty minutes between jobs. If you're regularly north of thirty, it's the sequencing that needs a look, not the driver.

Next, guard your good routes from getting blown apart by emergencies. Reactive work is the natural enemy of a tidy schedule, because one urgent call on the wrong side of the patch can detonate an otherwise perfect day. You can't make emergencies disappear, but you can soften the blow: leave a bit of deliberate slack in the day for them, batch your non-urgent jobs so the plan isn't already hanging by a thread, and lean on predictable work where you can. A solid base of planned preventive maintenance visits, booked ahead and grouped by area, gives you a backbone of nice dense routes that the odd emergency slots around instead of smashing to bits.

Last one, and it's easy to miss in a chat about routing: get the job done right the first time. A job you have to go back to is a whole extra trip your lovely tight schedule never planned for. Every avoidable return visit is drive time you're paying for twice, so nailing it on the first go protects not just that job but the shape of your whole week.

It all ties together

Route density doesn't sit off in its own corner. Pull this lever and a few others move with it, which is what makes it such a good one to get right.

The obvious one is fuel. Fewer, shorter trips means a smaller bill at the pump, so if fuel costs are chewing into your margins, tighter routing is one of the best ways to spend less without dropping a single job. Fewer miles means less wear on the vans too, so they need servicing and replacing less often.

It feeds straight into profit, as well. Turning wasted drive time into completed jobs is about as close to pure margin as you'll find, because the engineer, the van, the overhead, it's all already there and already paid for. Route density is one of the cleanest ways of boosting profitability without touching your prices, which means no awkward conversations with customers about why the bill's gone up.

And it takes some of the sting out of the skills shortage. When good engineers are like gold dust and cost a fortune to keep hold of, squeezing more productive hours out of the ones you've already got beats trying to find another one. Lift each engineer's jobs-per-day through better density and you've basically added a pair of hands without hiring anyone, which is exactly the hole the skills shortage keeps digging.

Where to start

You don't have to rip everything up and start again. Just get a rough handle on the size of the problem first. Over a week or two, have a look at how much of each engineer's day is driving versus actually being on site. Most owners who do this for the first time get a bit of a shock, and that shock is the whole point, because it shows you how much capacity is sitting there locked up in the schedule.

After that, the first real move is dead simple: stop booking jobs purely in the order they land and start grouping them by area, even in a basic way. Zone your patch, try to keep a day's work inside one zone, sequence each day so it flows instead of criss-crossing, and leave a bit of breathing room for the reactive stuff you know is coming. Keep tidy records of every job and where it is, so the info you need to plan tighter days is right there rather than scattered across three notebooks and someone's memory.

None of this asks your engineers to graft any harder. It just asks the office to plan a bit smarter, and the payoff drops straight onto the bottom line.

Key Takeaways

Route density might be the most overlooked lever in the whole business, purely because the cost it goes after, unpaid drive time, never shows up on an invoice and so almost never gets questioned. But the numbers don't lie: it's one of the biggest drains on productivity going, and clawing back even a slice of it can free up close to a whole extra job per engineer per day.

Group the work by area, sequence each day so it flows instead of backtracking, protect your routes from reactive chaos, and cut out the return visits that punch holes in the plan. Do that and you'll get more done with the same people and the same vans, spend less on fuel, and turn hours you were already paying for into money you were basically leaving on the road. When capacity is pricey and margins are tight, that's about as close to free money as this game gets.

FAQs

What is route density in field service?

Route density is how tightly the jobs on an engineer's day are packed together geographically. High density means an engineer works a tight cluster of nearby jobs and spends most of the day actually working. Low density means they're crossing the whole service area between jobs, burning hours and fuel on driving that nobody pays for. The denser the route, the more paid work gets done in the same day with the same people.

Why does drive time matter so much if I'm already paying my engineers anyway?

That's exactly why it matters. You're paying for the whole day whether the engineer is fixing something or sat in traffic, so every hour lost to driving is an hour of wages, fuel, and van wear producing zero revenue. It's a cost you're carrying without earning anything back for it. Reducing it means you get more billable work out of the same wage bill, rather than paying people to drive around.

How do I actually measure my route density or drive time?

Start rough. Over a week or two, look at how much of each engineer's day is spent driving versus on site, even a ballpark split is revealing. A useful benchmark is average travel time between jobs: well-run operations tend to keep it under about twenty minutes, and if you're regularly over thirty, your scheduling probably needs attention rather than your drivers. You don't need fancy software to start; you just need to stop ignoring the number.

Isn't this just about buying route optimisation software?

No, and that's the key point. Most wasted miles are decided when the day is scheduled, not when the engineer is driving, so the biggest gains come from how you group and sequence work in the office. Software can help once you're doing the basics well, but plenty of the improvement is available to any business willing to zone its patch and plan days that flow rather than criss-cross. The habit matters more than the tool.

What's the quickest win to improve route density?

Stop booking jobs purely in the order the calls come in. Group them by area instead, so each engineer works a tight patch on a given day rather than crossing the whole territory. That single change, even done loosely by zoning your area into a few regions, tends to cut drive time faster than anything else, and it costs nothing to try.