Delivery evidence

Dispatcher follows the load after pickup and records what happened at each stop. Appointment windows remain beside actual arrival and departure times. At delivery, the actual delivery time supports a comparison with the customer’s promise, while the proof reference and attached evidence explain the outcome.

A delivery record needs more than a final status. Operations Analyst may need to answer when the truck arrived, which stop was involved and where to find the supporting document. Keep that evidence linked to the load so the team can investigate a delay without asking the driver to recreate the journey from memory.

• Preserve the appointment. Keep the agreed opening and closing window for the stop. Record actual arrival and departure separately, including a delay that occurs while the truck is already at the location.
• Connect the proof. Enter the stop’s proof reference and attach the relevant evidence to the load. Give the attachment a useful title and evidence type so the next person can identify what it supports.
• Close with actual times. Record the delivery time and reconcile the assignment’s completion. Retain the promised delivery time for performance review even when the arrival was later than expected.

Agree which document or source establishes delivery and who checks it. Define attachment visibility before sharing evidence outside the operating team. Some documents may be appropriate to share while internal review notes need restricted access. Decide who corrects a mistaken attachment or timestamp and how the original record remains available.

If delivery evidence comes from a carrier portal or telematics provider, configure that connection with stable source references. Agree the time-zone mapping and the meaning of arrival, departure and final delivery. A repeated incoming event should lead the team to the existing outcome instead of creating another completion action.

A driver reaches the delivery location before the appointment closes, but unloading finishes later. Dispatcher records arrival and departure against the stop and records actual delivery according to the agreed completion rule. Operations Analyst can then distinguish timely arrival from a late completed delivery without changing the original promise.

During the rehearsal, attach a delivery document to the wrong load and have Dispatcher identify the mistake before completion. Repeat the exercise with a correct proof reference but no supporting file. The team should follow its evidence rule and keep any unresolved question visible. When the complete-delivery action is repeated, inspect its operation outcome and verify that the original delivery evidence remains intact.

• Evidence Attachments — Documents grouped with their load, evidence type, uploader and visibility.
• Load Stops by Sequence — Stop appointment windows alongside actual movement and proof references.
• Load Board by Lifecycle — Dispatched, in-transit and excepted loads that still need attention.

Use delivery and proof for completion and exception reconciliation when an action or its evidence disagrees. Compare results using the report definitions.