Review and evidence

A route review has a specific source revision, reviewer, decision time and reason. Review decisions keeps that record against the load. An operation receipt can record an action attempt with its key, expected revision, result state and time. Together, they help the team understand what was decided, what was attempted and whether the attempt completed, failed or needs review.

• Independent decision. Transport Supervisor examines the current route candidate and records Approve, Reject or Return with a reason.
• Durable outcome. A receipt distinguishes Pending, Completed, Failed and Needs Review attempts.
• Supporting material. record attachments stores a titled file or evidence reference with uploader, upload time, evidence type and visibility.

The Operations Overview page includes pending review decisions and failed operations. Route Review Queue draws attention to Submitted proposals. Operation Outcomes brings failed and needs-review receipts into a focused list. These screens help the team find work; the underlying decision, receipt and attachment hold the actual context.

Decide which changes require a fresh route review. A change to stops, equipment choice or estimated route after review can make an earlier decision stale. Agree how reviewers confirm the current revision and how they handle a returned proposal. Set evidence visibility rules for Internal and Shared attachments. Keep operation keys stable for attempts that should be treated as the same action, and decide who investigates a failed receipt before another dispatch attempt.

App Administrator maintains membership and scope. Transport Supervisor should not review their own route preparation as an independent decision. Auditor needs a reliable read path to the decision and its reason, but not edit authority. Before release, rehearse each role against a real load and check that the intended separation holds.

A Dispatcher submits a proposal for a load. Transport Supervisor sees that a stop window changed since the earlier revision and returns it with a reason. The Dispatcher submits a revised candidate; the supervisor approves that source revision. If a guarded operation later fails, its receipt records the expected revision and failure reason. The next operator can inspect the decision and receipt before retrying. An attachment with a delivery document can stay with the same load for the final review.

• Operation Outcomes — Failed and needs-review actions with reasons and expected revisions.
• Route Review Queue — Submitted route candidates that need a supervisor decision.
• Review Decisions — Decision history with reviewer, source revision and reason.

See route review and exception reconciliation.