Operations review

Operations Overview brings pending review decisions, failed operations and open-order exceptions into a shared scope. Review decisions and operation receipts retain the detail behind those summaries. A decision identifies the reviewer, reason, source revision and operation key. A receipt identifies the action, expected revision, result state, external reference and failure reason where applicable.

• Review the decision. Order Reviewer checks the current order and routing context before approving, rejecting or returning it.
• Inspect the result. Admin or Order Coordinator follows Pending, Failed and needs review receipts.
• Keep supporting files. Attach evidence to the order with Internal or Shared visibility.

A completed receipt records an operation outcome; it does not replace the reviewer’s decision or a provider or fulfillment event. A returned review decision is still part of the order’s decision history. Attachments retain title, evidence type, upload date and uploader so the team can find the file relevant to the exception.

The reviewer can follow a submitted route back to the customer order, while the coordinator can follow a receipt back to the action under investigation. Neither record should be replaced merely because a later attempt succeeds.

Choose who can decide supplier routing and who can investigate receipt failures. Agree when an attachment is Shared and who may see it. Define a retry practice that checks the operation key and expected revision before a second attempt. Keep a named owner for an exception so failed results do not disappear in a broad dashboard count.

Submit a route for a confirmed order. The Order Reviewer approves the current revision and records a reason. An operation receipt then reports a needs-review result with an external reference. Admin checks the action, key and expected revision, while the Supplier Coordinator checks whether an acknowledgement already exists. The team resolves the receipt before trying another action. The original decision and receipt remain available for the next reviewer.

Rehearse a second case where the reviewer returns the route. The coordinator revises it and resubmits. The first reason stays attached to the original decision, and the new decision references the correct source revision. Add an Internal attachment and confirm that its visibility is respected by the appropriate role.

• Failed operation receipts — Failed and review-needed actions with the reason and order.
• Routing review inbox — Submitted routes waiting for a decision.
• Decisions by reviewer — Each reviewer’s recorded decisions and reasons.

Review routing decisions and investigate exceptions.