Corrections and reconciliation

An operation receipt records the action, expected revision, operation key and result against an opportunity. The receipt shows whether the action is pending, completed or failed, or needs review. The Sales Manager can inspect the linked effects and failure reason when the result needs explanation, then reconcile the receipt against the actual local evidence.

Corrections also depend on what has already happened. Unexecuted scope can be canceled without deleting its history. Executed scope needs a compensating action that the Sales Manager reviews and that remains pending until the downstream result is confirmed. This preserves the distinction between requesting a correction and verifying that its effects have been resolved.

• Recognize repeated actions. Use a stable operation key for the guarded request. A retry should refer to the same operation so the team can inspect the persisted result without repeating the underlying effect.
• Classify the correction. The Relationship Owner records the reason and current revision. Determine whether the scope has already executed before choosing the correction path, and retain the evidence that explains the original action.
• Reconcile the evidence. Compare the receipt’s expected revision and declared effect with the linked local result. Mark completion only when they match; keep a discrepancy visible for review when the evidence does not support completion.

Agree who investigates failed operations and how the Relationship Owner asks for a correction. Decide what downstream confirmation is required when a connected system carries out part of the work. Give the Sales Manager enough context to approve the compensating action and verify the eventual result.

Rehearse stable operation keys across repeated page actions and retries. The team should be able to distinguish an unfinished operation from a second request for genuinely new work. Define how the reviewer records a discrepancy so another authorized person can continue the investigation without reconstructing the entire conversation.

A Relationship Owner has completed an approved segment operation and then discovers that the requested scope needs correction. They submit the reason against the current revision. Because the scope already executed, the Sales Manager reviews the compensating action and keeps it pending until the required downstream confirmation is available.

Inspect the receipt before and after confirmation. The reconciled result should match the declared revision and effect, with the original evidence still available. Rehearse a retry using the same operation key and confirm it returns the persisted result without repeating the effect. Finally, introduce a mismatch between a receipt and its local evidence; the Sales Manager should see an item needing review with a useful discrepancy explanation.

• Operation Exceptions — Failed operations and receipts needing review, with action, expected revision and discrepancy details.
• Review Decision History — The reviewer responses that explain an authorized correction or other governed decision.

Rehearse correction and reconciliation after segment completion or a reviewed customer outcome.