Best Case Amount
A Best Case Amount is the value shown in the Best Case column of Salesforce Collaborative Forecasts.
Definition
A Best Case Amount is the value shown in the Best Case column of Salesforce Collaborative Forecasts. It sums the Amount of open Opportunities whose Stage maps to the Best Case forecast category for a given period and owner, then rolls that total up the forecast hierarchy and applies any adjustments. Sales reps and managers read it as the deals they believe are more likely than not to close, even when they are not yet willing to commit to them.
Best Case sits between Pipeline and Commit on the Forecasts tab. Pipeline holds everything still open, Commit holds the conservative number the rep will stand behind, and Best Case holds the reasonable upside in between. The same value is exposed on the read-only ForecastingItem object, so it also appears in reports and dashboards. Which Stages feed Best Case is controlled by the Stage-to-Forecast-Category mapping that admins set in Setup, which makes the field only as trustworthy as that mapping.
How Best Case Amount is built and read
Stage drives the forecast category
Every Opportunity Stage maps to exactly one forecast category: Pipeline, Best Case, Commit, Omitted, or Closed. The mapping lives in Setup under Opportunity Stages, and it is the single rule that decides whether a deal contributes to Best Case Amount. When the Stage of an Opportunity changes, both its Probability and its forecast category change with it, so a deal can move into or out of Best Case the moment a rep advances it. A common mapping puts mid-funnel Stages such as Proposal and Negotiation into Best Case, leaves early Stages like Discovery in Pipeline, and reserves Commit for late Stages the rep is confident about. There is no separate Best Case checkbox on the Opportunity. The category is derived entirely from the Stage value and its configured mapping. This is why the column is only as meaningful as the mapping behind it. If too many Stages are mapped to Best Case, the number swells and loses its signal. If the mapping is tight and deliberate, Best Case Amount becomes a reliable read on credible upside for the period.
Single-category versus cumulative rollups
Salesforce offers two rollup methods, and they change what Best Case Amount actually contains. With single-category rollups, the Best Case column sums only the Opportunities whose category is Best Case. Nothing else is folded in. With cumulative rollups, the Best Case column includes Best Case Opportunities plus everything in the more confident categories beneath it: Commit and Closed (and Most Likely, where used). The cumulative view answers a different question. It shows the full total a rep is likely to bring in if their Best Case deals land, without anyone having to add categories together by hand. The choice is set once for the org in Setup, and it matters because the same column label can mean two very different sums. A leader comparing Best Case to quota needs to know which method is active. A cumulative Best Case will always be larger than a single-category Best Case for the same pipeline, because it absorbs the categories below it. Confirm the method before reading the number or building a dashboard on top of it.
Rolling up the forecast hierarchy
Best Case Amount aggregates through the forecast hierarchy, not just for one person. A rep sees the Best Case total from their own Opportunities. Their manager sees that rep, every other rep on the team, and the manager's own deals if they carry any. The default forecast hierarchy follows the role hierarchy, so each manager rolls up the people who report to them through roles. Sales operations can also build a custom forecast hierarchy when the reporting lines for forecasting differ from the org chart. The roll-up is what makes the Forecasts tab useful to leadership. A VP can open a single quarter and see the Best Case number for the whole org, then drill down team by team to find where the upside is concentrated. Because the hierarchy controls visibility, a misconfigured forecast role or a missing forecast manager can quietly hide a rep's deals from their leader's Best Case total, which is one of the more confusing problems to diagnose after a reorganization.
Adjustments layered on the raw total
The calculated Best Case roll-up is a starting point, not the final word. Reps and managers with the right permission can adjust Best Case Amount up or down to reflect judgment the raw data does not capture yet. A manager might raise a rep's Best Case because a verbal commitment came in that is not in the system, or trim it because a flagged deal looks shaky. Salesforce keeps the adjustment separate from the underlying amount and shows the delta inline, so you can always see both the raw roll-up and the adjusted figure. Manager adjustments and owner adjustments are tracked distinctly, which is why the ForecastingItem object exposes several amount fields rather than one. Adjustments are powerful, but they need a policy. When leadership overrides a rep's Best Case without explaining it, the rep stops trusting the forecast they are supposed to own. Agreeing on when and how adjustments happen keeps the number credible to everyone who reads it.
Best Case versus Commit and the upside band
Best Case and Commit answer two different questions about the same pipeline. Commit is what the rep is willing to put their name on, the number they expect to deliver. Best Case is what they think is genuinely achievable if the more uncertain deals break their way. By definition Best Case is greater than or equal to Commit, because a deal the rep will commit to is also one they consider achievable. The gap between the two is the upside band, and sales operations watches it closely. A narrow, persistent gap suggests reps are forecasting conservatively and may be sandbagging. A very wide gap suggests Best Case is padded with deals that are not really likely. Reading the two columns together tells a leader more than either one alone. A healthy forecast shows Commit tracking toward quota with a believable Best Case sitting above it, giving the team a clear sense of both the floor and the realistic ceiling for the period.
Periods, dates, and the revenue field
Best Case Amount is always scoped to a forecast period such as a month, quarter, or year, and the Opportunity Close Date decides which period a deal lands in. An Opportunity with a Close Date in the third quarter contributes to that quarter's Best Case if its Stage maps to Best Case. Rolling multi-period views simply sum the per-period values. The amount being summed is the Opportunity revenue field configured for the forecast type, usually the standard Amount. Some orgs forecast on Expected Revenue or a custom currency field instead, and the Best Case column reflects whichever field the forecast type uses. This is a frequent source of confusion. If the org closes its books on one field but forecasts on another, Best Case Amount will not reconcile to the numbers finance reports. Aligning the forecast revenue field with the field the business actually closes on keeps Best Case meaningful when leadership compares it to bookings and quota at the end of the period.
Where the value surfaces beyond the tab
The Forecasts tab is the primary home for Best Case Amount, but the value travels further. The ForecastingItem standard object stores forecast amounts per user, period, and category, and it is read-only because the platform calculates the numbers from Opportunities and adjustments. Reporting on ForecastingItem lets teams build dashboards like Best Case versus Quota, Best Case trend by quarter, and Best Case minus Commit for upside analysis. CRM Analytics exposes the same metric in its pipeline and forecasting apps for richer visualization and trending over time. Einstein and the broader Revenue Intelligence tooling can assess whether a rep's Best Case is realistic by comparing it to how similar deals closed before, surfacing forecasts that look too optimistic. None of these surfaces replace the Forecasts tab. They read from the same underlying data so that a rep, a manager, and an analyst are all looking at one consistent Best Case number rather than three competing versions of it.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Best Case Amount.
Hands-on resources to go deeper on Best Case Amount.
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 the Best Case Amount column show in Collaborative Forecasts?
Q2. What configuration determines whether an Opportunity contributes to Best Case Amount?
Q3. How does Best Case Amount behave across the forecast hierarchy?
Discussion
Loading discussion…