Forecast categories

Forecast categories are the labels a sales team uses to group open deals by how likely they are to close in the current period, most commonly pipeline, best case, commit and closed, plus omitted for deals left out. They let a manager add up a forecast without inspecting every deal.

Why it matters in B2B sales

A forecast is only as reliable as the category each deal sits in. The number a sales leader commits to is usually built from commit plus some share of best case, so one deal in the wrong category moves the forecast by its full value. When categories reflect rep optimism rather than buyer actions, the forecast misses late.

The sales pipeline shows what exists. Categories say what the team expects to land, and which deals a manager assumes are safe.

The standard forecast categories

Commit means the rep expects the deal to close this period and will be held to it. Best case means it can close this period, but a step is still unconfirmed. Pipeline means a qualified deal not expected this period. Omitted removes a deal from the forecast, usually because it is lost. Closed counts deals already won.

Salesforce's standard categories are Pipeline, Best Case, Commit, Closed and Omitted, with Most Likely as an extra option. HubSpot's manual categories follow the same pattern. RevOps usually owns the definitions.

Forecast category vs deal stage

A deal stage says where the deal is in your sales process. A forecast category says whether you expect it to close this period. Salesforce maps each stage to a category by default and lets reps override it. A deal in negotiation can still be best case if the buyer has no reason to sign before next quarter.

Define each category by buyer evidence, not by stage. Commit might require a confirmed compelling event, an agreed signature date and a known procurement path.

A concrete example

A sales director at an IT services firm reviews the quarter. One AE has three deals in commit but a confirmed signature date on only one. The other two have no procurement contact, so the director moves them to best case. The forecast drops and now matches what buyers have agreed to.

How it shows up in day-to-day selling

Categories usually change in the forecast call, from memory. Accurate categories depend on CRM hygiene, the work reps skip first. Cobl reads the calls, emails and CRM history on each deal and shows what is proven, what is missing and what puts it at risk. Before each pipeline review it lists the gaps to fix.

A commit that rests on a rep's confidence is a number nobody can defend.

Frequently asked questions

How do you change a forecast category in Salesforce?

Edit the Forecast Category field on the opportunity, if your admin has made it editable. By default the category follows the stage, so changing the stage changes it too. An admin changes the default mapping by editing the values of the Opportunity Stage picklist.

Who decides a deal's forecast category?

The rep proposes it and the manager confirms it in the forecast review. The rep owns the CRM field, but the manager answers for the number. Clear entry rules for each category give both sides the same test to apply.

How many forecast categories should a team use?

Most teams use four or five: pipeline, best case, commit, closed and omitted. More categories rarely improve accuracy, because each needs its own definition and reps apply them inconsistently. A few strict categories usually forecast better than many loose ones.