Dispatch and Delivery

The Dispatcher starts from the reviewed load and its resource assignment. Stops describe the planned pickup, delivery and service work. Tracking events add the reported journey, including departures, arrivals, delays and exceptions. Each event retains its source and current state so the team can inspect where the information came from.

Delivery proof belongs to the load and the relevant stop. It records the delivery date, recipient and signature reference, together with a Captured, Verified or Disputed status. The Operations Reviewer uses that evidence to decide whether the recorded completion can be trusted. A tracking event that says Delivery is useful context, but the reviewer still checks the actual proof required for the case.

• Dispatch the assigned scope. Confirm the intended driver, vehicle and assignment period before following the load into execution. Keep the current load revision and stop sequence available to the team.
• Record stop progress. Follow Planned, En Route, Arrived and Completed stop work, with Missed used where that is the recorded outcome. Retain actual arrival and departure dates separately from the appointment and service window.
• Review delivery proof. Capture the recipient and signature reference against the correct load and stop. The Operations Reviewer verifies eligible proof or keeps a disputed result visible for investigation before accepting completion.

Agree which journey reports come from your dispatch team and which arrive through connected driver, telematics or partner services. Decide who checks a reported event before it is confirmed and how a later report supersedes it. Keep the source visible so the Dispatcher can investigate a disputed arrival.

Define what evidence is sufficient for delivery verification and who resolves a disagreement about the recipient or signature reference. Set the handoff when a stop is Missed or a delay changes the promised delivery commitment. The Fleet Planner needs to understand the changed scope before the team relies on a revised plan.

Use a depot pickup followed by a customer delivery. Record the departure and arrival events and inspect their sources. At the delivery stop, capture the recipient and signature reference. Ask the Operations Reviewer to compare the proof with the load, stop and actual delivery date before accepting it as Verified.

Next, rehearse proof attached to the wrong stop and a disputed recipient. Keep those cases out of verified completion until the discrepancy is resolved. Repeat an uncertain completion request and inspect the operation evidence before recording another effect. The Finance Officer can then follow the verified delivery context when reviewing freight charges, without assuming that delivery verification also establishes invoice payment.

• Stop Progress Board — Planned, En Route, Arrived and Missed stop work grouped for dispatch follow-up.
• Delivery Proof Review — Captured proof awaiting a decision on the load and stop it supports.
• Assignment Schedule — The driver and vehicle period behind the dispatched scope.

Follow dispatch and delivery proof, then correction and reconciliation when the recorded outcome needs investigation.