5 frequent delivery problems still costing fleets time and money

7:42 AM. Marta opens her laptop and stares at the spreadsheet. Thirteen routes, thirty-two clients, two vans in the shop. She starts dragging cells with her coffee still half-finished. By 9:15 the first call: "Marta, Iván's blown a tire in Sant Cugat, what do I do?" By 10:30 the second: "Marta, this client isn't picking up, I've been waiting twenty minutes." By 11:00 the third, and the fourth, and the fifth. The plan that took two hours to build stopped existing before noon.

If this sounds familiar, you're not alone. This is how most last-mile delivery works today: with spreadsheets, constant phone calls, and one person — always the same one — holding the whole thing together in their head. That's not a metaphor.

Five frictions explain almost every bad day. We see them repeat in fleets of five vans and fleets of a hundred and fifty. They aren't rare. They're the default.

1. Routes are planned by hand

The person who plans has been doing it for years. They know their drivers, their territory, and their clients better than anyone. That's valuable. But it's also the bottleneck: every decision is manual, every change means going back to the spreadsheet, every route depends on one person's judgment on one specific morning.

The problem isn't lack of skill. It's that skill doesn't scale. A day of forty-five stops gets planned well. A day of several hundred doesn't — not because the planner got worse, but because the morning isn't long enough.

2. Everything is coordinated by talking

An incident, a question, a change of order, an impossible delivery. Each of these starts a phone call. The dispatcher spends the whole day with the phone glued to their ear, handling the urgent and pushing the important to tomorrow (where it'll be urgent too, of course).

Synchronous communication eats the whole day. And when someone takes fifteen calls in a row, no one is watching the rest of the operation.

3. WhatsApp for everything

WhatsApp is a communication channel, not a control system. But the reality is people use it to send addresses, delivery photos, signed slips, ETAs, photos of damaged goods, and sometimes memes too.

Three weeks later, trying to find the proof of delivery for client X in the "MONDAY DELIVERY" group is impossible archaeology. And when a client disputes a charge, that search decides whether you eat the loss or not.

4. The customer tells you about the incident

This is the worst one. By the time the customer calls to ask where their order is, you've already lost. Not because of the incident itself — surprises exist, they've always existed — but because you found out last. Your customer thinks you didn't know. And they're right: you didn't know.

What the customer perceives isn't the delay. It's the lack of warning.

5. All the knowledge lives in one head

This is the real fragility. If Marta gets sick on a Tuesday, that fleet has a problem. If Marta takes two weeks off, that fleet improvises for two weeks. That's not an operation; it's a balancing act.

A single holiday — or just a cold — can cost overtime, extra fuel, and frustrated drivers for days. Not because the backup is worse, but because the knowledge wasn't written down anywhere they could see.

What matters lives outside the spreadsheet

The takeaway isn't "buy software." The takeaway is that as long as the process lives inside one person's head, the phone calls, and the WhatsApp groups, there's no way to spend time on what matters. There's only time to put out fires.

Going digital doesn't mean losing closeness with your team or no longer knowing your drivers. It means that when your dispatcher gets sick, the backup can look at the screen and understand. It means the incident reaches you before it reaches your customer. It means that the proof of delivery from three weeks ago is one click away, not a dig through chat logs.

Routal doesn't replace the dispatcher's judgment — it extends it. Routes get built in minutes, incidents show up on screen the moment they happen, drivers see their stops and ETAs without having to call, and customers get automatic updates when something changes.

Start with the most urgent thing: make sure the next incident reaches you through the system, not through the customer.

See how it works →