Rethinking contractor operations at Evri

Most contractor networks already have plenty of performance data. The harder problem is turning it into something that changes behaviour.

A contractor may know that service has slipped or that a particular metric is moving in the wrong direction, but still not know which part of the operation deserves attention first. A central team may be able to identify an underperforming area without seeing enough of the local context to understand what is actually causing it.

That creates a gap between measurement and action.

Wehand could sit in that gap, combining network-level performance with the operating context inside individual contractor businesses and turning it into clearer priorities for both sides.

Accountability works best when the cause of a problem is understood.

If a contractor misses a target because of weak management discipline, the response should be different from one caused by temporary capacity pressure, unusual route conditions or a cluster of vehicle failures. Treating every poor result as the same management problem can create activity without solving anything.

Depot-1 could help separate those cases by looking across the operation rather than at a single metric. The aim would be to make conversations between Evri and its contractors more specific: what changed, why it changed and what needs to happen next.

That creates accountability based on evidence rather than simply on the final score.

Small operating businesses do not have unlimited management capacity.

A contractor may be dealing with staffing, fleet, performance, customer issues and day-to-day exceptions at the same time. Giving that team another dashboard does not necessarily make the operation easier to run.

What matters is compression.

Instead of presenting ten problems, the system should help identify the two or three that are most likely to affect performance. Instead of showing that a group of drivers is underperforming, it should help distinguish who needs attention, what behaviour is driving the issue and what intervention is most likely to work.

That turns intelligence into something a local operator can actually use.

A contractor model also creates a useful source of variation.

Different businesses will respond to similar operating challenges in different ways. Some will develop better routines, stronger coaching or more effective ways of managing exceptions. Others will repeatedly struggle with the same issues.

Across a sufficiently large network, those differences become valuable data.

Wehand could help identify which management approaches consistently lead to stronger outcomes and where those practices could be adapted elsewhere. Instead of relying only on centrally designed processes, the network could learn from what its best operators are already proving in practice.

The aim would not be to take control away from contractors.

It would be to give Evri a clearer view of where intervention is genuinely needed, while giving contractors better intelligence for running their own businesses.

That changes the relationship from one built mainly around reporting results to one built around understanding and improving them.

For a contractor-led network, that distinction could matter just as much as the technology itself.