Review and evidence

Operation receipts preserve the key, action, expected revision, outcome and time for guarded changes. They can also retain an external reference, effect references and a failure reason. A pending, failed or review-needed receipt directs Independent Reviewer to the underlying order and local effects. The receipt is a trail of attempted work, not a reason to repeat an external action without checking what already happened.

Review decisions record the source revision, decision, reason, time and reviewer against the order. Attachments can keep supporting files with a title, type, visibility and uploader. These records make the approval and the source evidence available together when the team has to explain a correction or an uncertain operation.

• Exception queue. The Shift Operations page opens underlying records from failed operations.
• Decision history. Independent Reviewer checks the revision and records a reasoned outcome.
• Supporting evidence. Attachments and provider events give the reviewer concrete source material.

For example, an operation receipt may remain pending even though a provider callback arrived. Finance Lead compares the provider event identity with the order and expected revision. Independent Reviewer compares the local effects with the receipt’s referenced scope. Only matched effects can justify completion. A mismatch remains in review with the reason visible to the next shift.

Agree who may resolve pending and failed receipts and who independently approves changed operational scope. Set a convention for operation keys so repeated requests can be recognized. Decide which attachments are internal and which are shared. Keep provider credentials and external references under the team’s access policy, with Finance Lead responsible for payment evidence review.

Review the effect references the operation expects. They should point to actual order, line or payment outcomes rather than a narrative claim that the action probably succeeded. If a receipt has a failure reason, resolve that specific condition before closing it. The team should compare current revision and identity before any retry, especially when an external provider may already have acted.

Open a failed correction in Shift Operations and follow its underlying receipt. Check the order revision, line quantities, reviewer decision and payment event. Confirm whether the intended effect is absent, present or uncertain. Attach the evidence and update the receipt outcome only when the actual effect references match. If the payment provider has not supplied a definitive outcome, leave the case for reconciliation.

Try the same operation key again during rehearsal. The team should see the previous result and avoid creating another effect. Record who made the review decision and why, so a later shift can follow the same chain without relying on memory.

• Operation Exceptions — Open failed and review-needed effects with their reasons.
• Pending Operation Receipts — Examine operations waiting for a confirmed outcome.
• Review Decisions — Check the reviewer, source revision and decision reason.

Reconcile an exception explains the read-first investigation; correct or cancel explains the independent decision.