Exceptions and reconciliation

A load marked Exception describes an unresolved service outcome. An operation that is pending, failed or needs review describes an action whose effects need attention. Transport Supervisor examines both kinds of evidence, using the load reference to connect the operating problem with the action that tried to change it.

Each operation retains a stable key, expected revision and result state. External and effect references help the supervisor inspect what actually happened. Dispatcher can request a correction within authorized scope without deleting the earlier scan, stop evidence or review decision that explains how the load reached its current condition.

• Read before retrying. Transport Supervisor examines pending and failed operations and follows their effect references. Compare scope, identity, quantities and revision before accepting completion or considering another execution attempt.
• Correct within scope. Dispatcher distinguishes an unexecuted draft from accepted or executed work. Read the current load revision and related stops, decisions and receipts before a correction; an equivalent repeated request returns the prior result.
• Retain evidence. Preserve accepted parcel milestones, recipient proof and uploaded files. Titles, evidence type, uploader and upload time help Auditor find the material supporting a later explanation.

Agree who owns unresolved actions at shift change and what comparison is required before an operation can be marked Completed. Define how the receiving process records external event identity and local effect references. Staff need to find the actual outcome after a timeout without guessing whether another attempt is harmless.

Choose attachment visibility deliberately and test it with the operating identities. Internal and Shared identify intended evidence audiences; the team should know who can actually read a file before using it in a partner handoff. Agree how a correction preserves original history while making the new authorized result easy to follow.

Use a parcel scan acceptance that times out after its local effect has been written. Dispatcher sees the unresolved operation and asks Transport Supervisor to inspect it. The supervisor compares the expected revision with the accepted scan and checks the linked effect before recording completion. Repeating the action must not create another accepted copy of the same provider event.

Repeat with an effect reference pointing to a different load. Leave the operation needing review with the discrepancy explained. Then rehearse cancellation of an eligible unexecuted plan and repeat the same request. The original result should remain available, while previously executed pickup or scan evidence remains intact. These cases give the next shift a concrete way to distinguish a recoverable action from service that still requires investigation.

• Operation exceptions — Actions that are pending, failed or need review, with their expected revision and effect references.
• Load exceptions — Loads whose service outcome remains an explicit Exception.
• Internal load evidence — Attachments available to authorized staff investigating the load.

Use Correct and reconcile for the investigation and Accept a parcel scan for its original review boundary.