Last-Mile Delivery Exception Dashboard
Design a dispatcher dashboard that prioritizes failed deliveries, route disruption, customer promises, and accountable recovery.
The brief
Understand the problem
Background
A regional delivery network completes most stops normally, but access failures, incorrect addresses, damaged parcels, vehicle issues, and missed time windows require rapid coordination.
User context
Nora supervises twenty-eight drivers during an evening shift. A storm has closed two roads, three priority medicines are delayed, and customer support is updating recipients separately.
Product problem
Nora needs one operational picture that distinguishes urgent service risk from ordinary delay and prevents dispatch and support teams from issuing conflicting instructions.
Objective
Create network overview, exception queue, route detail, and recovery assignment states for last-mile operations.
What to design
Define the experience
Required experience
- Assess route health and time-sensitive exposure
- Prioritize exceptions by impact, age, and recovery window
- Inspect a route, parcel, driver, and customer-contact history
- Assign a recovery action and monitor its acknowledgement
Screens and states
- Delivery network overview
- Exception queue
- Route and parcel workspace
- Recovery assignment
Core user flow
Follow the critical path
- 01
Nora sees that road closures affect four routes
- 02
She filters for medically time-sensitive parcels
- 03
A route detail shows one parcel can transfer to a nearby driver
- 04
She assigns the handoff, support receives the same update, and both drivers acknowledge
Product rules
Requirements and constraints
Requirements
- Separate network incidents from individual delivery exceptions
- Expose promise window, parcel priority, owner, and last event
- Link customer communication to the operational case
- Require acknowledgement for route changes and handoffs
- Keep original scan and location events available for investigation
Constraints
- Driver location should be limited to operational need and retention policy
- Estimated arrival times can change after reassignment
- Dispatch actions cannot instruct unsafe driving
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Shift snapshot
- 28 active routes
- 612 remaining stops
- 19 open exceptions
- 3 medically time-sensitive parcels
- 2 road closures
Finish line
What to deliver
- Four desktop screens covering detection through acknowledged recovery
- A priority and ownership model for network and parcel-level exceptions
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Cormorant Garamond & Open Sans
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Cormorant Garamond & Open Sans
Clear interface writing gives people the confidence to understand what changed and decide what to do next.