Why Live Dispatch Board
The problem
When runners self-claim at /dispatch, supervisors lose the old “assign from pack” checkpoint —
but they still need answers: How many STAT bags are still on the rack? Who is out to ICU?
Did anyone start a trip in the last hour? Spreadsheets and refresh-heavy queue screens don’t
scale for multi-ward hospital volume.
How the Live Dispatch Board solves it
The board in Reports v2 is a supervisor console fed by the same trip and rack data as the kiosk:
- KPI tiles — rack count, out for delivery, STAT pending, claim→start latency.
- Active trips — expandable rows with wards, picklists, and trip labels (
TRIP-XXXX). - On the rack tab — claim and start on behalf of a runner when needed.
- Date range on historical tabs — default last 7 days for completed and returned trips.
What makes it different
- Out for delivery shows all active trips immediately after kiosk start — no intermediate “claiming” state on the board.
- Server-side pagination — built for tenants with thousands of packed picklists on a rack.
- Same tile semantics as the kiosk — supervisors and runners speak the same language (Yours / Available / Taken).
When this isn’t the right lens
- Courier / 3PL tracking — use Fulfillment Queue dispatch dialog.
- Financial or inventory valuation — use Operations Intelligence KPIs, not this board.
- Runner step-by-step — use Dispatch Station kiosk how-tos instead.