Review and evidence

Review Decisions record an approve, reject or return decision against a load revision. The reviewer, decision time, reason and operation key stay with the parent load. This lets the team tell which revision an independent Operations Reviewer examined. The Dispatcher approves the route during planning. If the route or assignment changes, the earlier decision remains part of the history rather than silently applying to a different scope.

Record Attachments give the load supporting files. Each attachment has a title, evidence type, upload time, uploader and Internal or Shared visibility. That lets the team place recipient proof, route evidence or correction support beside the load while controlling who should see it. A proof reference on a Load Stop points to the handoff; the attached file can carry the underlying document.

• Decide. Operations Reviewer reads the current load revision and records the decision and reason against that revision.
• Support. Load Owner and Dispatcher attach the files needed to explain a route change, exception or recipient handoff.
• Reconcile. Operation Receipts retain the operation key, action, expected revision and result state for effects that need verification.

A receipt can be Pending, Completed, Failed or needs review. A Completed result should follow a comparison with the linked effect references and expected revision. A failed result gives the team a reason to inspect what happened before any retry. This is especially important when a correction request repeats: the original operation key should lead back to its prior result.

Choose who can review a load revision and how independence from the preparer is maintained. Agree what a rejection or return means for the next revision, how reasons are written and how decisions are communicated to dispatch. Decide which evidence types the team uses and when visibility is Shared. The Admin should test access to attachments with actual team member accounts.

Define an operation key convention before importing external events or running repeated corrections. Keep a direct reference to the affected load and its current revision. When a receipt is Failed or needs review, decide who investigates and what linked effects establish completion. Reconciliation should inspect the local evidence before any further external action.

A Load Owner asks to replace a delivery stop after a route has been approved. The Dispatcher checks the load revision, the affected stop and any receipt showing an executed action. The Operations Reviewer reads the changed scope, records a Return or Reject decision with a reason if the evidence is incomplete, and later records an approval on the corrected revision if the change is acceptable.

The owner attaches the supporting instruction with appropriate visibility. The associated Operation Receipt retains its operation key and expected revision. If a repeated correction request arrives, the team can locate the prior receipt rather than making a second unexplained change. Where the receipt’s effect references do not match the linked records, it remains needs review for investigation.

• Draft load review — Draft loads whose revision and owner need a route decision.
• Decision history — Reviewer, reason and decision tied to each load revision.
• Receipts needing review — Pending, failed and discrepancy cases awaiting investigation.

See planning and route review and corrections and reconciliation.