Delivery evidence

Dispatcher follows the load through ordered stops, recording observed arrival and departure times against the appointment windows. A proof reference gives the team a way to find the evidence for that stop. Load attachments retain supporting files with an evidence type, upload details and visibility choice.

At delivery, Dispatcher records the actual delivery time and follows the completion action to its receipt. The original promised time stays attached to the load. Transport Supervisor can compare the commitment with the observed result and inspect the evidence when a recipient or carrier disputes what happened.

• Follow the stop sequence. Dispatcher checks the address and appointment window for each planned stop. Actual arrival and departure remain separate observations. Sequence helps the receiving shift understand where the load has been and which stop is being discussed.
• Attach the supporting record. Dispatcher gives each file a useful title and evidence type, with the load parent and uploader retained. Internal and Shared distinguish the intended visibility. The team should choose visibility deliberately when the material contains information meant for a restricted audience.
• Record completion against the promise. Dispatcher saves the observed delivery time as the load reaches Delivered. Transport Supervisor compares it with the original promised delivery time. The completion receipt provides the action outcome, while stop references and files provide the supporting operating evidence.

Agree which source establishes arrival, departure and final delivery times. Decide what constitutes useful proof for the pilot and how staff name evidence files. A descriptive title should help another Dispatcher recognize the recipient or stop without opening every attachment.

Set the visibility convention with Transport Supervisor and rehearse it with the intended users. Define how the team handles a delivery observation that arrives late from an external source. Keep the original promise intact so a correction to observed evidence does not change what the organization had committed to deliver.

Use a rehearsal load with a promised delivery at 15:00. Dispatcher records arrival at the recipient at 15:20 and departure at 15:45. The supporting file confirms the handover time. Record the actual delivery time agreed for this operating case and complete the action, then inspect the resulting receipt.

Transport Supervisor compares the observed delivery with the unchanged promise and can trace the file to its uploader. Repeat the exercise with an attachment placed on the wrong load. Dispatcher should identify the mismatch before the file is relied on during review. The corrected evidence needs a clear load association.

Finally, have Auditor inspect the authorized evidence from a separate account. Confirm that internal material follows the agreed access scope and that a visible proof reference leads staff to the intended supporting source.

• Load Stops by Sequence — Appointment windows beside observed arrivals, departures and proof references.
• Evidence Attachments — Load files with uploader, evidence type and visibility.
• Delivered Loads — Completed movements with promised and actual delivery times for comparison.

Follow Delivery and evidence and use Exception reconciliation for a disputed completion outcome.