Mark a stop as failed or skipped
Can't complete a delivery in the Upper driver app? Skip the stop and add a reason and notes so dispatch can decide whether to reschedule, reassign, or close it.
When you can't complete a delivery — the customer isn't home, the address is wrong, the gate is locked — record the stop as skipped in the Upper driver app instead of leaving it open. You add a reason and a note explaining what happened, and that information travels back to the web app so your dispatcher can decide what to do next.
Labels vary by workspace. If your workspace is set up for service work, you may see Technician, Proof of Service, and Service Options in place of Driver, Proof of Delivery, and Delivery Options. The steps are the same.
Skip a stop you can't complete
Open the stop
Open the stop you're working in the driver app.
Choose to skip instead of complete
Rather than completing the stop, mark it as skipped.
Add a reason
A reason is captured on a skipped stop. Choose the reason that best matches the situation — for example, the customer wasn't home, the address was wrong, or access was denied.
Add a note
Add a note explaining what happened — what you tried and what stopped the delivery. The clearer the note, the faster your dispatcher can act on it.
The reason and the note are what your dispatcher uses to decide the next step, so be specific. "Customer not home, knocked twice, no lockbox" is actionable. "Couldn't deliver" forces dispatch to call you to find out what happened.
What your workspace may require before you skip
Your admin decides what proof, if any, is required to skip a stop — and these requirements are set separately from the ones for completing a stop. Depending on your workspace settings, you may be asked for one or more of these before the skip is recorded:
- Photos — one or more images
- Signature
- Service notes — a typed note
If your workspace requires none of these, you may be able to skip a stop in a single tap.
What happens after you skip a stop
- The skipped stop, with its reason and your notes, syncs back to the web app, where dispatch can see it.
- Your dispatcher decides what to do next — reschedule the stop, reassign it, or close it out.
ETAs for a route are based on historical traffic data, not a live feed, so the times dispatch sees are projections rather than minute-by-minute readings.
Troubleshooting and FAQ
Related
Mark a stop as completed
Finish a delivery in the Upper driver app: capture any required proof of delivery and notes, then mark the stop complete so the work syncs back to dispatch.
Message dispatch
Message your dispatcher from the Upper driver app using crew chat. Your dispatcher sees it on the same web dashboard they use to manage routes.