Broadcast Pipeline
Send a mission offer to multiple eligible drivers simultaneously — dispatch mode choice, broadcast tracking, driver proposals, and the anti-duplicate safeguard (FR395).
Overview
Broadcast mode (screen G-04) sends a mission offer to multiple eligible drivers at the same time. The first driver to accept is automatically assigned. All other pending offers are withdrawn immediately. This is the preferred dispatch method when speed of acceptance is the priority and you have no pre-assigned driver in mind.
When to use it: use broadcast when you want the market to determine who takes a mission, when you need to fill a last-minute request quickly, or when your eligible driver pool is large and you do not want to choose manually.
Dispatch mode choice — modal G-07
When you trigger dispatch for an unassigned mission (from any view — Gantt, List, or Map), the Dispatch mode modal (screen G-07) appears first. It presents two options:
| Option | Description |
|---|---|
| Assign directly | Opens the Direct Assignment wizard (G-06) where you pick a specific driver |
| Broadcast | Opens the broadcast configuration panel (G-04) |
Choose Broadcast to proceed with the pipeline described below.
Configuring the broadcast
On the broadcast configuration panel you set:
Driver pool
Select which drivers receive the offer:
- All eligible — every driver available in
[pickupAt, estimatedEndAt]with a compatible vehicle category - By vehicle category — restrict to a specific class
- Custom selection — manually pick drivers from a list
Drivers who do not meet the base eligibility criteria (availability overlap, vehicle category, active licence) are excluded automatically regardless of pool setting.
Offer expiry
Set how long drivers have to respond before the offer expires. The default is 5 minutes. If no driver accepts within this window, the mission returns to "Unassigned" status and you receive a notification.
Distance filter (optional)
Optionally restrict the pool to drivers currently within N km of the pickup point. This reduces irrelevant notifications for distant drivers.
FR395 — Broadcast anti-duplicate
FR395 — Broadcast Anti-Duplicate ensures that a driver never receives a second offer for the same mission if they have already responded (accepted, declined, or let it expire).
This matters when:
- A broadcast expires without acceptance and you launch a second broadcast.
- You manually restart a broadcast after adjusting the driver pool.
The system tracks per-mission, per-driver response history. Drivers who have already responded are excluded from subsequent broadcast rounds for that mission. To include a previously excluded driver, an operator with admin rights can manually override this lock from the mission's dispatch history.
Monitoring the broadcast in progress
Once a broadcast is live (screen G-04), the monitoring panel shows:
- Offers sent — number of drivers who received the notification
- Pending — drivers who have not yet responded
- Accepted — the driver who accepted (if any); triggers immediate assignment
- Declined — drivers who explicitly declined
- Expired — drivers who did not respond before the offer timeout
The list updates in real time via SSE. You can cancel the broadcast at any time; all pending offers are withdrawn and the mission returns to "Unassigned".
Driver acceptance flow
From the driver's perspective:
- The driver receives a push notification: mission reference, pickup time, origin, destination, and client category.
- They have until the offer expiry to accept or decline.
- If they tap Accept, the system checks that no conflicting assignment was created between offer send and acceptance (race-condition guard).
- If the check passes, the driver is assigned and all other offers are withdrawn.
- If the check fails (another driver was assigned first), the accepting driver is notified that the mission is no longer available.
After acceptance
Once a driver accepts:
- The mission status updates to "Confirmed" (or "Assigned", depending on your workflow configuration).
- The driver receives full mission briefing details on their mobile app.
- The assignment is reflected in the Gantt, List, and Map views.
- The broadcast history is preserved in the mission's dispatch timeline for audit purposes.
Related pages
- Direct Assignment — assign a specific driver with optimistic locking (FR394)
- Crew Modes — broadcast can target a crew configuration instead of a single driver
- Gantt View — visualize the assignment on the timeline after acceptance
- RSE Compliance — compliance checks that filter the eligible driver pool
Map View
Monitor live driver positions, manage last-minute assignments geographically, and respond to the "Signal Lost" alert (FR393).
Crew Modes
Configure the number of drivers for a mission — single driver, double crew, and relay driver — and understand how each mode affects dispatch and RSE compliance.