When the Van Turns Up and the Stock Doesn't

There's a particular kind of bad day in field operations. The engineer arrives on site. The job is booked, the customer is in, the appointment window is met. Then it becomes clear the right meter, the right fuse gear, or the right bracket didn't make it onto the van. The job can't be completed. The engineer drives away. The customer needs rebooking. The slot is gone.

This happens more often than most operations teams want to admit. And the cost isn't just the aborted visit. It's the knock-on: a rescheduled appointment in an already tight calendar, a technician who's now underutilised for the rest of the day, and a customer who's lost confidence before the work has even started.

The question worth asking isn't just how to order more stock. It's where in the workflow the problem actually starts.

The Fault Line Is Usually Upstream

Stock shortages rarely come from nowhere. In most cases, the signal was there. A job was allocated without anyone checking whether the right parts were physically available. Or the check happened, but it happened in a spreadsheet that nobody updated after the last bulk delivery. Or the stock was logged as available in the warehouse but had already been loaded onto a different van the day before.

The gap is almost always an information gap. The person scheduling the job and the person managing stock are working from different pictures. By the time the mismatch surfaces, it surfaces at the worst possible moment: on site.

In large-scale utility and installation operations, this gets harder. You might have dozens of engineers across multiple regions, drawing from multiple storerooms or vehicle stock. Keeping an accurate real-time picture of what's available, what's allocated, and what's running low is genuinely difficult without the right systems in place.

Where the Fix Sits

The fix isn't a new ordering process on its own. It's connecting stock visibility to the job scheduling workflow, so both sides of the operation are looking at the same data at the same time.

When a job is scheduled on Reach, the stock and logistics side of the platform is part of that process, not separate from it. Schedulers can see what materials are needed for a job type, check whether they're available, and allocate them before the engineer leaves the depot. If stock is running low on a particular part, that's visible before it becomes a problem on site.

Field technicians can see their job details through the Reach mobile app, including what they should have with them. If something's missing before they leave, they can flag it. That's a much cheaper conversation than the same conversation happening in a customer's hallway.

From an operations management perspective, the reporting tells you where the shortages are clustering. If aborted visits keep happening on a specific job type, or in a specific region, the data shows it. That's the kind of pattern that's very hard to spot when your job management and your stock records live in different systems.

The Wider Cost of a Broken Loop

Aborted visits are the visible symptom. The less visible cost is what they do to the rest of the schedule.

A job that fails on site doesn't just create one empty slot. It creates a rebooking that has to fit somewhere in a calendar that's already allocated. That displaced appointment often pushes something else. In fast-moving installation programmes, like a regional EV charge point rollout or a smart metering installation programme, one bad week of aborted visits can set a project back by a meaningful amount.

There's also the technician's time. An engineer who arrives at a job that can't be completed is, from that moment, a resource you're paying for without getting the output. If that pattern repeats across your workforce, the cumulative effect on cost and programme delivery is significant.

Customer experience is part of it too. In utility and regulated installation work, customers often wait for appointments. When an engineer arrives and has to leave without completing, the trust that took time to build can go quickly.

Closing the Gap

The operations that handle this well tend to share one characteristic: they've connected their scheduling, stock, and mobile working into a single workflow rather than running them as separate functions.

That means the scheduler sees stock availability when they're booking a job, not after. It means the engineer gets accurate job information before they leave, not when they arrive. And it means operations managers can see, in real time, what's happening across jobs, teams, and materials.

Reach is built to do exactly that. Scheduling, dispatch, job tracking, mobile working, stock and logistics, and reporting all run in one platform. The individual modules are configurable, so you turn on what fits your operation and add more as your needs grow.

If aborted visits and stock-related delays are a regular feature of your operation, the starting point is usually the same: look at where the information breaks down, and fix the workflow there.