Commit vs Best Case Pipeline

• Use Commit for: deals that meet your team's explicit commitment rule and have evidence for the forecast period.
• Use Best Case for: deals that could close in the period if identified remaining conditions resolve.
• Check the report before comparing totals: Salesforce's cumulative rollups combine categories, while single-category rollups keep them separate.✓ 3

What Commit and Best Case actually mean

The names describe forecast judgment, not a universal mathematical threshold. HubSpot's setup documentation calls Best case a moderate-likelihood deal that closes in a favorable scenario. It calls Commit a high-likelihood deal committed to the forecast. The documentation does not provide a single probability cutoff that every sales team should use. A practical category policy therefore has to say what evidence earns a promotion from Best Case to Commit in your business.✓ 5

Salesforce treats Best Case and Commit as distinct standard categories alongside Pipeline, Omitted, and Closed. It also supports an optional Most Likely category in Lightning Experience. A team using that additional middle category may have a different boundary between Best Case and Commit from a team using the standard set. Write down the local category names and their meaning before comparing reports from two organizations.✓ 2

A useful rule is to ask what still has to happen for the buyer to close in the selected period. If the answer is a specific unresolved approval, final stakeholder meeting, procurement step, or signature timing, record that condition in the deal review. This is an editorial operating rule, not a claim that a vendor imposes those checkpoints. If the condition remains uncertain, Best Case may communicate the uncertainty better than Commit. If it is resolved and the seller and manager accept the close date, Commit may be defensible. Neither label replaces a buyer-confirmed next step.

Why the same stage can produce different forecasts

A CRM stage is a workflow position; a forecast category is the judgment attached to that position. Salesforce says forecasts rely on the mapping between the Opportunity Stage and Forecast Category fields. In its sample mapping, Proposal/Price Quote is Best Case at 75%, while Negotiation/Review is Commit at 90%. Those percentages are Salesforce's example configuration, not benchmark thresholds for every pipeline. Salesforce also says changing an opportunity's stage changes its probability and forecast category.✓ 1

The mapping is a starting point rather than a substitute for inspection. Salesforce allows an opportunity owner to edit the Forecast Category field and override the default stage-to-category mapping. Two opportunities in the same stage can therefore carry different category judgments. When a category looks surprising, inspect the record's stage, category, owner, amount, close date, and most recent change before treating the forecast column as an explanation.✓ 1

HubSpot likewise lets an administrator organize deal stages into forecast categories with category dropdowns. Its setup page distinguishes the category mapping from the amount shown in a forecast: a weighted amount is the deal Amount multiplied by Deal probability. Check both the category and the chosen amount basis when reconciling a deal list with a forecast number. A Commit label alone does not tell you whether the displayed amount is full or weighted.✓ 5

For an internal policy, give sellers a short evidence checklist and an exception process. The checklist might ask whether the buyer has confirmed the intended timing, whether the commercial scope is stable, who can approve it, and what exact step remains. These are proposed review questions, not measured predictors of closing. The exception process should record why a manager retained a deal in Commit despite an open condition, or moved it back to Best Case after the condition changed.

The rollup trap in a Best Case forecast

Before comparing a Commit number with a Best Case number, identify the rollup method. Salesforce says a single-category rollup combines opportunities within each category into a separate forecast. A cumulative rollup combines multiple categories. Therefore, a column labeled Best Case Forecast can be a broader total than opportunities whose individual category is Best Case.✓ 3

Salesforce explains that cumulative columns include opportunities in the named category and subsequent categories in the sales pipeline. Read that way, a Best Case Forecast column includes Best Case, Commit, and Closed, while Commit Forecast includes Commit and Closed. Do not add those two cumulative columns together as if they were mutually exclusive deal sets. First decide whether the question is "Which deals are individually in Best Case?" or "What total could be recognized through the Best Case cumulative view?" The answer requires different columns or filters.✓ 3

A separate adjustment can create another difference. Salesforce says an adjustment adds a layer of detail without changing the underlying gross rollup, and forecast managers can adjust their own Commit and Best Case forecasts and those of direct subordinates within the documented hierarchy. During a review, separate category movement from an adjustment to the forecast total. The two represent different decisions.✓ 4

A deal-review rule that can survive a handoff

Start every review with the same time period and amount basis. Then show the opportunity's current stage and category, the last category change, the buyer action supporting the proposed close date, and the unresolved condition. Ask the seller to state the next observable event that would move the deal from Best Case to Commit. If nobody can name that event, the category boundary is too vague to guide a review.

Treat a category change as an auditable decision. Record who changed it, when, and why. A Salesforce owner override can intentionally depart from the stage default, so the reason matters. If the stage itself changes, Salesforce says probability and category also change, which makes it important to distinguish automatic mapping from an explicit forecast judgment.✓ 1

Keep the policy small enough to apply consistently. Define one Commit rule, one Best Case rule, and what happens when a deal misses either. Salesforce standard categories cannot be deleted or deactivated, although labels can be renamed for single-category rollups. Salesforce cautions against changing the API names of category picklist values. A renamed label should therefore come with an updated internal glossary and report review, not an assumption that everyone already uses it the same way.✓ 2

In HubSpot, category order also affects the Deal change history report. If administrators customize labels or rearrange categories, inspect the reporting effect before interpreting movement as improvement or deterioration. The point of the review is to preserve a readable sequence of judgments, not to force every opportunity upward each week.✓ 5

FAQ

How we researched this

We read Salesforce's category, stage-mapping, rollup, and forecasting-element documentation and HubSpot's forecast setup documentation on October 8, 2026. Each factual statement is tied to a saved page excerpt and a public source below. The proposed deal-review checklist is editorial guidance; it does not claim to be a tested accuracy method.