The Hours That Disappear Between Jobs

Ask any field operations manager where the day goes and they'll point to the same place: the gaps. Not the jobs themselves. The time between them.

A technician completes a meter exchange in a single postcode. The next job is forty minutes away. Nobody flagged that when the rota was built. He sits in the van, waiting for a call that takes twelve minutes to come through. By the time he's on the road, the morning has a hole in it. Multiply that across a team of fifty engineers and you're not looking at lost minutes. You're looking at lost shifts.

What the Rota Actually Shows

When you pull the data from a utility field operation and look at it honestly, the pattern is consistent. The lost time isn't in one place. It's spread across the day in small chunks that don't get counted individually because no single gap is big enough to flag.

Travel time is the obvious one. Jobs booked without reference to where the previous job sits, or where the next one is, add distance that nobody planned for. That distance costs fuel. It also costs capacity, because an engineer who's driving isn't installing.

Then there's the time spent waiting for information. The job sheet that wasn't updated before the engineer arrived. The customer who wasn't told the appointment window. The part that was logged as available but wasn't at the van. Each of these produces a call to the office, a delay on site, or a wasted visit. Wasted visits are the worst version of this problem because you've spent the travel time and you've got nothing to show for it.

Dispatch lag is the third culprit. When a job finishes earlier than planned and the back office doesn't know in real time, the engineer sits idle. There's no mechanism to pull forward the next appointment or slot in a nearby job. The rota was built that morning and it doesn't flex.

Why Traditional Scheduling Builds These Gaps In

Most utility operations still run rotas that were built on a combination of spreadsheets, experience, and phone calls. A coordinator puts jobs together based on geography, rough availability, and what they know about each engineer. That knowledge is valuable, but it doesn't scale.

When you're running a team of twenty engineers in one region, an experienced coordinator can hold the picture in their head. When you're running two hundred engineers across multiple regions, the picture is too big for any one person to hold. Jobs get clustered badly. Travel time isn't calculated, it's estimated. Changes during the day don't ripple through the rota, they get handled manually, one call at a time.

The rota data tells you what happened after the fact. What most operations are missing is a system that uses that data to change what happens next.

What Changes When the Data Works in Real Time

Reach gives field coordinators visibility of every live job, every engineer's location, and every gap in the day as it opens up. When a job finishes early, the system can identify the next closest suitable job and prompt the coordinator to move it forward. When a job runs over, the rest of the day adjusts.

The scheduling logic accounts for travel time when jobs are assigned, so the rota isn't built on optimistic assumptions about how long it takes to cross a city. Engineers are matched to jobs based on where they are, what certifications they hold, and what stock they're carrying. That last point matters more than it sounds. Sending an engineer to a job they can't complete because the right part isn't in their van is a wasted visit, and wasted visits are expensive.

The mobile app means engineers have the job details before they arrive and can update progress without calling in. The back office sees the update the moment it happens. That connection between the field and the office is what closes the dispatch lag. There's no twelve-minute wait for information that already exists.

Our clients have seen measurable reductions in travel time and aborted visits since moving to Reach. Those reductions compound. Fewer wasted visits mean more completed jobs in the same number of working hours.

The Takeaway

The hours that disappear between jobs aren't invisible. They're in the rota data, if you know where to look. Poorly sequenced travel. Dispatch lag. Wasted visits caused by missing information or the wrong stock. These aren't edge cases. They're structural, and they repeat every day.

Fixing them isn't about working harder. It's about giving coordinators the right tools and giving the rota the ability to flex when the day changes.