Shipment dispatch, delivery exceptions and proof of delivery
A parcel delivery company needed depot staff, dispatchers, drivers and shippers working from the same shipment record. Over 24 weeks we built depot intake, a dispatch board, a driver app and a shipper portal, covering receipt, assignment, delivery attempts and returns.
Screens
The challenge
Dispatch decisions, driver updates and delivery evidence were spread across separate tools and messages. Failed attempts and address problems had no explicit next action or owner.
Our approach
Each shipment carries a status history, scan events, assignments and delivery evidence. Depot staff check inbound manifests by scan. Dispatchers plan routes against each vehicle's weight and volume and work an exception queue. Drivers download stop lists, scan at each stop and capture photos, signatures and one-time codes offline. A failed attempt records the reason, evidence and next step. Shippers track their parcels in a portal, while returns stay visible to operations.
Outcome
- Shipment history from depot receipt through delivery or return
- Dispatch assignments connected to what drivers record at each stop
- Photo, signature and one-time-code evidence with controlled access
- Failed attempts recorded with a reason, evidence and the next step
Client name withheld. Images are UI recreations using synthetic data and figures.