Dispatch
Tomorrow's runs, built this afternoon.
Confirmed orders become deliveries. Deliveries land on runs. Run templates hold the shape of a normal day, so building tomorrow is minutes of exceptions rather than an hour on a whiteboard.
- The Corner DeliDrop 4 units · by 07:00
- Harbour Hotel GroupDrop 12 units · 09–12
- Ridgeline Civil — Bell StSwap 6 units · from 06:30
- Bayview HotelCollection 9 units · any
- DM Carpentry — Lot 14Drop 10 units · pm
Drag onto a run, or tap a delivery then a run.
- 1Northside Medical3u · 08–10
Drop deliveries here
Drop deliveries here
Delivery is the centre
A delivery does not need an order behind it. Drops, collections, returns, transfers and pickup-and-drop are all kinds of delivery, each with its own proof steps.
The dispatch board
Runs down the side, unassigned deliveries in the tray. Drag to assign; capacity and sequence update as you go. Vehicle and driver constraints are on the board, not in the dispatcher's head.
Run templates and "build tomorrow's runs"
A template is a run's normal shape: driver, vehicle, depot, the usual sequence. One action fills tomorrow from templates and confirmed orders; the office handles what does not fit.
Release and freeze
A released run is on the driver's phone. A frozen run stops accepting changes from the office so the driver is not chasing a moving target.
Failed delivery and reschedule
A stop that fails is an event with a reason and a photo, and a reschedule is one action that puts it back on a run. Holding a delivery is a reschedule, never a lost note.
Customer notifications
ETA, delivered and failed messages go out per the customer's preferences, SMS or email, from the delivery timeline, with the tracking page link.
Where this matters most
The same module, in your trade.
See how dispatch & runs shows up on a normal morning in the trades boXe is built for.