Dispatch board

The dispatch board is where the operation runs each day. Lives at /app/road/dispatch.

Layout

• Left column — Unassigned legs — every leg that needs a trip, filtered by date, depot, and region.
• Middle — Trip lanes — one lane per trip. Each lane shows the assigned driver, vehicle, and the stops in order.
• Right column — Fleet availability — vehicles and drivers available for the selected date, with status (idle, on trip, maintenance, off-duty).

Drag a leg from Unassigned onto a Trip lane to attach it. Capacity + compatibility checks run on drop.

Creating a trip

Two ways:

1. Manual — + New trip → pick date, driver, vehicle, start depot. Add stops by dragging legs.
2. Auto-suggest — Suggest trips button runs a planner that groups unassigned legs by route and vehicle capacity, outputting draft trips. Dispatcher reviews and accepts.

Trip states

• Draft — being built, not released to driver.
• Released — visible in driver's app, driver can accept.
• In progress — driver has started.
• Completed — all stops done.
• Cancelled — manually cancelled; legs return to Unassigned.

State transitions are explicit. Releasing a trip sends a push notification to the driver's mobile app.

Filters

Filter by depot, date range, vehicle type, customer, cargo type (hazmat, reefer), subcontractor vs own. Saved filters per user.

Live status

Once trips are in progress, lanes show live progress: current stop, ETA to next stop, delay vs plan. Telematics feeds drive the live data; without telematics, the driver's mobile status updates fill in.

Bulk actions

• Release all drafts.
• Reassign driver / vehicle on multiple trips (e.g. when a driver calls in sick).
• Print trip sheets — a PDF per trip with stop list, addresses, contacts, cargo.

Conflicts

The board prevents:

• Two trips overlapping on the same driver / vehicle.
• Releasing a trip without a driver or vehicle.
• Assigning a driver whose licence / medical is expired.
• Over-capacity attachments.

Each conflict shows a clear message with the path to fix.