Route Planner

For drivers

A phone that keeps working when the signal doesn’t.

The driver app is a Flutter app for Android and iOS. It shows the next stop, takes three kinds of answer, and never makes you wait for the network before you can carry on.

1The stop card

The next stop, and what happened there.

Customer, address, notes, parcel count, phone number. A Navigate button hands off to Google Maps, Waze or Apple Maps, whichever the driver already uses. The top of the screen says how many stops are handled so far.

Delivered
Done. Saved on the phone straight away.
Failed
Pick a reason, add a note. It goes in a retry list so it does not get lost at the end of the day.
Skipped
Not now. Marked as skipped, with the time.

Today

Sync: 2 waiting

Handled 7 of 10

Next stop, number 8

62 Park Rd, Grafton

Parcels
2
Notes
Side gate, ring the bell twice

Navigate

DeliveredFailedSkipped
Example dataTwo events saved on the phone, waiting for signal. The driver does not have to do anything about it.

Offline

Saved on the phone first. Sent when there is signal.

Every delivered, failed or skipped is written to the phone before anything else happens. The app then sends it to the server whenever it can: when signal comes back, when the app is opened again, and every so often while it is open.

If the app is killed halfway down a street, the events are still there. A small chip on the screen says how many are waiting, for example “Sync: 2 waiting”. It is information, not a chore.

If the office changed the order of stops you had not done yet, the office wins on that. If you marked something delivered, you win on that. And if your sign-in expires while you are out of signal, the route you are on keeps working. The app asks you to sign in again when it is back online.

Re-route from where you are

+6 stops, 2 merged

Two of the new addresses were already on your route, so they were merged instead of added twice. Stops you have already handled stay where they are.

Accept new routeNot now
Example dataThe driver decides. Nothing changes under their feet.

2Mid-route changes

Add more files. Then re‑route from here.

A second manifest turns up, or someone hands you a bag of extra parcels. Add the photo, the PDF or the text to the route you are on. It is read and checked the way the morning manifest was.

Then you see a short summary, such as the number of new stops and how many were merged into ones you already had. You accept it or you do not. Stops you have already handled are locked and will not move.

3Location

What it does with the phone’s location.

The app asks for location once, when the driver starts a route. While the route is active and the app is open it records where the phone is, so the dispatcher’s dot moves. If the driver says no, the app shows a note and carries on.

That is all of it. Three things are not built.

  • Tracking in the background

    A driver's dot moves only while the app is open on their phone. We do not follow phones around when the app is closed.

  • Alerts on the lock screen

    A new or changed route is there when the driver opens the app. Push alerts are not wired up yet.

  • Proof of delivery

    Photos and signatures at the door are planned, not built. Today a stop is delivered, failed or skipped.

Talk to us about the pilot