1. Warehouse-to-Truck Loading
  2. Features
  3. Dispatch and delivery
Feature · Dispatch and delivery

Dispatch and delivery

Follow the truck from departure through stop events to delivery evidence.

OverviewReported tracking events
Warehouse-to-Truck Loading · Dispatch and delivery

Reported tracking events

Tracking events

New
Event numberLoadEvent typeOccurred atLocationSource
TE-80998LDS-58210Departure04 OctA-14Driver App
TE-85818LDS-49349Arrival08 OctP-7Telematics
TE-16337LDS-86171Stop Arrival03 OctF-16Dispatcher
TE-90979LDS-26813Stop Departure04 OctY-6Partner
TE-60512LDS-91371Delay10 OctS-18Driver App
6 of 6 records
A-14Tracking events · TE-80998
Departure
LoadLDS-58210
Occurred at04 Oct
SourceDriver App
StatusReported
Example screen with sample data

What you can do

Keep departure and delivery evidence with the load

Dispatch Coordinator records the actual pickup and a departure event when the truck leaves. The load moves into dispatch work, and the assignment identifies the driver and vehicle responsible for that journey. Approval of the loading check remains available for the handoff, while later movement has its own event history.

Tracking events carry a location, event type, time and reporting source. Staff can distinguish a dispatcher entry from information attributed to a driver app, telematics provider or partner. Set up the required connection before using an external source for ongoing updates.

How the work is organized

Each stop retains its appointment window and actual arrival and departure. Evidence Coordinator captures delivery confirmation against the load and the relevant stop, including the receiver and signature reference.

  • Record the departure. Confirm the load and assignment at the physical handoff, then record the pickup time and Departure event. Move the load to Dispatched using that observation.
  • Follow stop progress. Keep En Route, Arrived and Completed states aligned with the observed movement. Record Delay or Exception events when the journey departs from its plan.
  • Review delivery proof. Capture the delivery time, receiver and supporting signature reference. Keep Captured and Disputed evidence visible until the verification decision is clear.

What to agree during setup

Agree which person records movement when the driver cannot send an update. Decide what evidence establishes arrival or delivery for each customer arrangement. Keep the event occurrence time meaningful even when the office receives the information later.

Confirm how to identify the right stop on a load with several visits. A signature from the pickup location must not be accepted as delivery evidence at the customer. Define how to handle a missed appointment and which staff member contacts the receiver to establish the next action.

Check the handoff on an actual case

A truck leaves on time but reaches the customer after the agreed window. Dispatch Coordinator records the delay and actual arrival. The customer accepts the cargo, but the signature reference is initially unavailable. The delivery occurrence and evidence review now need separate follow-up.

Evidence Coordinator captures the receiver and delivery time, then requests the supporting document. The record remains Captured while that check is pending. If the receiver disputes the quantity or signature, record Disputed and retain the notes for Transport Supervisor. A journey marked Delivered still needs its delivery evidence reconciled.

For rehearsal, give the next shift a reported arrival followed by a correction from the partner. Ask staff to distinguish the superseded event from the confirmed observation. They should find the relevant stop and explain the delivery position without assuming every incoming update is equally reliable.

What your team sees

  • Active Loads — Planned, dispatched, in-transit and exception loads for the active handover.
  • Reported tracking events — Incoming movement observations awaiting confirmation.
  • Delivery evidence review — Captured and disputed delivery proof requiring investigation.

Follow the work through

Follow dispatch to delivery, then correction and reconciliation when evidence disagrees with the reported outcome. Review connections before importing partner events.

What it keeps track of

Data model
Loads
Planned and executed transport loads
Load assignments
Driver and vehicle assignment for a load
Load stops
Pickup, delivery and service stops on a load
Tracking events
Position and milestone events reported against a load
Proof of delivery
Delivery confirmation captured at the stop
Record attachments
Documents, photos and signature evidence attached to records

Who uses it

Permissions
Dispatch Coordinator
, Evidence Coordinator, Transport Supervisor.
Dispatch Coordinator
Owns movement updates; Evidence Coordinator checks delivery proof against the journey.

Set up Warehouse-to-Truck Loading your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started