Pipeline Design
Part of CRM sales pipelines
Distinguishing a forecast category from a pipeline stage
Understand what a pipeline stage, forecast category and probability each mean, and how to review a deal when the values disagree.
A pipeline stage records a deal’s progress in the sales process; a forecast category governs how that deal is treated in a forecast. They can be related, but they answer different management questions. Keep both current when one stage contains deals with different levels of commitment.
Ask which question the value answers
“Proposal presented” can be a stage because it names an event. “Commit” or “Committed” is a forecast category in some CRMs because it expresses a forecast judgement. The team should be able to explain each value without using the other as its definition.
| Value | Question it answers | Evidence to review |
|---|---|---|
| Pipeline stage | What has happened in the sales process? | Customer response or completed milestone |
| Forecast category | How should this deal contribute to the forecast? | Current commitment, remaining uncertainty and the period being reviewed |
| Probability | What percentage is assigned to a deal or stage? | The CRM’s configured rule or a deal-specific assessment |
Probability is another value, not a substitute for either decision. A weighted deal value may use it, while a forecast category may determine a separate forecast column. Check the CRM’s configuration before treating two figures as equivalent.
Pipeline Stage vs Forecast Category: Key Differences
- Pipeline stage
- What has happened in the sales process?
- Forecast category
- How should this deal contribute to the forecast?
- Probability
- What percentage is assigned to a deal or stage?
See why the same stage can have different categories
Picture two deals at “proposal presented”. One customer is still comparing options; the other intends to proceed, subject to final approval. The stage may be correct for both because the proposal has been presented, but their forecast categories may differ because the remaining uncertainty differs.
The reverse can happen too. Two deals at different stages may be placed in the same broad forecast category when the team judges them similarly for the period.
Keep a written rule for the category, including what evidence changes the judgement and who can approve an exception. A category should not become a reward for a salesperson or a way to repair a weak stage definition.
Know what the CRM does automatically
Many CRMs allow stage-to-category mappings, and some allow a manual override where configured. A reviewer should inspect the opportunity’s actual forecast category rather than infer it solely from the stage.
Dynamics 365 Sales documents a Forecast Category field on the opportunity that determines which column receives its revenue on the forecast grid. Its guidance distinguishes Pipeline, Best case, Committed and Omitted, and says Won or Lost should be set by closing the opportunity rather than selecting those categories manually. Access may depend on having the necessary licence or authorisation.
Some CRMs separate forecast category from deal probability, automate category changes, or alter automation after a manual probability change. Check the CRM’s configuration and the value a particular report uses.
CRM Forecast Categories (Common Examples)
- Pipeline
- In progress – not yet committed
- Best case
- High likelihood of closing, but not confirmed
- Committed
- Strong intent to proceed; low uncertainty
- Omitted
- Not included in forecast due to high risk or delay beyond period
Review a disagreement without hiding it
When stage and category appear inconsistent, ask three questions: Is the stage supported by an observable event? What has changed in the customer’s commitment or timing? Did an automatic mapping or a manual override set the category? Correct the value that misstates the deal and record the reason for an exception.
Consider the forecast period as well as the deal’s evidence. If a deal slips beyond the period, reassess its forecast treatment without pretending the proposal was never presented.
