Commit Amount
A Commit Amount is the value in Salesforce Collaborative Forecasts that represents deals a sales rep is confident will close in the period.
Definition
A Commit Amount is the value in Salesforce Collaborative Forecasts that represents deals a sales rep is confident will close in the period. It rolls up the Amount of every Opportunity whose Forecast Category is Commit, summed across the rep's own deals and the deals of anyone reporting to them in the forecast hierarchy. Reps treat Commit as the number they are willing to put their name on, which is why leadership reads it as the floor of the quarter's expected close.
The figure sits between two other totals. Closed is revenue already booked, and Best Case is the more optimistic total of deals that are likely but not certain. Commit is calculated by mapping each Opportunity Stage to a Forecast Category, then summing the Amount of every open and won deal that lands in Commit. Reps and forecast managers can override the calculated number through a forecast adjustment, and the column shows both the raw roll-up and the adjusted value.
How the Commit Amount is built and read
Where the Commit number comes from
Salesforce does not store Commit Amount as a field you type into. It is a calculated roll-up. Every open Opportunity carries a Forecast Category value, and that value is driven by the deal's Stage through a mapping an admin defines in Setup. When a Stage maps to Commit, the Amount of every Opportunity sitting in that Stage flows into the Commit total for its owner and period. Won deals also count, because a closed deal is a committed deal that already landed. The calculation runs per forecast period and per forecast user. A rep's Commit reflects only their own pipeline at the bottom of the hierarchy. The total is gross, meaning it sums the full Amount of each qualifying Opportunity rather than a probability-weighted figure. That is a deliberate design choice. Collaborative Forecasts asks reps to express confidence by choosing which category a deal belongs in, not by trusting a percentage. The result is a number that reflects human judgment about which deals are genuinely committed, layered on top of the underlying Opportunity data.
Cumulative rollup changes what Commit contains
The Commit column can mean two different things depending on the rollup method your admin selected. With individual category rollups, the Commit column shows only Opportunities whose Forecast Category is exactly Commit. Closed deals appear in their own separate Closed column. This is the literal reading of the category. With cumulative rollups, the Commit Forecast column includes committed Opportunities plus any closed Opportunities. The idea is to give forecast users a running total they are likely to bring in, without making them add columns by hand. Under this method, Best Case Forecast goes further and includes Best Case plus Commit plus Closed, and Open Pipeline includes Pipeline plus Best Case plus Commit. Knowing which method is active matters, because the same word Commit can describe a category-only sum or a Commit-plus-Closed running total. Sales operations teams should document which rollup their org uses so nobody misreads the column during a forecast call.
Stage to Forecast Category mapping
The mapping between Opportunity Stage and Forecast Category is the lever that controls what counts as Commit. Salesforce ships default categories of Pipeline, Best Case, Commit, Omitted, and Closed, and each standard Stage points at one of them out of the box. Late-stage values such as Negotiation or a verbal-agreement Stage commonly map to Commit, while early Stages map to Pipeline and won Stages map to Closed. This mapping is not set in stone. An admin edits it through Opportunity Stage picklist values in Setup, choosing the Forecast Category each Stage feeds. A loose mapping that pushes mid-funnel Stages into Commit inflates the number and misleads leadership. A tight mapping that reserves Commit for genuinely late deals keeps the column honest. Mature sales operations teams audit this mapping every quarter, because a single mis-mapped Stage can move millions through the Commit total. The mapping also affects Best Case and Pipeline, so any change should be reviewed against the whole funnel, not just the Commit column.
Adjustments override the calculated value
The raw roll-up is rarely the final word. Forecast adjustments let a rep or a manager change the Commit Amount to reflect knowledge the data does not capture. A rep might raise their Commit because a deal is verbally agreed but still in an earlier Stage. A manager might lower a rep's Commit because they doubt a deal will close on time. An adjustment changes the forecast value only. It never edits the underlying Opportunity record, so the deal's Stage and Amount stay exactly as the rep entered them. Salesforce keeps both numbers visible. You can see the original calculated amount and the adjusted amount side by side, with the difference shown inline, so the override is transparent rather than hidden. Who can adjust depends on the forecast hierarchy. Forecast managers can adjust the numbers of users below them, and owners can adjust their own. Disciplined teams require a short justification for every adjustment, because undocumented overrides quietly erode trust in the forecast over a few quarters.
Rolling up the forecast hierarchy
Commit Amount is not a single figure. It exists at every level of the forecast hierarchy. The hierarchy is a nested list of forecast users that decides how totals add up and who can view and adjust whose numbers. It is generated from the role hierarchy by default, and a designated forecast manager sits at each level overseeing the level below. At the bottom, an individual rep sees the Commit rolled up from their own Opportunities. Their manager sees that rep's Commit, plus every other rep on the team, plus any deals the manager owns directly. Move up another level and the regional leader sees the sum of all teams beneath them. This stacking is what lets a VP read one Commit number for an entire org while a rep reads one number for their personal pipeline. Because adjustments can be applied at any level, a manager's published Commit can differ from the simple sum of their reps' Commits. That gap is intentional and reflects the manager's own read on the quarter.
Reporting and watching Commit through the quarter
Commit Amount surfaces beyond the Forecasts tab. The Forecasting Items report type exposes it alongside Quota, Best Case, Closed, and Pipeline, so teams can build dashboards that track the number over time. Common views include Commit against Quota, the trend of Commit across the weeks of a quarter, and the gap between Commit and Closed. That last view is one of the most useful signals a sales operations team has. The difference between Commit and Closed represents deals the rep still expects to close but has not yet won. Watching it shrink week over week shows the quarter converting on plan. Watching it stay flat late in the period flags deals that are stuck. CRM Analytics dashboards can present the same metric with richer slicing, and Einstein-driven forecasting features can flag whether a given Commit looks realistic against how that rep has closed in the past. The reporting turns a static column into an early-warning system for the quarter.
Common ways Commit goes wrong
Three problems recur often enough to name. The first is a loose Stage-to-Forecast-Category mapping. When mid-funnel Stages feed Commit, the number balloons and leadership plans around revenue that was never truly committed. The fix is a quarterly mapping audit that keeps Commit reserved for genuinely late deals. The second is undisciplined adjustments. When reps and managers override Commit without recording why, the forecast becomes a set of opinions nobody can reconstruct later. Requiring a one-line justification on each adjustment keeps the data auditable and builds a culture where the number means something. The third is inconsistent rep behavior. Some reps sandbag and commit far below what they close, while others commit everything in sight. Both distort the roll-up that leadership reads. The remedy is a post-quarter review of each rep's Commit accuracy. Reps who miss in a predictable direction get coached to calibrate, so next quarter's Commit carries real information instead of personality.
Configure what feeds the Commit Amount
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.
Prefer this walkthrough as its own page? How to Commit Amount in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Rollup Methods for Pipeline ForecastsSalesforce
- Customize Pipeline Forecast CategoriesSalesforce
Straight from the source - Salesforce's reference material on Commit Amount.
Hands-on resources to go deeper on Commit 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 Commit Amount represent on the Collaborative Forecasts tab?
Q2. How does Commit Amount relate to Best Case in a Salesforce forecast?
Q3. Which coaching metric tracks the reliability of a rep's Commit Amount?
Discussion
Loading discussion…