The dispatch board

The dispatch board is where a delivery pool stops being a list of addresses and becomes a set of trips. It is the Resolve tab of a pool: the unresolved destinations plotted on a map on the left, and a column of runs on the right that you fill by selecting pins.

A run is a proposed trip. Nothing you do on the board is saved until you resolve — up to that point you are arranging pins, not dispatching work.

The board has two selection modes, and a bar appears once anything is selected:

• Select — click individual pins, and drag to pan the map as usual. Click a selected pin again to drop it.
• Lasso — drag a freehand loop around an area and everything inside it is selected at once. This is the fast way to carve a city into rounds.

With a selection made, the bar offers Assign to an existing run, New run, or Unassign. A destination belongs to at most one run, so assigning it to a second run moves it rather than duplicating it — reshuffling two rounds is one action, not two.

Runs are numbered until you pick a driver, at which point the card takes that driver’s name. Each run has a colour, and its pins on the map carry it, so you can see the shape of the day without reading a single row.

Two limits are worth knowing. Destinations with no coordinates are excluded from clustering and reported back in a banner, so they are visibly skipped rather than silently dropped. And a pool with more than 500 coordinate-bearing unresolved destinations is refused for a proposal — split or filter the pool first.

Estimates are best-effort and run under an overall time budget. A group whose estimate does not return in time simply shows no figure; the group itself is unaffected and resolves normally.

Resolving turns every non-empty run into exactly one trip. Empty runs are ignored, so you can leave a spare card on the board without consequence.

Each trip arrives:

• As a draft, with no scheduled start — dispatching is your next decision, not this one.
• With the pool’s trip type and priority, and with flexible stop order.
• With one stop per destination, carrying that destination’s recipient contacts, and its default tasks where your tenant applies those automatically.
• Linked back to the pool it came from, so the provenance survives.