Correcting scope begins with the original opportunity and its operation evidence. Relationship Owner must explain the requested change, while Sales Manager determines the allowed compensation for an executed effect. Deleting the earlier record would remove the basis for that decision.
Relationship Owner identifies the opportunity, current revision and correction reason. The configured action validates the supplied actor against live team membership and requires an operation key before proceeding.
Relationship Owner and Sales Manager inspect operation receipts and the linked activity, files and decisions. Classify the scope according to what genuinely occurred, including any external acknowledgment still being investigated.
Relationship Owner records the permitted cancellation of scope that has not executed. Retain the opportunity and its earlier evidence. Keep the stopping reason with the action evidence, preserving the earlier outcome and any effect that still needs confirmation.
An eligible independent Sales Manager reviews the requested compensating action against the executed revision and records the decision. Approval permits the correction action; the downstream correction still needs verified confirmation.
Relationship Owner retains the compensating receipt as Pending until downstream evidence is received. A timeout requires investigation before retry; the operation key prevents the same request from producing another effect.
Sales Manager verifies the declared revision and effect references. Auditor follows the original action, reason, independent decision and confirmed outcome through the retained records.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.