Blog

How to run local deliveries without spreadsheets and WhatsApp groups

20 October 2026 · 4 min read

Most delivery operations start the same way: a spreadsheet of orders, a WhatsApp group with the drivers, and one person keeping it all in their head. It works at ten deliveries a day. Somewhere past fifty, it starts to cost you, quietly, every day.

The signs you have outgrown it

None of these is a disaster on its own. Together they add up to hours a week and customers who are slowly losing patience.

• Addresses get typed twice. Once into the sheet, again into a message to a driver, and sometimes a third time into a maps app. Every copy is a chance for a typo.
• "Where is my order?" calls. The customer can't see anything, so they call you, and you call the driver, who is driving.
• Nobody knows who delivered what. When a customer says a parcel never arrived, the answer is buried somewhere in a chat history.
• Drivers overlap or sit idle. Two drivers end up in the same neighbourhood while a third waits for a message.
• The end of the day is reconciliation. Someone goes through the group chat to work out what was delivered, what failed and why.

What dispatching actually involves

Whatever tool you use, every delivery goes through the same six steps. Writing them down makes it obvious where the spreadsheet is doing the work and where a person is filling the gaps.

1. Capture the job. The address, a contact name and phone number, a time window if there is one, and notes such as "ring twice" or "fragile".
2. Assign it. Either you pick the driver, or you offer it to the drivers in the area and the first to accept takes it.
3. Track progress. Accepted, on the way, arrived, delivered, or failed with a reason. A driver should be able to update this with one tap, not a typed message.
4. Keep the customer informed. A tracking link that shows when the driver is on the way removes most "where is my order?" calls.
5. Prove the delivery. A photo, a signature or a scanned label, saved with the job. (We wrote a separate guide on choosing between them.)
6. Look back. How many deliveries each driver made, how many failed and why, how long they took. You can't improve what you can't see.

A simple workflow that scales

The goal is not more process. It is one place where each step above happens, so nothing depends on someone remembering it.

• One list of jobs that everyone works from, instead of a sheet plus a chat plus a notebook.
• A driver app where drivers see their jobs in order, open navigation with a tap, and update the status as they go.
• A live map for the dispatcher, showing drivers only while they are on shift. Drivers deserve privacy off the clock, and you don't need to see them.
• Automatic customer updates by email or WhatsApp, with a tracking link, sent when the status changes rather than when someone remembers.
• Proof of delivery and failure reasons stored with each job, so a dispute takes thirty seconds instead of an afternoon.

What to look for in dispatch software

There are many delivery management tools, and most demos look the same. These are the questions that separate them for a small or growing operation.

Does the price fit your volume?

Some tools charge per delivery or per task, some per driver, some a flat monthly fee. The cheapest option at 500 deliveries a month is rarely the cheapest at 5,000. Work it out for your real numbers, including your busiest month. Our guide to delivery software pricing walks through it.

Does the driver app work without signal?

Basements, lifts, rural roads and busy city centres all drop connections. If the app stops working when the signal does, drivers go back to messaging you. Look for an app that keeps jobs and proof of delivery on the phone and sends them when it reconnects.

Can jobs come in without retyping?

If you sell online, orders from Shopify or WooCommerce should become jobs on their own. If you get orders by phone or email, a quick form and a spreadsheet import should cover the rest.

How do customers hear about their delivery?

Check which channels are included and who pays for messages. Per-message SMS fees add up quickly at volume.

Does it optimise routes?

If your drivers do several stops per run, putting them in the best order saves real time. If most runs are a single drop, it matters much less. More on that in our route optimization guide.

Switching without disrupting a single day

The safest move is gradual, not a big switch on a Monday morning.

1. Start with one driver for a few days, while everyone else carries on as usual.
2. Import your existing jobs from the spreadsheet you already have, so you aren't typing anything twice.
3. Run both side by side for a week. Keep the old sheet as a backup until you trust the new one.
4. Move everyone over once the first driver is comfortable, and close the group chat for job assignments. Keep it for everything else.