Stops and delivery evidence

Each load can have ordered pickup, delivery or service stops. A stop belongs to a parent load and carries a line number, revision and sequence. Address and window times describe the expected visit. Actual arrival and departure times show what occurred, while a proof reference points the team to the supporting record. This gives the Dispatcher a way to explain the load’s path without compressing every event into the load’s status.

The load itself carries promised delivery, actual pickup and actual delivery times. The stop detail gives context when the overall promise and actual outcome differ. Record attachments on the load can hold the documents the team uses during review; their title, evidence type, visibility and uploader make the evidence easier to trace.

The Dispatcher reviews the load and its stop plan. The Transport Supervisor and Auditor inspect the resulting route and evidence within their authorized scope.

• Ordered sequence. Stop position and line number keep pickup and delivery work understandable.
• Service window. Start and end times show the planned visit interval.
• Recorded arrival. Actual times and proof reference help explain the outcome.

Agree which stops are required for a routine container movement and how the address should be written. Decide whether the stop window reflects a carrier appointment, terminal slot or customer delivery agreement. Define the source for actual arrival and departure and who records a correction when a timestamp is wrong. Choose how a proof reference maps to the document or event system already used by the team.

An attachment’s visibility matters when external parties and internal reviewers share a load. Decide which evidence should be shared and who may upload it. During import, preserve the stop order and parent load reference; a list of addresses without sequence loses the dispatch plan.

A load has a terminal pickup followed by a delivery stop. The ordered stops show each address and window; the Dispatcher checks that the load’s promised delivery agrees with the second stop’s plan. The transport partner receives the operating details through the team’s established process. When the driver arrives, the corresponding stop’s actual arrival and departure times show what occurred.

Suppose the terminal pickup runs late. The Dispatcher can see the missed window on Load Stop Windows and mark the overall load as an exception if required by the team’s policy. The proof reference and any uploaded document remain attached to the load. The supervisor uses those records when examining why actual delivery differed from the promise.

• Load Stop Windows — Stops whose windows have begun, with planned and actual times.
• Active Loads — Current load promises and responsible owners.
• Operations Overview — Authorized activity for the load’s owner and organization.

• Plan and dispatch a load.
• Reconcile operation evidence.