The screen that runs the 7 a.m. airport push.
Kanban lanes by status. Live map with route polylines coloured by lifecycle. Driver presence dots. Auto-refresh every fifteen seconds so a dispatcher can keep one hand on coffee.
Anatomy of the dispatch board
A board built for tomorrow morning.
Status lanes
Pending → Confirmed → Assigned → En route → On trip → Completed. Each lane lays out by pickup time, hottest first.
Live map
Each booking renders A/B pins plus a driving polyline coloured by status. Bounds auto-fit. Toggle Board ↔ Map from the URL.
Filter chips
Filter by class, by driver, by airport, by date window. Stickers stay in the URL so a dispatcher can share a view.
Driver presence
Online dots on the right rail. We know who is on shift, who is on a trip, and who is off duty.
Board · Map
Two views, one URL toggle.
Same data, two ways to see it. Kanban for the dispatcher; live map for the owner who wants to know where the £148 LHR run is right now. Switch via ?view=map — no extra page load.
- A/B pins + driving polylines per booking
- Status-coloured (pending amber → on-trip emerald)
- Fit-bounds on filter change
- Cursor on a pin pops the trip ref and driver
Operations on top
The four things a dispatcher does in their sleep.
Auto-suggest driver
Sort available drivers by proximity + class match. One click to assign.
Manual override
Drag a card between lanes. Reassign in two clicks. Audit log records every change.
Flight watcher
Airport bookings poll the inbound flight every 3 min. Delays ≥15 min auto-shift pickup.
WhatsApp inbound
Customer texts a job. We parse it into a quote and ask them to confirm — your phone never rings.
A dispatcher should drink coffee with both hands.
Open the live demo and watch a board auto-refresh as drivers move through statuses.