Delivery evidence

Dispatcher completes a load after obtaining the recipient proof reference and actual delivery time. The relevant stop keeps its proof reference alongside actual arrival and departure. The load records the actual delivery and retains the original promised time, giving Transport Supervisor and Auditor a clear basis for examining performance.

A scan labeled Delivered is useful parcel evidence, but the load may contain other parcels or an unresolved recipient handoff. Check the whole load before closing it. Partial or refused service remains an explicit Exception with supporting evidence available to the next person who investigates the outcome.

• Stop handoff. Read the planned stop sequence and windows, then collect actual arrival, departure and recipient proof. Admin maintains the stop record while Dispatcher prepares the delivery evidence through the agreed operating procedure.
• Load completion. Dispatcher checks actual delivery time and the recipient proof before requesting Delivered. Keep incomplete or refused work in the exception path so a completed label does not hide remaining service.
• Performance review. Transport Supervisor compares actual delivery with the original promise. Operations Overview brings on-time performance, delivery-week charts and late-delivery information into the broader review of active and exceptional loads.

Agree what the recipient proof reference must identify and where the supporting document or physical handoff evidence is stored. Establish how the dispatcher retrieves it when a partner reports delivery before the document is available. Use the same load and stop references throughout the handoff so a proof belonging to another delivery cannot close this one.

Define the operating time zone and the interpretation of the promised delivery time. Retain that promise when later operational estimates change. Decide how the team records the circumstances of partial or refused service and who collects the evidence needed for a later correction or completion attempt.

Use a load promised for 16:00 that reaches the recipient at 16:18. Dispatcher obtains the actual delivery evidence and the proof reference for the correct stop. Record the completed service against the original promise so the late result remains visible. Replacing the promise with the eventual arrival time would erase the operating question the performance review needs to answer.

Next, rehearse a partner message stating that a parcel was delivered while the recipient refused the remainder of the load. Keep the load as Exception and preserve the accepted parcel scans and supporting attachments. Finish with a complete load whose proof reference belongs to another stop. Require the mismatch to be resolved before delivery completion can succeed, then inspect the operation receipt for the accepted outcome.

• Delivery evidence queue — Loads that are dispatched, in transit or in exception, with the original promise and actual service times.
• Delivered loads — Completed delivery outcomes ready for comparison against their promised time.
• Stop handoffs — The stop windows, actuals and recipient proof references behind a delivery decision.

Follow Complete an evidenced delivery, then use Reports to examine delivery timeliness and the underlying evidence.