Pipeline, Best Case, Commit: Forecast Categories Explained

When you create or edit an opportunity, you set its Forecast Category to reflect your current confidence in closing it, and this value determines which column the opportunity appears in on the forecast grid (Microsoft).

Different platforms document these categories with specific confidence wording. For instance, one documentation source defines the categories as follows: Pipeline includes deals that have a low likelihood of closing; Best case includes deals that will close in the best case scenario, which have a moderate likelihood of closing; and Commit includes deals that have a high likelihood of closing and have been committed to the forecast (HubSpot). These definitions highlight that the category is fundamentally about probability assessment, not just stage progression.

Editorial recommendation: Use the specific confidence wording from your vendor’s documentation when defining your internal policy. This ensures that all team members interpret the category labels consistently and that the forecast number is built on a shared understanding of what each label implies about deal probability.

Vendor documentation defines forecast categories using distinct confidence language and probability bands. These definitions are product-specific and do not create a universal standard across platforms. When explaining a forecast number, you must cite the specific vendor documentation that governs your tenant configuration.

The documentation advises reviewing Committed deals first to identify stalled items and working with sellers to move top Best Case deals into Committed (Microsoft). Microsoft defines the Committed category as revenue from opportunities with high confidence (Microsoft). The Best Case category is defined as revenue from opportunities with medium confidence (Microsoft). The Pipeline category is defined as revenue from early-stage opportunities (Microsoft).

Oracle provides specific numerical probability bands for its forecast generation. Between 0% and 39% is accumulated in the Unforecasted / Pipeline category (Oracle). Between 40% and 59% is accumulated in the Best Case category (Oracle). Between 60% and 99% is accumulated in the Committed category (Oracle). Won opportunities have 100%-win probability and are added to the Won category (Oracle).

These differences mean that a deal labeled "Best Case" in one system may not meet the criteria for "Best Case" in another. You must record which vendor’s definitions apply to your specific forecast number to avoid miscommunication during review meetings. Do not assume that a label overrides the actual tenant configuration or that categories are identical across vendors.

In "Set up the forecast tool," you can toggle the "Automate forecast categories" switch on to automatically update forecast categories when a deal moves to a different deal stage (HubSpot). This specific automation behavior is documented for that source; do not assume every product behaves this way. Similarly, "Optimize Salesforce Sales Forecasting Setup" states that there is a default mapping defined in the Opportunity object’s Stage field (Salesforce). The same source explains that each opportunity stage aligns to a forecast category, which indicates an opportunity’s likelihood to close (Salesforce).

These automated rules handle the baseline assignment. A deal might sit in a stage that maps to "Best Case," but a manager may manually adjust it to "Commit" based on specific account signals. This manual override is a judgment call, not a system rule. The system provides the default structure; the human provides the confidence adjustment.

When configuring your tenant, note the constraints on available categories. In "Set up the forecast tool," in addition to "Not forecasted" and "Closed won," only five additional categories will appear in your forecast category mapping (HubSpot). Specifically, only the last five property values will appear as categories that you can map to in your forecast settings (HubSpot). This limit means you cannot map every possible stage to a unique category if your stage list is long. You must prioritize which stages receive distinct category mappings.

Editorial recommendation: Define the threshold for manual override. For example, deals above a certain amount might require manual review regardless of stage. Deals in specific industries might require different category assignments. Document these rules. This ensures that manual judgments are applied consistently, not arbitrarily. Consistency in judgment is as important as consistency in automation.

The amount basis determines whether a forecast number reflects the full deal value or a probability-adjusted figure. In the "Set up the forecast tool" documentation, the weighted amount is defined as the Amount multiplied by the Deal probability (HubSpot). Your policy worksheet should explicitly record whether your organization uses the weighted amount or the total amount for each forecast category. Using the wrong basis distorts the comparison between pipeline and commit numbers because one figure is scaled by confidence while the other is not.

The forecast period defines the time window for the forecast. In the "Set up the forecast tool" documentation, if you edit the forecast period, the forecastable revenue goals and forecast submission will be reset for all pipelines, and you will need to create new revenue goals and forecast submissions (HubSpot). This behavior means that changing the period is a significant policy event that clears existing data. Your worksheet must include a change reason field to document why the period was altered, as the reset action prevents simple tracking of previous submissions.

Ensure the amount basis matches the formula used in your reporting tool. If you use weighted amounts, document the probability source. If you use total amounts, note that the figure does not reflect deal confidence. The period scope must match the reporting cycle required by leadership.

Prevent double counting by treating forecast categories as sets of opportunities. In "Optimize Salesforce Sales Forecasting Setup," single forecast category rollups include opportunities in the given category only (Salesforce). Similarly, in "Configure columns and layouts in forecast grid | Microsoft Learn," if Best Case is selected, only opportunities with the forecast category set to Best Case will be aggregated (Microsoft). This means a single-category column must not be added to another column that already contains those same opportunities.

In "Optimize Salesforce Sales Forecasting Setup," the Best Case category includes all the best case opportunities, plus the opportunities in the Most Likely, Commit, and Closed categories (Salesforce). In "Configure columns and layouts in forecast grid | Microsoft Learn," a documented formula for the best case forecast is Closed + Commit + Best Case (Microsoft). Another documented formula for total forecast is Committed + Best Case + Pipeline (Microsoft). Your worksheet must follow the exact labels configured in your tenant. Do not assume these labels are identical across vendors or that a label overrides the actual tenant configuration.

When adjusting numbers, apply the change to only one level. In "Configure columns and layouts in forecast grid | Microsoft Learn," you can either adjust the rollup value or the calculated value that it contributes to, but not both (Microsoft). Record any manual adjustment in the policy worksheet with the reason for the change and the owner who made it.

How do I verify that a cumulative rollup does not double count?

Check that the cumulative formula explicitly lists the categories it includes. In "Configure columns and layouts in forecast grid | Microsoft Learn," the formula Closed + Commit + Best Case defines the set membership (Microsoft). If your tenant uses different labels, such as Committed, update the formula accordingly. In "Optimize Salesforce Sales Forecasting Setup," the Best Case category includes Most Likely, Commit, and Closed categories (Salesforce). Compare your tenant’s configuration against these documented examples to ensure no category is excluded or duplicated.

What should I do if a category is missing from the cumulative formula?

Check your tenant configuration to see if the category is included. In "Optimize Salesforce Sales Forecasting Setup," the Best Case category includes Most Likely, Commit, and Closed categories (Salesforce). In "Configure columns and layouts in forecast grid | Microsoft Learn," the total forecast formula is Committed + Best Case + Pipeline (Microsoft). If a category is missing, verify whether it is intentionally excluded or if the formula needs updating. Document any discrepancies in your policy worksheet.

Use the blank worksheet below to document your forecast-category policy. It is an editorial recommendation for maintaining a consistent record of how your team defines and manages forecast numbers.

The following table assigns specific policy fields to each forecast category. You must fill in these fields based on your internal standards and the specific configuration of your sales tool. The columns are designed to capture the label, the proof needed to include a deal, the basis for the amount, the time period, the responsible owner, and the reason for any changes.

When defining your categories, consider how different platforms handle deals that are not part of the forecast. For example, in the "Set up the forecast tool" documentation, "Not forecasted" is defined as deals that are in the pipeline for the current time period, but are not included in the forecast (HubSpot). This distinction is critical for your policy because it clarifies that a deal can exist in the current period without contributing to the forecast number. Similarly, "Closed won" is defined as deals that have closed within the forecasted time period (HubSpot). Your policy should specify whether closed deals are tracked separately or if they roll into a cumulative view.

The core task is defining which deals enter your number and how they aggregate. A forecast category acts as a filter for confidence and stage, not a guarantee of revenue. You must verify whether your system uses a single-category rollup or a cumulative total, as this setting determines how the final number is calculated. According to Salesforce documentation, you can set up Salesforce to roll up totals to a single category, or to collectively total the numbers across categories (Salesforce).

Definitions vary by platform, so do not assume labels are identical. Your policy must map these specific definitions to your internal stages and record the evidence required for each entry.

How do I know which rollup method is active?

Check your tenant configuration to see if it is set for a single category or cumulative totals. The method is a system setting, not a manual choice made during the forecast meeting. If you are unsure, review the setup options in your forecasting module to confirm whether the system sums all categories or selects one. This distinction is critical because it changes how the final number is derived from the underlying deal data.

Why does my total not match the sum of columns?

Verify the fields used for aggregation and check for adjustments on both rollup and calculated values. Ensure that the amount basis (such as weighted amount) is consistent across all categories before comparing the sum of columns to the final total.

What happens when I change the forecast period?

Document that revenue goals and submissions may be reset, requiring new entries. Changing the period can invalidate previous forecasts, so you must re-evaluate which deals fall into the new timeframe. Update your policy to reflect the new period boundaries and ensure all owners re-confirm their deal status against the updated timeline. This step prevents stale data from contaminating the new forecast number.