How to Read a Delivery Offer Screen Before You Accept

The pay figure is the only number on an offer screen the platform intends to honor. The distance, the duration and the tidy line on the map are projections, built to look reasonable rather than to describe your evening.

Once you know which fields are which, the ten-second decision gets easier.

The fields, and which are facts versus projections

Treat as close to fact: the payment amount, the name of the pickup business, and the general area of the drop-off. Those are commitments or descriptions of something real.

Treat as projection: total time, total distance, arrival estimates, and any predicted tip. Estimated durations assume clear roads, an order that is ready, parking that exists and a customer who answers. Where a tip is shown as a range or an expectation, it is a forecast and it can change after delivery.

So read the pay figure as the amount you are being offered to take a risk on a projection. How that figure was assembled in the first place is how a gig app builds the payout.

Distance shown versus distance traveled

The distance on the offer is normally measured from the pickup to the drop-off. Your actual driving has three legs, and the app pays attention to one of them.

Leg one is wherever you are now to the pickup. Leg two is the one on the screen. Leg three is from the drop-off back to somewhere work exists, and it is entirely invisible.

Leg three is what turns a good-looking offer into a bad hour. A long run out to a housing estate with no restaurants near it means you drive the whole thing again in reverse, unpaid, before another offer is plausible. The habit that fixes this is one question asked before you tap accept: where does this leave me, and what do I do next from there.

The fuel for all three legs comes out of the amount you were offered, along with everything else in the costs a gig app never shows you.

What is not on the screen, and how to infer it

The screen does not tell you whether the order is ready, how bulky it is, whether the building has a working lift, whether parking exists, or whether a second drop has been quietly bundled in.

Infer readiness from the pickup name. Chains that cook to a screen behave differently from a small kitchen that starts your order when you walk in. Infer bulk from the venue type — a large grocery pickup or a tray of drinks is a different job from a single bag. Infer the building from the area, if it is an area you know.

Which is the real point: your own memory of an address is the best information available and no app will ever give it to you. Write the bad ones down, because the screen will offer them to you again next week wearing a slightly different number.

The pickup is the strongest predictor of how long this takes

Waiting at a counter is unpaid time that somebody else controls, and it is the single largest variable in how long a job takes.

Pickups that eat time: kitchens that begin cooking on driver arrival, venues with one person covering the counter and the phone, places with nowhere to stop so you circle the block, and big stores where you queue at a service desk behind customer returns.

Pickups that do not: anywhere that stages sealed bags on a shelf with a name on them, and anywhere with a dedicated driver door.

Keep a list of both. A two weeks of notes and you will be declining bad offers on the pickup name alone, before you have even read the amount. Building that list is one of the quiet jobs of a first shift on a delivery app.

Build an accept rule so you are not deciding fresh each time

An accept rule is a short set of conditions you decide once, while calm and at home, and then apply mechanically when the countdown is running.

Give it four parts. A pay floor expressed against distance — a minimum you set for yourself and write down, not one you copy from a stranger. A maximum drop-off distance from the zone you work. A blacklist of pickups and buildings. And a cutoff condition for the end of a session, so you stop accepting outbound jobs before you want to be home.

Write it on paper and keep it in the car. The point of the rule existing outside your head is that the tired version of you at the end of a shift does not get a vote.

Review it weekly against what happened rather than how the shift felt. And know that declining a lot is itself measured on some platforms, which touches account standing — the mechanics of that are in how gig app ratings and standing metrics work and, at the sharp end, what triggers a gig app deactivation.

Offers that look strong and should still be declined

A high payment for a long run out of your zone. The money is real and so is the hour it takes, and the hour includes a dead drive home.

A stacked offer where the second drop sits in the opposite direction from the first. You are being paid for two jobs and doing the mileage of three.

Anything from a pickup on your bad list, whatever the amount. You already learned that lesson and paid for the lesson once.

An offer that lands while you are already carrying an order going somewhere else, unless the two genuinely fall on one line. And any offer at the very end of your session, because the leg home is not free.

And any offer that would require you to break a rule you set for your own safety — an unlit address, a building where something already went wrong, a drop that means leaving the car unlocked with the engine running.

Decline it and say nothing. No explanation is owed to anyone, and a countdown running out is not a loss.