Review and evidence

Review Manager records an approval, rejection or return with a reason, timestamp and reviewer. The decision points to the parent load and the source revision examined. This matters when a dispatcher changes the load after submission: a decision on an older revision should not be mistaken for approval of the new one.

Attachments preserve evidence with a title, evidence type, uploader, upload time and visibility. Internal and shared visibility support different audiences while retaining one load link. Pickup and custody discussions can therefore refer to the same case rather than copying documents into separate threads.

Operation receipts record the action, stable operation key, expected revision, result, occurrence time and any external reference or failure reason. Completed, failed and needs review are separate outcomes. Operations Analyst investigates a failed receipt by reading linked effects first. If the expected effect is unresolved, the receipt remains marked for review with the discrepancy; the investigation does not repeat external work merely to see whether it succeeds.

• Independent decision. Reviewer and source revision make approval traceable.
• Evidence file. Visibility and evidence type explain how an attachment may be used.
• Operation outcome. Stable keys and result states support safe reconciliation.

Agree which decisions require a reviewer outside the dispatch role, how reasons are written and who can see shared attachments. Set a response path for failed operation receipts and an authoritative source for confirming external effects. Decide how the team records an exception on a load while retaining the original pickup and delivery evidence.

Take an excepted load with a failed dispatch receipt and an attachment from the collection center. Operations Analyst reads the receipt’s key, revision and linked effect references. Review Manager inspects the original load evidence and records a decision with a reason. If the external effect is uncertain, keep the receipt in needs review until the authoritative source confirms it. If a correction cancels unexecuted scope, retain the original receipt and decision so a later analyst can understand the whole sequence. The load’s promise and actual events should remain available for delivery performance analysis.

• Operation Receipts Default List — Pending, completed, failed and needs-review actions with their reason and occurrence time.
• Evidence Attachments — Files linked to the load, labeled by evidence type and visibility.

See the operating process and implementation for the first rehearsal.