dispatcher support
A Dispatch Board Exception Queue for Weather Reroutes
A practical exception queue for handling weather reroutes on a dispatch board without losing load commitments, driver hours, or customer communication.
Trucking VA Team · · 4 min read

Table of contents8 sections
A weather system can invalidate a dispatch board in an hour. Roads close, appointments slip, and drivers who were legal on hours become tight after a detour. The dispatcher is then managing two jobs at once: recovering the loads already in motion and protecting the loads that have not yet started. Without a separate exception queue, those two jobs blur into a long list of urgent messages.
An exception queue keeps the weather-driven items in one place with an owner, a decision, and a deadline. It does not replace the dispatch board. It sits beside it and answers a narrower question: what must be decided now because the plan changed? That separation makes the work visible and keeps routine load updates from being buried.
Open the queue when the plan changes
Start the queue when a weather event is likely to affect a lane, an appointment, or a driver's available hours. Record the source of the warning and the time it was received. A forecast is not a fact, so label it as a watch until a road closure or a customer notice confirms the impact.
Each row should name the load, the driver, the affected segment, the original appointment, and the customer contact. Add the reason code: road closure, severe weather, shipper delay, receiver delay, or driver hours. The code helps the team see which recovery path applies.
Separate rolling loads from planned loads
A load already in transit needs a different response from a load that has not been picked up. For rolling loads, the queue should capture the driver's location, remaining hours, fuel status, and the next safe stop. For planned loads, it should capture whether the shipper will hold the appointment or whether the load needs to be re-powered.
Mixing the two creates confusion about urgency. A rolling load with a closed road may need an immediate decision. A planned load tomorrow may only need a customer update. Keep the two lanes visible and assign different review cadences.
Protect hours before chasing the appointment
When a reroute adds miles, the first constraint is often the driver's available hours, not the appointment window. Record the driving time to the alternate route, the remaining legal hours, and the rest requirement. If the alternate route cannot be completed legally, the queue should show the next safe option rather than a schedule that cannot be met.
The dispatcher should not ask a driver to skip a required rest to recover a load. That decision belongs to the carrier's safety process, not to a weather exception. Note the constraint and escalate it. A late load is recoverable; a safety violation is a different kind of cost.
Give every exception an owner and a clock
Each row needs a named owner and a next decision time. The owner may be the dispatcher, a customer service lead, or a manager. The clock is the point by which the decision must be made to preserve an option, such as a re-power window or a customer cutoff. Without a clock, the queue becomes a status list.
Set the clock from the operational constraint, not from convenience. If a receiver closes at 5 p.m., the decision about a late arrival must happen well before then. If a driver must rest, the re-power decision has a hard boundary. Write the boundary in the row.
Communicate one version to the customer
Weather events generate rumors. The customer may hear about a closure from another source and call in with a different understanding. The queue should hold the approved customer message and the time it was sent. One owner should be responsible for the external update so the story does not change with each dispatcher.
The message should state what is known, what is not known, and when the next update will come. Avoid promising a new delivery time before the route and hours are confirmed. A short, honest update preserves trust better than an optimistic estimate that has to be revised twice.
Close the exception with evidence
Close a row only when the recovery is complete: the load is re-powered, the appointment is rescheduled, the customer has agreed, and the driver has a confirmed plan. Record the evidence, such as a confirmation number, a message timestamp, or a revised rate confirmation. A row closed with a note that says "handled" cannot be reviewed later.
If the exception becomes a claim or a service failure, the record should show what was known and when. That history protects the carrier and helps the team improve its weather playbook.
Review the event after the fact
After the weather clears, review the queue for patterns. Which lanes were affected first, which customers needed the most communication, and where did the re-power options run out? A short review turns a stressful event into a playbook for the next one.
Do not use the review to assign blame. Weather is not a performance failure. The useful question is whether the process gave the dispatcher enough time and information to make the decisions the event required.
Key takeaways
- Open a separate exception queue when a weather event threatens lanes, appointments, or driver hours.
- Split rolling loads from planned loads and give each lane its own review cadence.
- Protect legal hours before chasing an appointment, and escalate any conflict to the safety process.
- Give every row an owner, a decision clock, one customer message, and closure evidence.
A weather reroute is a planning problem under time pressure. An exception queue does not make the weather predictable. It makes the decisions visible, owned, and reviewable, which is what a dispatch team needs when the board changes faster than the plan.
For related workflows, see the dispatcher board handoff guide and the trucking VA services overview.