The delivery driver's guide to cutting wait times and earning more per hour

Ask most delivery drivers how they're doing and they'll tell you about their best order of the night. Ask them about their worst hour and you'll usually find the real story: a single restaurant that took 30 minutes when they expected five. Waiting is the hidden tax on this job. It doesn't show up on any platform's earnings screen, but it quietly decides whether a shift was worth it. This guide is about getting that time back.

Why a long wait costs more than it looks

Imagine two orders that both pay £4. The first takes 10 minutes door to door. The second looks identical — until the kitchen makes you wait 25 minutes before the food is even ready. On paper they're the same £4. In reality, the first paid you roughly £24/hour and the second paid you under £8. Same money, completely different job.

This is why chasing the highest-paying order is a trap. The number that actually matters is earnings per hour, and waiting is the biggest, least-visible drain on it. A driver who avoids two bad waits a night can add an hour of real earning time to a shift without driving a single extra mile.

Learn which kitchens are slow — before you arrive

Every restaurant has a rhythm. A burger place might be four minutes at 3pm and twenty-two minutes at 7:30pm on a Friday. A fried-chicken shop might be quick all week and chaos on payday weekend. You can't keep all of that in your head, and you definitely can't know it for a restaurant you've never been to.

That's the entire idea behind community wait data. When hundreds of drivers each log a few real waits, patterns emerge that no single person could see: this kitchen is reliably fast, that one collapses at dinner, this chain is fine on weekdays but brutal on Saturday nights. Before you accept or set off for an order, a quick glance tells you what you're walking into.

How to read the colours and numbers

MOdelivr keeps it simple so you can read it at a glance, one-handed:

• Green — a short wait. Get in, get out.
• Amber — moderate. Fine if the pay is good, annoying if it isn't.
• Red — a long queue. Think twice, especially if you've got somewhere better nearby.

Each restaurant shows both the live "waiting now" picture and the typical wait for this day and time, plus a busiest-times chart so you can spot the windows to avoid. Nearby, logged places sort to the top, because the only restaurants that matter are the ones around you right now.

Five habits that protect your hourly pay

1. Check before you commit. A two-second look at the typical wait can save you a twenty-minute mistake.
2. Avoid the red at peak. If a kitchen is famous for collapsing at 8pm, that's the hour to work the fast places instead.
3. Stack smart. If you're already waiting at a restaurant and a second order from the same place comes in, taking it can double your pay for the same wait — that one wait now covers two drops.
4. Log every wait. The data is only as good as what drivers put in. Your two taps make tomorrow's decisions better — including your own.
5. Track your real £/hour. Measure earnings against working time, from your first arrival to your last drop. The headline pay on a job means nothing until you know the time it cost.

The goal isn't to drive more. It's to spend less of your shift standing still.

Waiting well when you can't avoid it

Sometimes you're already in the queue and there's nothing to do but wait. Use it. Log the wait so it counts. If you track earnings, add the order's pay now while you remember it. Glance at what's busy nearby so your next move is decided before the food lands in your bag. A wait you can't avoid is still a wait you can turn into useful information.

The community makes it work

None of this works without drivers sharing. One person's logs are a diary; a thousand drivers' logs are a map. That's the trade at the heart of MOdelivr: contribute a few honest waits, and in return you get the collective knowledge of every driver who came before you tonight. It's free, it's anonymous, and it gets better every single time someone taps "Got it".