Proof-of-Delivery Photos That Actually Hold Up in a Dispute
POD photos are only as useful as their metadata. We rebuilt our POD flow around the questions that come up six months later.
Plan operations across multiple service zones without juggling separate runs. Zone fan-out splits stops by polygon, dispatches each zone in parallel, and merges the result.
Until today, dispatchers running multiple service zones had to plan each zone separately. That made enforcing zone boundaries easy — but it also fragmented driver pools and made cross-zone overflow invisible.
How fan-out works
Drop a CSV with all stops, pick a zone template, click Dispatch. Fleetune classifies each stop against your zone polygons, fans out an optimization run for every zone in parallel, then stitches the result together as a single board view.
- Pass 1: zone-internal optimization across assigned drivers
- Pass 2: orphan and out-of-zone stops absorbed by the nearest driver-zone
- Pass 3: overflow modal for stops no zone can absorb (capacity / time windows)
The result feels like one dispatch. Behind the scenes it is several — each obeying the operational constraints of its zone.
When to use it
Zone fan-out shines for operators with stable service areas, dedicated driver pools per region, or franchise structures where territory ownership matters. For single-zone fleets, the existing global LSD mode is still the right default.