Scope correction

A request to withdraw a manufacturing proposal may arrive before any handoff, or after an external system has already acted. Those cases need different treatment. The correction workflow resolves the opportunity, checks the actor against live team membership and requires a reason, current revision and operation key. It then distinguishes unexecuted draft scope from scope whose effects have already occurred.

Unexecuted scope can be canceled without deleting its record or supporting evidence. Executed scope needs a reviewer-approved compensating action, with the receipt remaining Pending until the downstream confirmation arrives. Keep the stopping reason and effect references with the action evidence. Preserve the earlier deal outcome while explaining what scope was withdrawn and which effects still need confirmation.

• Read the prior scope. Relationship Owner identifies the relevant linked opportunity, current revision and earlier operation evidence. Preserve the activity and attachment context used by the original decision.
• Choose the correction path. Establish whether the requested effect was executed. An eligible independent Sales Manager reviews compensation for executed scope; administrative access does not replace that business decision.
• Verify the result. The operation receipt carries the expected revision, result state and supporting references. A Pending result remains visible until confirmation establishes that the intended correction actually occurred.

Agree what evidence establishes that a handoff has been executed and which connected system owns the effect being corrected. Define how the correction reason, original receipt and compensating receipt refer to each other through the available evidence fields. Agree any downstream cancellation with the relevant system owner and retain the acknowledgment that explains the actual result.

Configure the action to reject a stale revision, missing reason and unauthorized actor. Decide how a changed request is submitted for a fresh decision while preserving review decisions for earlier revisions. A Return decision asks for revised preparation; it does not itself cancel an external action. Rehearse the action under the Relationship Owner and Sales Manager identities used in ordinary work.

A customer withdraws its request after engineering approved the submitted drawing. Relationship Owner first reads the prior receipts. If the agreed external handoff has not occurred, the correction records the withdrawal reason while retaining the inquiry and approval evidence. The owner should be able to explain why the scope stopped without rewriting the earlier engineering decision.

If the handoff has occurred, Sales Manager reviews the requested compensating action against the executed revision. A request to the downstream system remains Pending until its acknowledgment is verified. During rehearsal, repeat that request with the same operation key and simulate a timeout after the external action. The app must avoid another effect and keep the uncertain result visible for investigation. Auditor should be able to follow the original action, the correction reason and the final confirmation in sequence.

• Decisions returned for revision — Read the independent review reason and compare its revision with current scope; an earlier return may already have been addressed.
• Pending operation confirmations — Follow compensation whose actual downstream outcome still needs evidence.
• Failed operations — Investigate a recorded failure before deciding whether a retry is appropriate.

Scope correction and compensation explains the separate paths. Reconciliation to verified completion checks the outcome. Agree external ownership in integrations.