The definition
Forecast categories are labels a deal owner puts on each open deal to state how it should count in this period's forecast. The standard set has three working values. Commit means I promise this closes in the period, plan on it. Best case means it can close if things break right, do not plan on it. Pipeline means it is real but not landing this period. Some enterprise schemes add omitted for deals excluded from the period entirely.
The crucial property: a category is a judgement, not a calculation. Stage probability is statistics about deals like this one. A category is a statement about this exact deal, made by the person who knows it. The two answer different questions, and a good forecast, as laid out in the forecasting guide, reads them side by side.
Why it matters
Work an example. A team has €400,000 of open deals with close dates this quarter. The weighted pipeline says €175,000. Now the owners categorise: €120,000 sits in commit, €130,000 in best case, the rest is pipeline that will slip. Leadership can now plan on €120,000, coach toward the best case list, and stop counting the rest. The weighted number alone could not separate the promise from the hope, because a 60 percent stage contains both.
The second payoff is accountability with memory. Commit accuracy is measurable: of the deals in commit at the start of the quarter, how many actually closed? A rep who commits €100,000 and lands €55,000 is not unlucky twice in a row, they are miscalibrated, and the number makes the coaching conversation concrete. Weighted value cannot do this, because nobody personally promised it.
How to set it up in Pipedrive
One custom field does the work: a single-option field on the deal, named Forecast category, with the values Commit, Best case and Pipeline. Do not make it required at creation, because a fresh deal has no business being categorised yet. Instead, make it expected in the stages where close dates land inside the current quarter, and walk it in the weekly forecast call. The field rules from custom fields apply: this field earns its place only if a report reads it and a meeting acts on it.
Reporting is one Insights view: open deal value with a close date in the period, summed by forecast category. Put it next to the weighted pipeline number on the team dashboard, and add a small quarterly report on commit accuracy per owner. Pipedrive's own forecast view by expected close month remains useful as the time axis. The category field adds the judgement axis on top.
Where teams get it wrong
The first failure is duplicating stages. If commit simply means negotiation stage, the field is dead weight, and reps treat it as admin. The category must be allowed to disagree with the stage, that disagreement is its entire information content. The second failure is category inflation under pressure: quarter end approaches, a manager needs the number, and best case quietly becomes commit. One inflated quarter destroys the calibration you were building, and the field takes a year to regain meaning.
Third, categories without consequences. If the forecast call never revisits what was committed and what landed, the labels drift into decoration. Keep the loop closed: commit, close the quarter, compare, discuss. And keep the scheme small. Three values that everyone defines identically outperform a five value taxonomy with boundary debates every Monday.