Table 4From “What is AI demand forecasting? A forecast is a system, not an oracle”
What evidence should a sales forecast carry?
Table 4What evidence should a sales forecast carry?
| Evidence field | Review question | Why it stays visible |
|---|---|---|
| Target and unit | What outcome is forecast, and at which grain? | A revenue forecast is not an opportunity-count forecast |
| Population and exclusions | Which records or units enter the forecast? | A changed population can look like a changed model |
| Cutoff and horizon | What information was available, and when does the period close? | Hindsight and unlike windows do not enter silently |
| Baseline and intervention | What model or human change produced the final value? | A final number without its baseline cannot be audited |
| Later actual | Which reconciled observation evaluates the forecast? | An open status is not an outcome |
| Decision and disposition | What action followed, and who accepted the evidence? | Evaluation remains separate from execution |
Swipe or scroll horizontally if the table is wider than your screen.
Source: Table from this essay. Sources and interpretation are given in the article.

From the essay
Revenue operations & AI
What is AI demand forecasting? A forecast is a system, not an oracle
AI demand forecasting needs a target, horizon, information cutoff, override boundary, and later actual. Automation alone is not forecast governance.
Read the essayThis exhibit belongs to an essay: the numbers live here, the argument lives there.
Cite or embed
Related exhibits

Table 3Table
How should sales forecasting governance work?
What is AI demand forecasting? A forecast is a system, not an oracle

Table 2Table
What remains human when AI enters sales forecasting?
What is AI demand forecasting? A forecast is a system, not an oracle

Figure 1Figure
The AI forecast control map
What is AI demand forecasting? A forecast is a system, not an oracle
Contact
Bring the question you're working on.
Research, a guest lecture, or a commercial question.