You do not create a Commit Amount directly. You configure the Stage-to-Forecast-Category mapping that decides which Opportunities feed the Commit column, and you pick the rollup method that controls what the column totals. Both live in Setup and both require Collaborative Forecasts to be enabled.
- Enable and configure forecasts
In Setup, go to Forecasts Settings and enable Collaborative Forecasts. Turn on the forecast types you need, such as Opportunity Revenue, so the Commit column has data to roll up.
- Choose a rollup method
Still in Forecasts Settings, select your rollup method. Individual category rollups make Commit show only Commit-category deals. Cumulative rollups make the Commit Forecast column include Commit plus Closed.
- Map stages to the Commit category
Open Opportunity Stage picklist values in Setup. For each Stage, set the Forecast Category. Point only genuinely late Stages at Commit so the number stays a trustworthy floor.
- Set up the forecast hierarchy
Confirm the forecast hierarchy reflects your reporting lines and assign a forecast manager at each level. This determines how each user's Commit rolls up and who can adjust it.
Individual category rollups isolate Commit; cumulative rollups fold Closed into the Commit Forecast total. Choose one and document it so the column is read correctly.
The picklist value on each Opportunity Stage that decides whether its Amount lands in Pipeline, Best Case, Commit, Omitted, or Closed.
Whether forecast managers and owners can override the calculated Commit, set through forecast settings and the hierarchy.
- Cumulative and individual rollups make the Commit column mean different things; never compare numbers across orgs without checking which method each uses.
- Editing a Stage-to-Forecast-Category mapping reshapes Best Case and Pipeline too, so review the whole funnel before you change what feeds Commit.
- Adjustments change only the forecast value, not the Opportunity record, so the deal's Stage and Amount stay put even when the published Commit moves.