Know the Fix Before You Dispatch Anyone

10pm. A site goes dark.

The usual sequence kicks off before anyone's even sure what's wrong. Call an engineer. Wait for them to get in the van. Two hours on the road to reach a store that's been offline the whole time.

They arrive, plug in, start working through it. The fix takes two minutes: restart the router.

Two hours of downtime and a call-out, for a two-minute fix.

I've watched this play out more times than I can count, across POS terminals, payment devices, fuel pumps, refrigeration units. The fault is rarely the hard part. Getting someone in front of it is.

Most operational tooling in retail is built to detect that something's wrong. Far fewer are built to tell you what's wrong, specifically enough that the person closest to the problem can act on it. That gap between detection and action is where most of the cost sits, not in the fault itself, in the distance between the fault and the fix.

The shift worth making

If root cause is known before anyone leaves the office, the response changes shape entirely. Sometimes an engineer never needs to travel. Someone already on-site, a store manager, a member of staff, can be talked through it over the phone, working from clear, specific instructions built around exactly what's broken.

No drive. No call-out. The site's back up in the time it takes to make that call.

Same fault, same 10pm, same store. The only thing that's different is whether the answer arrives before the van does.

This matters more the bigger the estate gets

At ten sites, a two-hour round trip is an inconvenience. At two hundred sites, it's a structural cost that compounds every week: engineers on the road instead of on planned work, sites down longer than they need to be, staff waiting on someone to arrive rather than acting on what they already have in front of them.

The operators who get ahead of this aren't the ones with the most monitoring dashboards. They're the ones who've closed the gap between "something's wrong" and "here's exactly what to do about it." That's a different problem to solve than visibility. Visibility tells you a light's gone red. Root cause tells you why, and what to do next.

That's the test worth applying to any system you're running today: whether it stops at flagging a problem, or gets you to the fix.