Review and evidence

A review decision connects an outcome to the run revision examined by a reviewer. It records an approve, reject or return decision, the decision time, reason and operation key. The Transport Supervisor can inspect review evidence while the Dispatcher prepares the operational record. When a run changes after review, the old decision still refers to its earlier revision.

Attachments keep a title, evidence type, upload time, visibility and uploader with the parent run. Internal and Shared visibility need clear operating rules. A photo or document should support a specific observation or decision rather than become an unlabelled collection. The Auditor can inspect authorized evidence and the reason behind the decision.

• Preparation. The Dispatcher links the file or observation to the correct run and identifies its evidence type.
• Review. The Supervisor checks the source revision and any recorded decision and reason.
• Outcome. The team inspects the operation receipt for a completed, failed, pending or needs-review result.

Operation receipts also carry the operation key, action, expected revision and occurrence time. Those details help the Supervisor distinguish a new request from a repeated attempt and check whether an external effect was recorded.

Agree which decisions need a second person, what evidence is required, and who can see a Shared attachment. Decide how a returned revision moves back to the Dispatcher and how a rejected case is resolved. For an external action, define the operation key and reference format so the result can be reconciled later. A failed or uncertain result should be investigated through its original receipt before anyone retries the action.

Keep review and execution as separate duties. The decision says what a person approved or rejected; the receipt says what happened when an operation was attempted. Neither substitutes for an actual pickup, boarding or delivery observation. The App Administrator configures access while the Auditor verifies that the history remains understandable.

The Dispatcher prepares a run revision and attaches an operator’s evidence marked Internal. The Supervisor sees a Return decision on that revision because the boarding count conflicts with the stop observation. A later corrected revision has its own Approve decision. The two records remain tied to the revisions they describe; the earlier decision does not approve the later version.

A later operation has a receipt marked needs review. The Supervisor compares the operation key, expected revision and effect references with the run and any external acknowledgement. The team checks the recorded outcome before another attempt. A receipt marked Completed should be explainable from the linked run and its evidence, rather than treated as a generic success banner.

• Review decisions — See who decided, when, why and against which revision.
• Receipts needing attention — Inspect failed and uncertain attempts before retrying.
• Run attachments — Find evidence by parent run, type, visibility and upload time.

Review an assignment and reconcile completion.