Keep the day in view
The schedule uses a familiar run sheet structure. Route, timing, vehicle and current status can be read together, with a focused detail view when the dispatcher needs to make a change.
Relay
A working day changes quickly. Relay explores a dispatch workspace where the schedule stays visible, unassigned work is easy to spot and every edit has a clear result.
Studio concept / Interactive prototype
Keep the day
in view
One run still needs a driver
The scenario
A small change
without losing the picture
- 01
Spot the exception
Run RL-105 has no driver. Its status is visible beside the other runs, and the filter brings it into focus.
- 02
Make the assignment
Choose a driver for the sample run, then confirm. An unconfirmed selection does not silently change the schedule.
- 03
See what changed
The run list and calculated counts update together. Nothing is sent to a driver; this is a local interface preview.
Now try it
A change everyone can follow
Assign the unallocated run, filter the schedule or reassign another job. Changes reset when you reload the page.
RelaySample dispatch day
A clear view of the day
All routes and people in this preview are sample data
- Open runs
- 4
- Need a driver
- 1
- Complete
- 1
| Run / route | Time | Driver / status | Edit |
|---|---|---|---|
| RL-104Parramatta to Blacktown | 08:30 | TaylorIn progress | |
| RL-105Penrith to Parramatta | 09:15 | Not assignedUnassigned | |
| RL-106Liverpool to Bankstown | 10:00 | CaseyPlanned | |
| RL-107Castle Hill to Hornsby | 10:45 | MorganPlanned | |
| RL-108Auburn to Silverwater | 08:00 | JordanComplete |
Choose a driver to assign the unallocated sample run
Behind the concept
A busy schedule
One place to follow it
The brief follows a dispatch team coordinating runs in a spreadsheet and discussing changes by phone. The interface brings the schedule, driver assignments and exceptions into one view.
The approach
The decisions
behind the direction
Make changes legible
The proposed workflow distinguishes an unsaved edit from a confirmed change. A production version would need permission checks, handling of simultaneous edits and a reliable change history behind the interface.
Design for interruptions
Dispatch rarely follows a perfect sequence. The concept gives delayed runs and unassigned work a visible place, so an exception can be addressed without losing the wider schedule.
In focus
What this
concept explores
- A daily dispatch view
- Route status and assignment details
- Schedule filtering
- Visible exceptions and unassigned work
- A proposed role and change history model
Next concept