Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryBBest Case Amount
SalesIntermediate

Best Case Amount

Best Case Amount is the Collaborative Forecasts column that shows the forecast value rolled up from Opportunities in the Best Case forecast category, summed across the user's pipeline and any reports rolling up beneath them.

§ 01

Definition

Best Case Amount is the Collaborative Forecasts column that shows the forecast value rolled up from Opportunities in the Best Case forecast category, summed across the user's pipeline and any reports rolling up beneath them. Where Commit shows the conservative number the rep is willing to bet on and Pipeline shows everything still open, Best Case captures the deals the rep believes are more likely than not to close even though they cannot commit. The column is one of the central readings on the Forecasts tab and is the field sales leadership watches alongside Commit and Closed when assessing whether the quarter is on track or in danger.

Best Case Amount is calculated by mapping each open Opportunity's Stage to its Forecast Category, summing the Amount of every Opportunity whose Forecast Category is Best Case for the relevant period and ownership, then applying any forecast adjustments. The Best Case column on the Forecasts tab and the matching ForecastingItem record both expose the value. Stage-to-Forecast-Category mappings are controlled in Setup; admins configure which Stages roll up to Pipeline, Best Case, Commit, and Closed. Most production forecast designs use Best Case to mean reasonably likely to close, leaving more aggressive forecasts in Pipeline and more conservative ones in Commit.

§ 02

How Best Case Amount is calculated and used in forecasting

Stage to Forecast Category mapping

Opportunity Stages map to one Forecast Category each: Pipeline, Best Case, Commit, Closed (or Omitted). Setup, Opportunity Stages controls the mapping. A typical mapping puts Negotiation and Proposal in Best Case, with Discovery in Pipeline and Closed Won in Closed. The mapping is what drives every forecast category column, including Best Case Amount.

How the column rolls up the hierarchy

Best Case Amount aggregates across the Forecast Hierarchy. A rep sees their own Best Case. Their manager sees the rep's Best Case plus the manager's own (if they have direct Opportunities) plus the Best Case from every other rep on their team. The Forecast Hierarchy walks the role hierarchy by default and supports custom Forecast Hierarchy configurations for sales operations.

Forecast Adjustments and Best Case

Sales reps and managers can adjust Best Case Amount manually. The adjustment overrides the calculated roll-up with a human judgement number. Salesforce surfaces the adjustment-amount delta inline so managers know whether they are looking at the raw roll-up or the adjusted forecast. Most production forecasts include some adjustment to reflect deals the data does not yet capture.

Period and date filters

Best Case Amount is calculated per forecast period (Month, Quarter, Year) using the Opportunity Close Date as the inclusion filter. An Opportunity with a Close Date in Q3 contributes to Q3 Best Case if its Stage maps to Best Case. Multi-period forecast views (rolling four quarters, etc.) sum the per-period values.

Best Case versus Commit

Best Case is what the rep believes is more likely than not. Commit is what the rep is willing to put their name on. Best Case is always >= Commit by definition. The delta between Best Case and Commit is the upside band sales operations watches as a confidence signal.

Reporting and dashboards

Beyond the Forecasts tab, the ForecastingItem standard object exposes Best Case Amount in custom reports. Common dashboards include Best Case versus Quota, Best Case Trend by Quarter, and Best Case minus Commit for upside analysis. The objects shipping with Collaborative Forecasts (ForecastingItem, ForecastingAdjustment) make these reports straightforward.

Common configuration pitfalls

Three patterns recur. Loose Stage-to-Forecast-Category mappings (e.g. all open Stages mapped to Best Case) make Best Case Amount meaningless. Adjustments not visible to upstream managers create surprise. And forecasting on Amount when the org actually closes on a different field (Expected Revenue, Custom Revenue) produces forecasts that do not match the books.

Best Case in CRM Analytics and Einstein

CRM Analytics dashboards expose Best Case Amount as a standard pipeline metric. Einstein Forecasting can predict whether the rep's Best Case is realistic based on prior closure patterns. Both surfaces complement the standard Forecasts tab without replacing it.

§ 03

How to make Best Case Amount accurate

Best Case Amount is a calculated field; the work is configuring Stage mappings, adjustment workflows, and reporting so reps and managers can trust the column.

  1. Audit Stage-to-Forecast-Category mappings

    Setup, Opportunity Stages. Confirm each Stage maps to the right category. Loose mappings (everything in Best Case) make the column useless; tight mappings give reps a clear model.

  2. Configure Forecast Hierarchy

    Setup, Forecasts Hierarchy. Confirm the rollup reflects how sales leadership wants to see numbers. Default role-hierarchy rollups are fine for many orgs but enterprise sales operations often customise.

  3. Train reps on Best Case versus Commit

    Explain the difference: Best Case is more likely than not; Commit is willing to put your name on. Without training, reps muddle the categories and the forecast loses signal.

  4. Build a Best Case Trend dashboard

    Report on ForecastingItem grouped by period and forecast category. Show Best Case alongside Commit and Closed for the full picture.

  5. Set forecast adjustment policy

    Decide which roles can adjust Best Case and when. Adjustments that come from sales leadership without warning the rep undermine trust in the forecast.

Gotchas
  • Loose Stage-to-Forecast-Category mappings make Best Case Amount meaningless. Tight, intentional mappings are what give the column signal.
  • Adjustments invisible to upstream managers create surprise. Adjustments should follow a visible workflow.
  • Forecasting on Amount when the org closes on Expected Revenue or a custom field produces forecasts that do not match the books. Pick the right Revenue field at the Forecast Type level.
  • Reps who do not understand the difference between Best Case and Commit make the categories noise. Training matters.
§

Trust & references

Sources

Cross-checked against the following references.

Official documentation

Straight from the source - Salesforce's reference material on Best Case Amount.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.

About the Author

Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.

§

Test your knowledge

Q1. What does Best Case Amount represent?

Q2. How does Best Case Amount relate to forecast hierarchy?

Q3. What is a useful way to use Best Case Amount for coaching?

§

Discussion

Loading…

Loading discussion…