Dispatch and delivery

Dispatcher reviews an Assigned driver and vehicle combination against its Approved load before departure. The departure handoff moves the load into Executed and the assignment into Active, with a departure event recording what happened. These records should tell the same story before the next Dispatcher relies on them. A change in planned work needs attention before it becomes a confusing trip history.

Stops carry their sequence, location and appointment time. Planned, En Route, Arrived and Completed describe progress; Missed and Cancelled keep exceptions visible. Tracking events add the reported time, location and event type, with a source that identifies where the information came from. The team can distinguish a reported milestone from a confirmed one during review.

• Check departure together. Confirm the linked load and assignment are ready, then review the load outcome, departure event and active assignment as one operating handoff.
• Record stop progress. Dispatcher follows pickup, delivery and service stops in their intended sequence. Keep a missed appointment visible instead of replacing it with an unexplained completed result.
• Capture delivery evidence. Record the recipient, delivery time and signature reference against the correct load and stop. Captured evidence goes to Evidence Reviewer for verification or dispute follow-up.

Agree who records departure and who confirms tracking events received from a driver or partner. Use consistent time zones for planned dates, appointments and actual outcomes. A source label of Telematics identifies the origin of an event; arrange and test the provider connection before relying on imported position updates.

Decide what evidence the team needs for delivery and how to handle a signature belonging to the wrong stop. Review the relationship between actual delivery, completed assignment and proof of delivery. Keep unresolved exceptions in the review queue so a hurried status change does not hide the need to contact the driver or customer. Discuss how corrections will retain the actual trip context.

An assigned truck leaves the depot for a load with an approved destination. Dispatcher records the departure and later marks the delivery stop Arrived. The driver reports delivery, but the signature reference points to a neighboring customer’s document. Dispatcher retains the actual arrival information and sends the captured evidence for review.

Evidence Reviewer marks the proof Disputed while the team obtains the correct reference. The load’s physical delivery and the evidence dispute describe different parts of the case. Rehearse the handoff until Dispatcher can explain the actual trip and Evidence Reviewer can identify what still needs checking. Review a second attempt to record departure so the team knows how to detect a repeated event or a partially completed handoff.

• Active Loads — Review loads awaiting a decision alongside approved work and active trips.
• Delivery Evidence — Review captured confirmations and disputed delivery details.
• Freight Charge Review — Inspect load-linked charges with their currency and current billing status.

Use dispatch to delivery for trip progress and evidence to verification for unresolved outcomes. Agree external tracking and accounting handoffs on the integrations page.