Last-Mile Delivery Workflow
Last-mile work is three distinct moments per shift: morning prep, on-the-road execution and end-of-day evidence. This page walks each of them — what the app does, what it remembers, and what you hand back to dispatch.
Morning — ~15 minutes from sheet to ready
0–3 min. Drop the dispatch CSV/Excel into the app. Map the address column. The parser handles the messy stuff: stray quotes, mixed-format addresses, ZIP+4, common typos.
3–10 min. Confirm pins on the map. Any address the geocoder is unsure about is flagged — fix by typing or by dragging the pin to the actual loading bay.
10–12 min. Lock the depot as start. Tap Optimize. The route reorders and an ETA appears next to every stop.
12–15 min. Walk the van against the route order. Done — you are driving early in the day instead of late.
On the route — one tap per stop state
The current stop card shows address, recipient, phone, note and visit duration. Three big buttons run the entire on-route loop:
Go. Hands the leg to Google Maps or Waze for turn-by-turn. Pick once, the app remembers.
Done. Triggers proof-of-delivery capture (configurable per stop or per route). The stop drops off the active list, the next one comes up.
Failed. Captures a reason (recipient absent, refused, address unreachable, etc.) and keeps the stop on file. It surfaces in tomorrow's planning so it doesn't get lost.
What proof of delivery actually captures
Photo — uploaded in the background, you don't wait for it. Used for safe-drop and contactless evidence.
Signature — finger or stylus on the screen. Stored as PNG, tied to the stop ID.
Barcode / QR — scan the parcel label. EAN-13, Code 128 and QR are all parsed; format auto-detected.
ID check — a binary "we verified ID" toggle for age-restricted deliveries. No personal data is stored, just the toggle and timestamp.
Text note — "left at front door", "neighbour #4B", "called twice no answer". Anything dispatch will read later.
Each item is configurable per route — required, optional or off. Dispatch sets the policy once.
End of shift — clean handoff to dispatch
The completed route stays in My Routes with start time, total distance, total time and progress. All POD evidence is tied to it.
Failed stops carry over: they show on tomorrow's planning with the reason from today, so a route from yesterday's failed-only stops takes two taps to build.
Dispatch retrieves POD from the synced backend (or, on free tier, you share the route summary screen).
Built for the apps already on the driver's phone
Google Maps and Waze for navigation. Phone dialer for the recipient call. Camera for the photo. SMS for templated "I'm two stops away" messages. The app is the planner and the POD store, not another navigation rewrite.
Try the last-mile workflow free