A forecast category is a label applied to an opportunity that indicates how confident you are it will close in the period. It sits alongside the sales stage and answers a different question: stage describes where a deal is in the process, category describes whether you’re counting on it.
What Are the Standard Forecast Categories?
Salesforce ships with five, and most teams use them roughly as intended.
- Pipeline holds early-stage deals that haven’t been qualified into anything countable.
- Best Case covers opportunities that could close with things breaking your way.
- Commit is what the rep is standing behind.
- Closed is won revenue.
- Omitted removes a deal from forecast rolls without deleting it, which matters for deals that are real but not this quarter.
Categories map to stages by default, so moving a deal forward changes its category automatically. That default is convenient and it’s also the source of most of the trouble with them, because it lets stage progression stand in for a judgment nobody actually made.
Why Separate Category From Stage?
Because a deal can be advanced and unlikely at the same time.
An opportunity in a late stage with a champion who has gone quiet and no economic buyer engaged belongs in Best Case regardless of how far it has traveled. If stage alone drives the forecast, that deal gets counted, and the miss arrives at the end of the quarter with no warning.
Separating the two also makes disagreement visible. A rep at Commit and a manager at Best Case on the same deal is a conversation worth having, and it can’t happen when both fields say the same thing by construction.
How Do Teams Get Forecast Categories Wrong?
Three ways, all common.
Categories drift upward and never down. Deals get promoted as they progress and nobody demotes them when momentum stops, so the Commit bucket inflates through the quarter. This is the same problem forecast accuracy exposes after the fact, visible in the categories weeks earlier.
Definitions go unwritten. Ask five reps what qualifies a deal for Commit and you’ll get five answers, which makes the aggregate meaningless. What Commit requires should be a documented test, not a feeling.
And nobody uses Omitted. Deals that have clearly slipped stay in the current period because moving them feels like an admission, so the category that exists precisely for honest slippage sits empty.
How Conquer Sharpens Forecast Category Calls
A category is a judgment about momentum, and momentum is visible in activity, not in stage.
That means the useful question during a pipeline review isn’t what stage a deal is in but what has actually happened on it recently.
With Conquer, calls and texts are placed from Salesforce and logged against the opportunity as they occur, alongside the dispositions that record what came of them, so a manager reviewing categories can see whether a Commit deal has a live conversation behind it or just a stage.
Try defending your Commit list from activity data alone. Whatever survives is your real forecast.