Route Planner

How it works

A day, step by step.

Here is what happens between the manifest landing in your inbox and the last parcel being marked delivered. Where a person has to do something, we say so.

Upload the manifest

Drop in the day’s files, or paste the text, and pick the date. Several files at once is fine. Each page is read on its own, then the pages are put back together.

Nothing here needs a template. If your depot sends a manifest in its own odd layout, that is what we are trying it on.

Photo
Of a printed manifest or a delivery list. It has to be legible to a person.
PDF
With real text in it. A PDF that is just a scanned picture is not read yet.
Spreadsheet or CSV
Columns are matched to address, name, notes and parcels. You can save the mapping for next time.
Pasted text
From an email, a message, anywhere. One address per line works best.

Check what it read

This is the step that matters. Every stop is listed with the address as it was read and the page it came from. Click one and you see the page with that line marked.

Five flags: valid, needs confirmation, incomplete, not found, duplicate. You can edit an address, delete a stop, add one, or drop a pin on the map. A stop that could not be placed stays unplaced until someone does that. We do not fill the gap with a guess.

Example review table with five stops and their flags
No.Address as readFromFlag
127 Dominion Rd, Mt EdenPage 1Valid
23/112 Symonds St, GraftonMatched 112 Symonds St. Is the unit 3?Page 2Needs confirmation
3Flat 4, Newton RdNo street numberPage 2Incomplete
49 Gabbro Lane, AucklandLeft unplaced. Pin it on the map.Page 3Not found
527 Dominion Rd, Mt EdenSame as stop 1Page 3Duplicate
Example dataClick a row and you see the page it came from, with the line marked. Nothing is sent out until a person has been through the flags.

Stops land on zones

Once an address is confirmed it is placed on the map and matched against your zones. A zone can be a polygon you draw, a list of postcodes, a list of suburbs, an administrative boundary, or a radius around a point.

A driver can hold several zones, with backups for when someone is away. Stops that fit no zone go to an “unassigned” tray, where you can see them and decide.

Split between drivers, sequenced by road

Where one driver owns a zone, those stops are theirs. Where several do, the work is split between them. Each driver’s stops are then put in order by road distance, with limits you set such as maximum stops and shift length.

This part runs on routing software we host ourselves: an address search (Pelias), road distances and directions (OSRM), and the ordering and splitting (VROOM), all on OpenStreetMap data. The map you look at uses the same data.

12345123456789D?unplacedpin it by hand
Simplified, not to scale. Each driver gets one run, in an order that follows roads rather than straight lines.

Review the plan, then publish

The dispatch board shows every driver’s run. Drag a stop to another driver, lock one so it stays put, and look at the whole day before anyone sees it.

Publishing sends the route to the driver’s phone. If you change something after that, the driver gets the new version rather than a second copy.

The driver works through it

The phone shows the next stop: address, notes, parcels, a phone number. A Navigate button opens Google Maps, Waze or Apple Maps. Then delivered, failed or skipped.

Failed stops go into a retry list so they are not forgotten at the end of the day. Every action is saved on the phone first and sent when there is signal. More on offline.

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.

More parcels turn up mid-route

The driver adds a photo, a PDF or some pasted text to the route they are already on. It goes through the same review as at the desk. New stops are added, duplicates are merged, and stops that no longer apply are marked cancelled, never deleted.

Stops already delivered or failed are locked. The rest are re-ordered from where the driver is standing, and the driver sees the change before accepting it. Your company chooses whether drivers can do this freely, need approval, or can only add stops.

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.

Watch the day, keep the history

While the day runs, the board shows driver dots, stop statuses and how far through each route is. Afterwards the history stays: every delivered, failed and skipped has a time on it, and nothing is overwritten.

Dispatch board

Live
ABC
  • Driver A

    Handled 7 of 10

  • Driver B

    Handled 4 of 9

  • Driver CBehind

    Handled 2 of 8

Example dataDots move as phones report in. A dot only moves while that driver has the app open.

Want to see it on your own manifest?