Forecast definition record
Before you start
- Your entries stay on your own copy; nothing is sent anywhere.
- Copy dates from your sales tool as they appear there.
- Write “not known” for anything you cannot find, never zero.
- The record holds words only, no sums.
In this order
- Forecast call first
- Name each category
- Record definition changes
- Keep open questions
What to settle for each category
- Commit
- Which stage and proof a deal needs before it counts, and who may move it in or out.
- Best case
- What a deal still lacks to be commit, and the last close date that still counts for this period.
- Pipeline
- Which open deals count at all: stage, a close date inside the period and a named owner role.
- Omitted
- Which deals stay out of the number this time, and why.
| Call date date | |
|---|---|
| Reporting period your wording | |
| Snapshot timestamp the date, then the clock time | |
| Amount basis your wording | |
| Currency label your wording |
| Category label your wording | |
|---|---|
| Inclusion rule one plain sentence | |
| Exclusion rule one plain sentence | |
| Definition source where your team keeps it |
| Category label your wording | |
|---|---|
| Inclusion rule one plain sentence | |
| Exclusion rule one plain sentence | |
| Definition source where your team keeps it |
| Category label your wording | |
|---|---|
| Inclusion rule one plain sentence | |
| Exclusion rule one plain sentence | |
| Definition source where your team keeps it |
| Previous definition where your team keeps it | |
|---|---|
| Changed definition where your team keeps it | |
| Open question one plain sentence | |
| Owner a role, not a person’s name | |
| Next action one next step | |
| Review date date |
Not on this record: weighted pipeline, probability inputs and forecast sums. Write “not known” in any box you cannot fill.