Load Context and Delivery

A load provides the operational record behind the coaching discussion. It carries a record number, subject, owner, transport partner and promised delivery time. Its organization identifies the responsible carrier scope. The equipment class and freight amount provide additional commercial context, while the lifecycle shows whether the load is planned, moving, delivered or needs attention.

Ordered stops retain the addresses and time windows used by the team. Actual arrival and departure times and proof references help explain what happened during the movement. Dispatcher can use that evidence when preparing a coaching session associated with the load, keeping the incident reference aligned with the operation the reviewer is examining.

• Planned movement. Dispatcher prepares the load with its organization, owner and eligible transport partner. The planning action establishes the Planned load and its driver and vehicle assignment. Review the promised delivery and equipment context before the operation starts.
• Physical progress. Confirm actual pickup before following the dispatch and in-transit stages. Record the pickup time and retain stop-level arrival and departure evidence as available. Keep an exception visible when the operating result needs attention, with supporting evidence that explains the situation.
• Delivery outcome. Recipient proof and actual delivery time support marking the load Delivered. Retain the proof reference and relevant files so the supervisor can inspect the result. Delivery records the movement’s outcome; coaching completion and carrier financial settlement each follow their own process.

Agree what establishes physical pickup and which recipient evidence supports completion of a delivery. Define how stop windows and actual times are interpreted in the organization’s time zone. Check the transport partner’s eligibility note and the staff responsible for maintaining the counterparties used on loads.

Decide how an incident reference relates to the load’s stop and proof evidence. If an external recording system supplies the incident, retain the reference needed to find the relevant material. Agree who checks that the session describes the correct driver and movement. The reviewer should be able to reconstruct the context from the retained records without treating an unrelated delivery file as coaching evidence.

Use an illustrative load with a pickup and delivery stop. Dispatcher confirms physical pickup, records its actual time and follows the load into transit. The stop records retain the observed arrival and departure times. On delivery, recipient proof and the actual delivery time support the Delivered outcome, with the evidence available under the same load.

Prepare a coaching session concerning an incident during that movement. Confirm the incident reference and relevant stop context, then attach the supporting material to the load. Transport Supervisor should be able to locate the correct event while still distinguishing the delivery result from the session’s review state. Repeat the case with recipient proof missing and check that a successful delivery outcome is not accepted from the status request alone.

• Active Loads — Planned and moving loads, plus exceptions, with owners and promised delivery times.
• My Loads — Assigned operational work for the current staff member.
• Stop Windows — Stop timing and proof context for the load being reviewed.

Follow load movement and evidence, then carry the relevant context into coaching preparation and review.