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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.