Set a mutual action plan for enterprise deals past stage three

A bounded operating guide to mutual action plan, with the evidence, decision rights, and close condition the revenue team can review.

Set a mutual action plan for enterprise deals past stage three

Name the decision and the queue owner

Give the case a stable identifier before any document is attached. Distinguish a new request from a correction to an earlier one. A clean-looking status is not evidence that the underlying work is correct. For mutual action plan, the working file keeps the deal record and the buyer milestone list beside the decision note. In the go-to-market strategy review, the mutual action plan note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.

The record should show the source, the decision, and the surviving value in one place. Say which system of record governs if two sources disagree. Record the queue and the entity so the case cannot drift into another team's work. A mutual action plan exception keeps the next review date attached and routes the question to the account executive. The mutual action plan record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.

Map the source and the evidence trail

Use the same case key in the queue and in the evidence extract. Use the same definition across the queue and the review so the counts agree. Record who supplied each document and when it arrived. A mutual action plan exception keeps the next review date attached and routes the question to the account executive. The mutual action plan record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.

Preserve a conflicting value instead of overwriting the first one. Do not let a deadline expand a role beyond its written limit. A case that moves between owners should keep both owner periods visible. Apply the same mutual action plan test to the signed action plan and to the value that survives in the CRM. At the weekly revenue review, the mutual action plan figure is re-read and every change is dated in the same working file.

Set the authority boundary

Do not let a deadline expand a role beyond its written limit. Name the backup owner and the coverage window in advance. Record rejected and deferred requests as well as approvals. Apply the same mutual action plan test to the signed action plan and to the value that survives in the CRM. At the weekly revenue review, the mutual action plan figure is re-read and every change is dated in the same working file.

Name the backup owner and the coverage window in advance. If two roles share a queue, mark which one decides each item. The next reviewer should not have to ask which document is authoritative. The mutual action plan close note cites the CRM, the approver, and the time of the final check. In the go-to-market strategy review, the mutual action plan note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.

Run the daily handoff

Assign every unowned case before new work begins. Escalate an item that has waited past the written threshold. Keep the queue view readable on one screen. The mutual action plan close note cites the CRM, the approver, and the time of the final check. In the go-to-market strategy review, the mutual action plan note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.

Use the same definition across the queue and the review so the counts agree. Open the day with a queue pass by age, owner, and missing evidence. Do not let a status update stand in for a verified event. Every mutual action plan handoff names the account executive and the field in the CRM that will confirm the change. The mutual action plan record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.

Handle exceptions without rewriting history

Keep the original request so a later correction does not erase the reason for the work. If the exception repeats, give it a reason code. Route one bounded question to the owner instead of negotiating in the queue. Every mutual action plan handoff names the account executive and the field in the CRM that will confirm the change. The mutual action plan record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.

When access blocks the work, name the system, role, and approver. Record who released the dependent action and when. Record the stop reason and the release decision together. In this mutual action plan case, the record points to the CRM and names the account executive as the decision owner. At the weekly revenue review, the mutual action plan figure is re-read and every change is dated in the same working file.

Close with a verified destination value

A case that moves between owners should keep both owner periods visible. A closed status is not proof that the destination changed. A clean-looking status is not evidence that the underlying work is correct. In this mutual action plan case, the record points to the CRM and names the account executive as the decision owner. At the weekly revenue review, the mutual action plan figure is re-read and every change is dated in the same working file.

The next reviewer should not have to ask which document is authoritative. A clean-looking status is not evidence that the underlying work is correct. If the destination is another team, require an acknowledgment. The mutual action plan record should let a second reviewer rebuild the decision from the buyer milestone list and the signed action plan. In the go-to-market strategy review, the mutual action plan note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.

Review the pattern, not only the case

Keep the original request so a later correction does not erase the reason for the work. Use the same definition across the queue and the review so the counts agree. A stable total can hide a growing tail. The mutual action plan record should let a second reviewer rebuild the decision from the buyer milestone list and the signed action plan. In the go-to-market strategy review, the mutual action plan note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.

A clean-looking status is not evidence that the underlying work is correct. The next reviewer should not have to ask which document is authoritative. Use the same definition across the queue and the review so the counts agree. The mutual action plan case note should show what the CRM held at the time and who reviewed it. The mutual action plan record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.

Keep the record ready for the next reviewer

Avoid a private second version in a personal document. Use the same definition across the queue and the review so the counts agree. A case that moves between owners should keep both owner periods visible. The mutual action plan case note should show what the CRM held at the time and who reviewed it. The mutual action plan record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.

A case that moves between owners should keep both owner periods visible. Avoid a private second version in a personal document. Keep the source reference and the coded value in the same row. In the mutual action plan queue, an item without a next action is treated as an exception. At the weekly revenue review, the mutual action plan figure is re-read and every change is dated in the same working file.

Related GTM guides