The playbook
Sales Forecasting: Template and Field Guide
This sales forecasting template turns a broad task into a record another person can use. It captures opportunity, value, close period, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| opportunity | Record the opportunity associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| value | Record the value associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| close period | Record the close period associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| evidence | Record the evidence associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with opportunity. Use the same reference throughout the record so notes are not attached to the wrong item. Then define the forecast period and included opportunities. This establishes the information required before the worksheet becomes a request for action.
Next, review stage evidence close dates and historical conversion. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as treating every open deal's full value as expected revenue, rather than a broad instruction to “improve performance.”
Finally, compare forecasts with actual closed outcomes. Put use realistic assumptions and disclose uncertainty in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Treating every open deal's full value as expected revenue |
| Action | Use realistic assumptions and disclose uncertainty |
| First check | Define the forecast period and included opportunities |
| Follow-up check | Compare forecasts with actual closed outcomes |
| Outcome to define | forecast error by period |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If value changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep forecast error by period connected to the item so the team can later assess whether the action was useful.
Preserve the context of the last meaningful conversation. The next owner should know what was promised, what remains unresolved, and who is expected to act. A stage label alone rarely supplies enough information.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now