The playbook
Sales Forecasting: Checklist
Use this sales forecasting checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect forecast error by period. Check an actual customer or opportunity record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
For each included deal, review the expected close period and the evidence behind its stage. Compare forecast assumptions with historical outcomes, while allowing for changes in deal mix. Keep committed revenue separate from weighted estimates and upside scenarios.
Before you use the checklist
Name the exact item being checked and its purpose. Gather opportunity, value, close period, evidence. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Define the forecast period and included opportunities | A dated observation showing how opportunity was verified | sales operations lead |
| Review stage evidence close dates and historical conversion | A dated observation showing how value was verified | record owner |
| Compare forecasts with actual closed outcomes | A dated observation showing how close period was verified | sales manager |
Check the failure path
- Look specifically for this failure: treating every open deal's full value as expected revenue.
- Use realistic assumptions and disclose uncertainty. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check evidence.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Define the forecast period and included opportunities,” a meeting about the subject is not the evidence itself. Retain the relevant opportunity and value, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents estimate future sales using documented opportunity evidence and assumptions deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow forecast error by period using a consistent definition so later reviews can connect execution quality with useful results.
Review a small sample of underlying records before trusting a summary. Duplicates, stale close dates, and missing outcomes can make a dashboard misleading even when the calculation is correct. Correct the record-level cause.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now