Run a win-loss review that changes one forecast input
A bounded operating guide to win-loss review, with the evidence, decision rights, and close condition the revenue team can review.

Name the decision and the queue owner
Record the requester and the promised response time. If the team cannot reproduce the result from the record, the control is not finished. Do not let a deadline expand a role beyond its written limit. The win-loss review record should let a second reviewer rebuild the decision from the buyer debrief notes and the loss reason code. In the go-to-market strategy review, the win-loss review note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.
Give the case a stable identifier before any document is attached. A short written rule is easier to test than an unwritten habit. Say which system of record governs if two sources disagree. The win-loss review case note should show what the CRM held at the time and who reviewed it. The win-loss review 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
A clean-looking status is not evidence that the underlying work is correct. Use the same definition across the queue and the review so the counts agree. Do not let a deadline expand a role beyond its written limit. The win-loss review case note should show what the CRM held at the time and who reviewed it. The win-loss review record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.
Use the same case key in the queue and in the evidence extract. If the team cannot reproduce the result from the record, the control is not finished. Use the same definition across the queue and the review so the counts agree. In the win-loss review queue, an item without a next action is treated as an exception. At the weekly revenue review, the win-loss review figure is re-read and every change is dated in the same working file.
Set the authority boundary
Record rejected and deferred requests as well as approvals. A role change should trigger a review of queue access. Preparation, comparison, and follow-up may sit with the assistant. In the win-loss review queue, an item without a next action is treated as an exception. At the weekly revenue review, the win-loss review figure is re-read and every change is dated in the same working file.
A delegation needs a scope, a limit, an end date, and a named backup. Record rejected and deferred requests as well as approvals. Preparation, comparison, and follow-up may sit with the assistant. The win-loss review reviewer records the forecast input change, the owner, and the next action in one place. In the go-to-market strategy review, the win-loss review note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.
Run the daily handoff
The next reviewer should not have to ask which document is authoritative. Record one next action and one due time per open item. The record should show the source, the decision, and the surviving value in one place. The win-loss review reviewer records the forecast input change, the owner, and the next action in one place. In the go-to-market strategy review, the win-loss review note is compared with the approved revenue plan and signed off by the named owner before the quarter closes.
A handoff is complete only when the receiver acknowledges it. Log the handoff time when a case crosses a shift. Escalate an item that has waited past the written threshold. A sample win-loss review review checks the closed-lost record, the buyer debrief notes, and the surviving value in the CRM. The win-loss review 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
Do not close a case just because the requester stopped asking. A clean-looking status is not evidence that the underlying work is correct. Route one bounded question to the owner instead of negotiating in the queue. A sample win-loss review review checks the closed-lost record, the buyer debrief notes, and the surviving value in the CRM. The win-loss review record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.
Use the same definition across the queue and the review so the counts agree. Name the owner for every open item, including items waiting on someone else. A clean-looking status is not evidence that the underlying work is correct. For win-loss review, compare the closed-lost record with the destination value rather than relying on a status label. At the weekly revenue review, the win-loss review figure is re-read and every change is dated in the same working file.
Close with a verified destination value
Keep the prior value so the change can be explained. Test one closed case by rebuilding it from the evidence map. The next reviewer should not have to ask which document is authoritative. For win-loss review, compare the closed-lost record with the destination value rather than relying on a status label. At the weekly revenue review, the win-loss review figure is re-read and every change is dated in the same working file.
The record should show the source, the decision, and the surviving value in one place. If the team cannot reproduce the result from the record, the control is not finished. Record the close reason with the same codes used in the exception queue. For win-loss review, the working file keeps the closed-lost record and the buyer debrief notes beside the decision note. In the go-to-market strategy review, the win-loss review 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
Set the next review date before the action begins. 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. For win-loss review, the working file keeps the closed-lost record and the buyer debrief notes beside the decision note. In the go-to-market strategy review, the win-loss review 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. Keep the prior procedure available for comparison. A clean-looking status is not evidence that the underlying work is correct. A win-loss review exception keeps the forecast input change attached and routes the question to the sales leader. The win-loss review 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
Record event time separately from entry time. The record should show the source, the decision, and the surviving value in one place. Do not store credentials or unnecessary personal data in the case. A win-loss review exception keeps the forecast input change attached and routes the question to the sales leader. The win-loss review record stays in the revenue operations folder, where the sales leader confirms it against the CRM before the forecast commit.
Use the approved repository for sensitive content. The record should show the source, the decision, and the surviving value in one place. Label the version of every file that can change. Apply the same win-loss review test to the loss reason code and to the value that survives in the CRM. At the weekly revenue review, the win-loss review figure is re-read and every change is dated in the same working file.