Correction and compensation

Correct authorized scope while preserving the original action and any decision required to compensate executed work.

Step by step

Identify the requested correction Relationship Owner

Relationship Owner identifies the opportunity, the affected work and a clear reason. Check current membership and revision before requesting a change.
- Check reason, actor and revision
- Updates Opportunities, Team members
Classify the effect Sales Manager

The guarded action distinguishes unexecuted draft scope from work that has already taken effect. Sales Manager checks the receipt history when the result is uncertain.
- Distinguish unexecuted and executed scope
- Updates Operation receipts, Opportunities
Cancel unexecuted scope Relationship Owner

Relationship Owner uses the authorized cancellation path for eligible unexecuted work. Preserve the original records and action evidence so the reason remains available later.
- Preserve cancellation evidence
- Updates Opportunities, Operation receipts
Authorize compensation Sales Manager

For executed scope, an independent Sales Manager reviews the proposed compensating action and its reason. Reviewer approval is required before proceeding with that compensation.
- Approve compensating action
- Updates Review decisions, Operation receipts
ApprovalA person approves before the work moves on.
Await confirmation Sales Manager

Keep the compensating action Pending until downstream confirmation establishes its effect. Sales Manager checks the evidence and retains the original history alongside the correction.
- Retain Pending until confirmation
- Updates Operation receipts

And how to keep it from happening.

Cancellation used for executed work. Inspect the effect before choosing a correction path. Work that already took effect requires the compensation decision.
History removed to tidy the record. Keep the original action and explanation available to the Auditor, including evidence of an unsuccessful attempt.
Confirmation assumed. An external reference identifies something to inspect. It must be supported by confirmation of the intended downstream effect.

Start free, then use Proto to change fields, steps and approvals before your team goes live.