Sales Forecast Categories: Commit, Best Case, Pipeline Defined

Here is a scenario that plays out at the end of every quarter. A head of sales submits a $480k commit to the CEO on a Monday. The quarter closes on Friday. Actuals: $290k.

The $190k gap is not a math error. Nobody made anything up. Twelve deals sat in the Commit column of the forecast. Seven of them closed. Five did not. The five that missed were not surprises to the reps who owned them. They were optimism dressed up as certainty.

This is the forecast categories problem. The categories exist in every major CRM. The entry criteria for what earns each one almost never do.

What Forecast Categories Are (and Why They Are Not the Same as Deal Stages)

Before anything else, the distinction matters.

A deal stage describes where a deal sits in your sales process. Prospecting, Discovery, Proposal Sent, Negotiation, Closed Won. It is a description of buyer-verified progress through your pipeline. Stages are about the deal itself.

A forecast category describes how confident you are that the deal closes inside the current forecast period. It is a forward-looking judgment about timing and probability, not a description of where the deal stands. Categories are about whether and when money comes in.

Both HubSpot and Salesforce maintain these as separate fields precisely because the same stage can produce different levels of forecast confidence. A deal in Negotiation with a signed legal review and executive sponsor might be a Commit. A deal in the same stage but waiting on a Q1 budget release is Best Case at most. The stage is identical. The forecast confidence is not.

That separation is useful only if teams apply it consistently. Most do not, because nobody ever defined what consistency looks like.

The Five Standard Categories

HubSpot and Salesforce both use five core categories, with minor label differences.

Pipeline

Early-stage opportunities that are in the forecast window but carry low close probability. The buyer is engaged, needs exist, and the deal is real, but there are too many open questions to call it anything stronger. For most B2B teams, Pipeline means the deal could close this quarter if things accelerate, but the default assumption is it does not.

Entry criteria to keep it honest: the buyer has agreed to a next step, there is at least one confirmed point of contact, and the deal has been created within the last 45 days without going dark. A deal that has not had a buyer-initiated touchpoint in three weeks probably does not belong in Pipeline; it belongs in Omitted or archived.

Best Case

Deals that will close this period if the remaining conditions resolve favorably. There are genuine positive signals: a champion is engaged, the prospect has reviewed terms or pricing, and internal evaluation is underway. But a contingency remains. Budget approval is pending. Legal review has not started. A second decision-maker has not signed off.

Best Case is not a consolation Commit. It is a real category for real deals that have momentum but carry a specific identifiable risk. If your team uses Best Case as a holding bin for everything that is not Pipeline and not Commit, the category is doing no work.

Entry criteria: the economic buyer has been identified and engaged (at least one conversation), the prospect has taken at least one forward commitment (reviewed pricing, scheduled a follow-up with a specified date, or shared internal stakeholders), and the rep can name the specific condition that separates this deal from Commit.

Commit

The rep is calling this deal as closed within the forecast period. Commit means the rep is prepared to be held accountable if it does not close. For this category to carry any information value, the evidence bar must be high enough that calling a Commit feels like a real stake in the ground.

The standard entry bar for Commit: the economic buyer has verbally agreed to move forward, a specific close date within the current period has been confirmed by the buyer (not assumed by the rep), the deal amount is agreed or within a narrow negotiating range, and no open technical, legal, or budget blocker remains that could prevent close this period.

Note what is not on that list: "the rep feels good about it," "the prospect seemed interested on the last call," or "we have been talking for six months." Relationship tenure and rep intuition are not evidence. Buyer commitments are.

Closed Won

The deal has closed. Revenue is recognized. No ambiguity.

Omitted (or Not Forecasted in HubSpot)

Deals deliberately excluded from the forecast rollup. This is the correct home for dormant deals, deals pushed past the forecast window, or deals under active qualification where including them would inflate the pipeline number without adding information. Omitted is not a garbage bin; it is a deliberate exclusion.

Why Forecast Categories Break Down in Practice

The categories themselves are not the problem. Every CRM has them. The problem is that nobody writes down the entry criteria, and so the same label ends up meaning something different to every rep on the team.

Without a written standard, Commit means "I feel confident" to one rep and "the contract is out for signature" to another. When both deals sit in the Commit column of the rollup, the manager cannot distinguish between them. The forecast looks the same. The outcome will not be.

There is a second failure mode: automatic stage-to-category mapping applied without adjustment. If every Negotiation stage deal auto-maps to Commit, then the category reflects the stage, not the deal's actual close probability. You lose the analytical separation that makes the two fields valuable.

The fix is not sophisticated. It is a one-page document that defines the evidence bar for each category, reviewed with every rep on hire and referenced on every pipeline call. The document should answer: what must the buyer have done, not what the rep believes, for a deal to earn this label?

How to Set Up Forecast Categories in HubSpot and Salesforce

HubSpot

HubSpot's forecast tool is available in Sales Hub Professional and Enterprise. To configure it:

1. Go to Settings, then Forecast.
2. In the Forecast Submission settings, map each deal stage to a forecast category (Not Forecasted, Pipeline, Best Case, Commit, or Closed Won).
3. Toggle Automate forecast categories on if you want HubSpot to update the category field automatically when a deal moves to a new stage. This creates a workflow named "Forecast Category Mapping for Pipeline: [pipeline name]" in your workflows tool.
4. If you want reps to be able to override the auto-assigned category on specific deals, keep automation on but train reps to adjust the Forecast Category deal field directly. The manual override takes precedence.

The automation is useful for basic setups but has a critical limitation: it maps stage to category uniformly, which is exactly the failure mode described above. A deal in Negotiation auto-gets Commit regardless of whether the buyer has confirmed a close date. Consider leaving automation off and training reps to set the category field manually, using your written entry criteria as the standard.

Salesforce

Salesforce includes forecast categories as a default field on the Opportunity object. The five defaults are Pipeline, Best Case, Commit, Closed, and Omitted. Stages can be mapped to categories in the Sales Process settings, and reps can also adjust the category field on individual opportunities.

The Forecast page in Salesforce aggregates opportunities by category, lets managers adjust rep submissions upward or downward with an override, and tracks the adjustment delta over time. That override capability is where a manager can correct the gap between rep optimism and evidence-based confidence without having to edit individual deals.

To customize the category list, go to Setup, then Opportunities, then Fields, find the Forecast Category field, and edit the picklist values. Many teams add a Most Likely category between Best Case and Commit to give reps a landing zone for high-confidence deals that do not quite meet the Commit evidence bar.

The Data Layer That Makes This Work

Forecast categories are only as reliable as the CRM data underneath them. A rep who is committed to being accurate about categories still cannot calibrate correctly if the close date field has not been updated since the deal was created, if there is no logged activity to reference, or if the deal amount has drifted without being updated.

The specific fields that matter for category judgment are: close date (current and buyer-confirmed), deal amount (agreed or at least scoped), last buyer activity date, and the specific open blockers or next steps documented in the deal record. Without those fields current, the rep is guessing. The forecast category reflects that guess.

This is where pipeline visibility matters more than most teams realize. If your CRM is not capturing activity automatically, and your deal fields are not being kept current between calls, then every category judgment happens on stale data. The rep submits a Commit based on where they think the deal is, not where it demonstrably is.

Accurate sales forecast accuracy starts here: before you refine the category definitions, make sure the data underneath them reflects what actually happened in each deal. A well-trained rep applying the right entry criteria to bad deal data still produces a broken forecast.

Related: Sales Pipeline Stage Definitions: The Exit-Criteria Method covers how to define stages with the same rigor applied to categories here. The two posts work as a pair. Stages define where the deal is; categories define how confident you are it closes this period.

One Category Check That Surfaces Most Problems

Once a week, before the forecast call, pull a report of every deal in Commit. For each one, ask two questions: Has the buyer confirmed the close date? Is there a specific open blocker that would prevent close this period?

A Commit deal with no buyer-confirmed close date is a Best Case. A Commit deal with an open blocker that cannot resolve before period end is also Best Case or Pipeline. Move them. Do not wait for the call.

This single check, applied consistently, will compress the gap between your submitted Commit and your actual close number faster than any change to your forecasting methodology. The categories are already in your CRM. The entry criteria and the weekly check are what make them mean something.

Frequently Asked Questions

What are the standard sales forecast categories?

Most CRMs including HubSpot and Salesforce use five categories: Pipeline (early-stage, low confidence), Best Case (could close this period if everything goes right), Commit (high confidence, rep is calling it), Closed (won), and Omitted or Not Forecasted (excluded from the rollup). The specific labels vary slightly between platforms.

What is the difference between a deal stage and a forecast category?

A deal stage describes where a deal sits in your sales process: Discovery, Proposal, Negotiation. A forecast category describes how confident you are that deal closes inside the current period. The same stage can map to different categories depending on deal-specific context, which is exactly why the two fields exist separately in HubSpot and Salesforce.

How do I set up forecast categories in HubSpot?

Go to Settings, then Forecast, and map each deal stage to a forecast category. Toggle on Automate forecast categories to create a workflow that updates the category whenever a deal moves to a new stage. For teams that want manual override capability, leave automation off and train reps to set the category field directly on each deal.

Why does Commit mean something different to every rep?

Because most teams never write down the entry criteria. If Commit means verbal agreement to one rep and signed contract to another, the rollup is meaningless. Fixing this requires a written evidence bar: what the buyer must have done, not what the rep believes, before a deal earns the Commit label.

What should Commit accuracy look like for a B2B sales team?

A well-calibrated Commit call should close at 85% or higher within the forecast period. If your team submits $400k in Commit and closes $240k, the Commit label is being applied to deals that belong in Best Case. The gap tells you the entry bar is too loose, not that forecasting is inherently hard.