Exceptions and corrections

An exception needs a clear owner and a decision about the work that remains. The Dispatcher identifies the affected load and retains the actual pickup, stop and delivery information already recorded. The Transport Supervisor reviews the proposed correction or cancellation against that operating history.

The correction action retains a compensating operation receipt and preserves the original evidence. Cancellation applies to unexecuted scope. Effects controlled by an external system need confirmation from the responsible source, so the team investigates what actually happened before assuming that a local change has reversed an outside action.

• Exception context. The load retains its owner, transport partner and original promised delivery time. Actual movement and supporting attachments help the reviewer understand which parts of the plan have already happened and which remain open for a decision.
• Authorized correction. The Transport Supervisor reviews the intended action and records the reason. The decision needs to refer to the current load revision so the Dispatcher can distinguish the approved correction from an earlier discussion of a different plan.
• Retained effects. The compensating action’s receipt links the result to the original operating evidence. Inspect its outcome and references. An unresolved discrepancy stays visible for reconciliation rather than being treated as a completed correction simply because a request was made.

Agree which operating situations enter exception review and who informs the transport partner. Define the evidence the supervisor needs to distinguish executed movement from remaining scope. Explain who can authorize cancellation and which outside effects require action by another system’s owner.

Set a method for recording the correction reason and keeping supporting files accessible to the reviewer. Decide who investigates failed or uncertain correction receipts. The Dispatcher and Operations Analyst should know where to find the original action evidence and the later compensating result when reconciling the case.

A load has been picked up when a problem prevents the remaining movement from continuing as planned. The Dispatcher records the actual operating information and marks the load for exception handling. Attach the evidence that explains the issue and identify the remaining work for the Transport Supervisor.

The supervisor reviews the current load and authorizes the appropriate correction. Where unexecuted scope is canceled, retain the cancellation decision and compensating receipt alongside the original dispatch evidence. Confirm any externally controlled effects with their responsible source before telling the team that the wider case is resolved.

Repeat the case with a correction attempted against an older load revision. The team should recognize that the current scope needs review before acting. Then inspect a failed correction receipt and trace its references. The Operations Analyst should be able to explain what is known, which effect remains uncertain and who is responsible for confirming it without re-running the external work.

• Load exceptions — Excepted loads with ownership, promised delivery and retained actual movement times.
• Operation Receipts Default List — Failed actions and results needing review, including correction attempts.
• Evidence Attachments — Supporting files used to explain the original problem and the authorized response.

Follow delivery and correction, then operation reconciliation.