Exceptions and reconciliation

A load in Exception needs a clear explanation of what interrupted the intended movement. The Dispatcher starts with the load and its current revision, then brings the relevant evidence to the Transport Supervisor. A failed operation may require investigation even when the underlying load record has already changed, so read the receipt before attempting the action again.

Operation receipts retain the action, stable key and expected revision with the result and effect references. The supervisor compares those claims with linked local evidence and the authoritative external source where needed. Operations Overview helps the team triage active loads, pending review decisions and failed operations alongside delivery performance.

• Operational exception. The Dispatcher identifies the affected load and evidence. Vehicle readiness or defect information may help explain why the planned resource could not proceed.
• Corrective authorization. The Transport Supervisor reviews a proposed correction independently. Preserve the original decision and movement evidence when executed work needs a compensating action.
• Receipt reconciliation. Compare failed or uncertain results with the actual effects. Keep a concrete discrepancy on an item needing review until authoritative confirmation supports the outcome.

Agree when the Dispatcher marks a load as an exception and what supporting evidence the supervisor needs. Distinguish unexecuted scope that can be canceled under the procedure from movement or external work that already occurred. Define who contacts the responsible external operator when a correction affects work controlled elsewhere.

Configure reconciliation as an evidence check with guarded result updates. Decide how the supervisor finds the expected load revision and verifies each effect reference. A repeated request should use the agreed operation identity and be examined for an existing result before execution. Agree how the team records an unresolved discrepancy so the next shift can continue the investigation without reconstructing the failure from memory.

Rehearse a planned cross-dock movement whose assigned vehicle enters Maintenance before dispatch. The Dispatcher reads the readiness and related defect evidence, then identifies the affected assignment and load. Bring the proposed resource change to the supervisor under the agreed exception procedure and retain the evidence explaining why the original arrangement changed.

Next, inspect a failed dispatch or completion receipt. Compare its expected revision and recorded effects with the current load and movement observations. If the evidence is incomplete, keep the result under review with a specific discrepancy. Rehearse a cancellation of unexecuted scope separately from a correction after pickup, and confirm which person must authorize each step before anyone contacts an external operator.

• Loads in Exception — Find loads requiring an operational decision and identify their owners.
• Operation Receipts Default List — Investigate Pending, Failed and Needs review results.
• Vehicle Defects Default List — Read defect severity, repair evidence and release dates when reviewing readiness.

Rehearse exceptions and reconciliation and assign connection responsibilities under integrations.