Forecast Categories Explained: Commit, Best Case, Pipeline

Forecast categories are labels your CRM uses to sort open deals by how confident a rep is that each one will close in a given period. The five standard labels (used by Salesforce and mirrored by most other CRMs) are Pipeline, Best Case, Commit, Closed, and Omitted. They’re related to the deal’s sales stage, but they aren’t the same thing.

If you’ve ever opened a forecast report and seen a deal sitting in “Qualification” stage but tagged as “Commit,” you’ve probably wondered what’s going on. That’s not necessarily a bug. Stage and forecast category measure two different things, and mixing them up is one of the most common reasons forecasts go sideways.

This post breaks down what each category means, how they roll up into a number leadership actually trusts, and how to set definitions your whole team can agree on.

What is a forecast category, exactly?

A forecast category is a classification tag attached to an opportunity that signals how likely the rep thinks it is to close within the current forecast period, usually a month or a quarter. Salesforce, which popularized this model, uses categories to group opportunities by confidence of closing. Most other CRMs, including HubSpot, use some version of the same idea, though the labels can differ slightly, so check your own naming.

Here’s the distinction that trips up most new reps and managers. A pipeline stage (like “Proposal Sent” or “Negotiation”) describes where a deal sits in your sales process. A forecast category describes how sure you are it will close on time.

The two are connected, though. In Salesforce, each stage maps to a default forecast category, and that mapping drives how opportunities roll up into a rep’s or manager’s forecast. Admins can also allow users to override the category on a deal. So a deal in a late stage can still be tagged Pipeline if the rep isn’t confident, and a deal in an early stage can be tagged Best Case if the rep has unusually strong conviction. The override is where judgment enters the forecast, which is also where most of the trouble starts.

Stage (example)	Default category (example)
Discovery	Pipeline
Qualification	Pipeline
Demo	Best Case
Proposal	Best Case
Negotiation	Commit
Closed Won	Closed
Closed Lost	Omitted

That mapping is an illustration, not a recommendation. Yours will differ. One useful check: make sure every active stage maps to a category, because an unmapped stage defaults to Pipeline, which can quietly understate late-stage deals.

What does each category mean?

Pipeline is the broadest, lowest-confidence category. These are opportunities that are actively being worked but haven’t earned a stronger label yet. They might close this period, next period, or not at all. In most CRM configurations, every new opportunity starts here by default. Think of it as the “still in progress, don’t bank on it yet” bucket. It’s useful for understanding total potential revenue, but it typically gets excluded from the number you’d present as a committed forecast.

Best Case sits one notch up. These are opportunities with real interest and a plausible path to closing this period, but still some risk. It’s also the category most prone to inflation, and that tracks with what most RevOps teams will tell you: it requires less evidence than Commit and feels better to report than Pipeline, so reps lean on it. Writing down what specifically disqualifies a deal from Commit keeps Best Case from becoming a dumping ground for hopeful deals.

Commit is the rep’s public promise. These are opportunities the rep is telling their manager, in effect, “this one is closing this period, you can count on it.” In cumulative rollups, the Commit total usually becomes the floor that leadership plans around, because it includes Commit plus anything already Closed. Commit is better understood as an accountability signal than a probability estimate, which is exactly why it needs the strictest bar of any category.

Closed covers deals already won in the period. There’s no projection involved. It’s the booked outcome. In the standard setup, Closed means Closed Won only.

Omitted covers opportunities excluded from the forecast. That’s typically where Closed Lost deals land, along with deals that are on hold, stalled, or pushed to a future period. Some Salesforce orgs also enable an optional “Most Likely” category between Commit and Best Case, so check whether yours does before you compare numbers across teams.

Define categories by evidence, not by percentage

Different reps calibrate confidence differently, so one rep’s 80% might be another’s 55%. Defining a category by required evidence makes the label mean the same thing no matter who fills it in. Here’s an illustrative starting point:

Category	Example evidence required	Example disqualifiers
Pipeline	Qualified need and an identified contact	None, this is the default
Best Case	Confirmed need, budget discussed, a proposed timeline, a next meeting booked	No buyer contact in the last two weeks; no identified approver
Commit	A mutual close plan, confirmed budget, known approvals and signers, and a dated next step	Dependency on an unconfirmed event; legal or procurement not yet engaged

Pro tip: don’t let a close date inside the quarter be the only reason a deal reaches Commit. The date is a hope. The evidence is what turns it into a commitment.

How do forecast categories roll up into a number?

Most CRMs let you view totals by category in two ways. A single rollup shows only the deals in each category. A cumulative rollup shows each category plus everything more certain than it. Here’s an illustrative example with made-up numbers:

Category	Single rollup	Cumulative rollup
Closed	$400K	$400K
Commit	$600K	$1.0M (Commit + Closed)
Best Case	$1.1M	$2.1M (Best Case + Commit + Closed)
Pipeline	$2.3M	Open pipeline: $4.0M (Pipeline + Best Case + Commit)

Leadership can compare a conservative scenario (Commit, cumulative) against an optimistic one (Best Case, cumulative). Definitions of “open pipeline” vary, with some setups excluding Closed and some including it, so check which version your report uses before you compare numbers across teams or periods. A cumulative total and a single-category total can look very different for the same pipeline.

Weighted pipeline is a related but different idea: instead of sorting deals into buckets, it multiplies each deal’s value by a probability to produce a blended number. Teams often use both, and it’s worth understanding how weighted pipeline works alongside forecast categories.

Check whether the labels are earning their meaning

A label is only useful if it predicts something. One simple measure compares your Day One Commit forecast with what actually closed by the end of the period. If you started the quarter with $1.0M in cumulative Commit and $900K closed, that’s a 10% miss. Track it every quarter, along with how often Commit deals closed and how often Best Case deals closed. Here’s an illustrative history:

Quarter	Commit deals that closed	Best Case deals that closed
Q1	85%	35%
Q2	71%	40%
Q3	64%	28%

A declining Commit close rate like the one above suggests the definition is loosening, not that reps got worse at selling. Tighten the evidence requirements before you coach individuals. Decide on a target close rate for each category and review the numbers in your forecast meeting.

Warning signs in your categories

• A Commit total that sits on a thin Best Case and shallow pipeline. A healthy-looking Commit with little behind it is a fragile forecast.
• Deals jumping from Pipeline straight to Commit. That’s worth a second look in review.
• A growing Omitted bucket. It can mean deals are slipping or qualification is breaking down.
• Pipeline padded with stale deals whose close dates keep sliding forward each month.
• Overrides nobody explains. If categories change without a note, the label stops carrying information.

Five questions for a Commit review

1. What has the buyer actually done in the last seven days?
2. Who signs, and have we spoken to them?
3. Is budget confirmed, and by whom?
4. What is the next step, and when is it scheduled?
5. What could still stop this deal from closing this period?

If a rep can’t answer three of these, the deal probably belongs in Best Case. These questions draw on the same logic as qualification frameworks like BANT and MEDDIC, and a poorly qualified deal will fool even the best category definitions.

A simple checklist for defining your own categories

1. Write a one-sentence definition for each category your team uses (Pipeline, Best Case, and Commit at minimum).
2. List the specific, observable evidence required to qualify for each one. Avoid relying on probability percentages alone.
3. List disqualifying conditions, especially for Best Case and Commit (stale buyer contact, no confirmed budget, dependency on an unconfirmed event).
4. Map every active stage to a default category, and decide whether reps may override it.
5. Decide whether your forecast rollup will be cumulative or single-category, and make sure everyone reading the report knows which.
6. Review quarterly how often Commit deals and Best Case deals actually closed. If the numbers are way off from what the labels imply, your definitions need tightening, not your reps.

If you’re still getting oriented on forecasting basics, our beginner’s guide to sales forecasting is a good place to start.

Summary

Forecast categories sort open deals by how confident a rep is that each will close in the current period. The five standard categories are Pipeline (early and uncertain), Best Case (real interest with some risk), Commit (the rep’s public promise), Closed (won deals), and Omitted (excluded, usually including lost deals). They differ from sales stage, which describes where a deal sits in the process, although in many CRMs each stage maps to a default category that reps may or may not be allowed to override.

Define each category by observable evidence rather than a probability, check whether your rollup is single or cumulative, and track how often Commit and Best Case deals actually close. When Commit close rates slip, tighten the definition before coaching individuals. Watch for deals jumping straight to Commit, a growing Omitted bucket, and unexplained overrides.

Frequently asked

Is a forecast category the same as a sales stage?+

No. Stage tracks where a deal sits in your sales process. Forecast category tracks how confident the rep is that it will close on time. They often correlate, since stages map to default categories, but they’re separate fields and shouldn’t be treated as interchangeable.

What are the five standard forecast categories?+

Pipeline, Best Case, Commit, Closed, and Omitted. These are the standard categories Salesforce ships with, and most other CRMs use a similar structure even if some of the naming differs.

Where do lost deals go?+

Typically into Omitted. Closed usually means Closed Won only, so lost deals are removed from the forecast by mapping Closed Lost to Omitted.

Can a deal skip categories, like jumping straight from Pipeline to Commit?+

Technically yes, if overrides are allowed. Whether that’s a good idea is a different question. A deal that jumps straight to Commit without passing through Best Case is usually worth a second look in your forecast review.

Why does Best Case get inflated so often?+

Because it requires less evidence than Commit but still feels more credible to report than plain Pipeline. Tight, written disqualification criteria are the best fix we’ve seen for this.

Do I need all five categories, or can I use fewer?+

Some teams run a functional forecast with just Pipeline, Best Case, Commit, and Omitted, treating Closed separately since it’s an outcome rather than a projection. What matters more than the count is that every rep and manager applies the same definition consistently.

Do forecast categories replace probability weighting?+

Not necessarily. Categories group deals by confidence, while weighted pipeline multiplies each deal’s value by a probability. Many teams use both, using categories for the call and weighting as a cross-check.

Who should own the category definitions?+

Usually sales leadership and RevOps together. Sales owns the judgment about what evidence is meaningful, and RevOps owns the configuration, the stage mapping, and the tracking that shows whether the labels are working.