Skip to main content

Trucking Dispatch Alerts

What this feature does​

Trucking dispatch alerts help dispatchers spot schedule risk without taking attention away from the leg itself.

The system can show:

  • Actionable timing alerts when a dispatcher likely needs to do something
  • Informational timing notes when the system wants to surface timing confidence or data quality
  • Workflow status so the team can see whether an alert is still pending, reviewed, ignored, or needs a rest plan

Where dispatchers see alerts​

In the web dispatch scheduler, open a trucking leg to view its details.

The alert area appears in the leg details modal as a compact Alerts section. It is collapsed by default to reduce noise and can be expanded when the dispatcher needs more detail.

How alerts are organized​

Actionable alerts​

These are operational alerts that may require dispatcher follow-up.

Common examples:

  • A trip exceeds expected legal driving limits and needs a rest plan
  • The leg timing suggests dispatch should review the plan before release
  • The trip spans multiple days and needs confirmation

Informational notes​

These are lighter timing notices that do not automatically mean the schedule is in trouble.

Common examples:

  • Fallback route timing was used
  • Cached route timing may be stale
  • Timing was calculated with lower confidence than normal

Review states​

Each alert can show a workflow state so dispatch can quickly understand where things stand.

  • Pending Review: no review action has been taken yet
  • Reviewed: the dispatcher reviewed the alert and no further follow-up is currently required
  • Reviewed - Follow Up: the dispatcher reviewed the alert, but a follow-up step is still open
  • Ignored: the dispatcher chose to mute the alert workflow for this leg

Color meaning​

The alert workflow uses color to reduce scanning time:

  • Amber: follow-up is still needed
  • Blue: reviewed and currently complete
  • Gray: ignored or muted

What the actions mean​

  • Mark Reviewed: records that dispatch reviewed the alert
  • Message Driver: opens driver communication without changing alert workflow status
  • Add Rest Plan: records that the leg still needs a documented rest-plan decision
  • Ignore: hides the alert workflow for that leg
  • Ignore Rest Plan: clears the rest-plan follow-up when dispatch decides it is not needed

How the modal behaves​

  • The Alerts section stays small by default so route, stop, and leg details remain visible
  • Expanding the section shows the full alert detail and workflow actions
  • After the main action is taken, the workflow area can collapse into a summary view
  • If follow-up is still needed, the modal keeps the next relevant action available

Example dispatcher workflow​

  1. Open a leg from the dispatch scheduler
  2. Expand Alerts only if you need detail
  3. Review the alert details
  4. Choose the appropriate action:
    • mark reviewed
    • message the driver
    • add a rest plan
    • ignore the alert
  5. Confirm the workflow color and status changed as expected

Tips for teams​

  • Treat amber alerts as open operational work
  • Treat blue alerts as reviewed history unless a new timing issue appears
  • Use gray only when your team intentionally wants to mute the workflow for that leg
  • Expand alerts when needed, but keep them collapsed during normal leg review to reduce clutter