Probability
Probability is a standard percentage field on the Salesforce Opportunity record that shows how likely a deal is to close.
Definition
Probability is a standard percentage field on the Salesforce Opportunity record that shows how likely a deal is to close. It runs from 0 to 100 percent and ships on every opportunity in Sales Cloud.
The value is usually set by the opportunity Stage. Each stage carries a default probability, so moving an opportunity from one stage to the next updates the number for you. A sales rep can still type a different value when a specific deal does not behave like the average deal at that stage.
How probability shapes the opportunity and the forecast
Where the field lives and what it measures
Probability sits on the Opportunity object as a standard field labeled Probability (%). It expresses the chance that the opportunity reaches Closed Won, written as a whole percentage from 0 to 100. A brand new prospecting deal might read 10 percent. A deal in late negotiation might read 75 percent. A deal marked Closed Won reads 100 percent, and one marked Closed Lost reads 0 percent. The number is not a guess that floats free of the rest of the record. Salesforce ties it to the opportunity Stage so the two values stay in step. When you set up the Stage picklist, you assign a default probability to each stage value. That default is what populates the field as the deal moves forward. Because the field is editable, a rep who knows the deal well can override the stage default. The override sticks on that record and does not change the default for anyone else. This pairing of a sensible default with a manual escape hatch is what lets Probability stay both consistent across a team and accurate on a single high-stakes deal.
The link between Stage and the percentage
Stage drives Probability through the Stage picklist setup. Every value in that picklist (Prospecting, Qualification, Proposal, Negotiation, and so on) has a probability paired with it. When a rep changes the stage, Salesforce writes the matching default into the Probability field. So the everyday way probability changes is simply that the deal advances. There is one wrinkle worth knowing. If a rep manually overrides the probability and then changes the stage, the new stage default takes over and the manual value is replaced. Admins who want stage and probability to move fully independently sometimes remove the automatic link, but that means probability no longer updates on its own and reps must set it by hand. For most teams the better path is to design the stages so their default probabilities already reflect reality. If your Proposal stage really closes about half the time, set its default to 50 percent. Good stage design keeps the field trustworthy without forcing reps to fiddle with it on every deal.
Expected Revenue, the number probability feeds
Probability is the input to Expected Revenue, a standard read-only field on the opportunity. Expected Revenue equals Amount multiplied by Probability. An opportunity worth 20,000 dollars at 25 percent shows an Expected Revenue of 5,000 dollars. The same deal at 75 percent shows 15,000 dollars. The Amount is the full deal size if it closes. Expected Revenue is the risk-adjusted slice of that size. This single calculation is why probability quality matters so much. Expected Revenue rolls up into reports and pipeline views, so leaders use it to judge how much revenue is realistically in play, not just how big the open deals look on paper. If reps inflate probability, Expected Revenue inflates with it and the pipeline looks healthier than it is. If reps leave it stale, the number understates real momentum. Some teams build their own formula fields for weighted pipeline using Amount times Probability when they want the same logic on a custom report or list view. The math is identical. Expected Revenue is just the version Salesforce ships out of the box.
Probability versus forecast category
People often confuse probability with forecast category, and the two really do work together. Each opportunity stage maps to a forecast category such as Pipeline, Best Case, Commit, Omitted, or Closed. The category tells forecasting which bucket the deal belongs in. Probability is the percentage chance of closing. Stage is the bridge that sets both at once: change the stage and Salesforce updates the probability and the forecast category together. The difference is how each one is used. Probability drives Expected Revenue and weighted math on the record itself. Forecast category drives how amounts roll up in Collaborative Forecasts, where a Commit deal counts differently from a Best Case deal. A deal can sit at 60 percent probability while its stage maps to the Best Case category. Neither value is wrong. They answer different questions. Keeping both mappings aligned to how your stages actually behave is the heart of clean forecasting, because a stage that says 90 percent probability but maps to Pipeline sends mixed signals to anyone reading the numbers.
Probability in account and advanced forecasting
Beyond the basic Expected Revenue calculation, probability can feed richer forecasting features. In account forecasting, available in industry editions like Manufacturing Cloud, you can enable Opportunity Probability so that forecast revenue and quantity values are weighted by each opportunity's probability rather than counted at full value. A deal at 40 percent then contributes 40 percent of its amount to the projected number for that account. This gives a more honest forward view than treating every open deal as a certainty. The same idea applies whenever you weight a pipeline. Summing raw Amount across open deals tells you the ceiling, the most you could book if everything closed. Summing Amount times Probability tells you a grounded expectation. Sales operations teams lean on the weighted figure for planning because it absorbs the reality that not every deal lands. The catch is the same one that runs through this whole topic: the weighted number is only as good as the probabilities behind it. Disciplined stage definitions and periodic accuracy checks are what make weighted forecasting worth trusting.
Keeping probability honest over time
Probability is easy to set up and easy to let rot. The most common failure is stage defaults that were picked once and never revisited. If your Negotiation stage defaults to 70 percent but those deals historically close 45 percent of the time, every forecast built on that field is optimistic by design. The fix is to compare default probabilities against real win rates by stage, then adjust the defaults so they match what actually happens. Manual overrides deserve attention too. A rep who pushes a struggling deal to 90 percent to look good distorts Expected Revenue and the forecast. Many teams limit or audit overrides, or use validation rules and reports to surface deals where the probability looks out of line with the stage. The goal is not to ban judgment, since a rep often does know more than the default. The goal is to make sure the field reflects a real read on the deal rather than wishful thinking. Treated this way, Probability stays a quiet, reliable input that sales leaders can actually plan around.
Configure default probability per opportunity stage
Probability itself is a standard field you do not create. What admins configure is the default probability tied to each opportunity Stage value, so the field populates sensibly as deals advance. You do this in the Stage picklist setup on the Opportunity object.
- Open the Stage field setup
In Setup, go to Object Manager, open Opportunity, choose Fields and Relationships, and open the Stage field. This is where each stage value and its settings live.
- Edit a stage value
Under Opportunity Stages Picklist Values, click Edit next to a stage such as Proposal or Negotiation. Each value has its own configuration row.
- Set the default probability
In the Probability field for that stage, enter the whole-number percentage that should populate when a deal reaches this stage. Base it on how often deals at this stage really close.
- Confirm the forecast category
On the same screen, check the Forecast Category mapped to the stage so probability and category tell a consistent story, then save.
- Validate on a test opportunity
Open or create a test opportunity, move it through the stages, and confirm the Probability and Expected Revenue fields update as expected.
The whole-number percentage written to the field when an opportunity enters this stage. Set per stage value.
The forecasting bucket (Pipeline, Best Case, Commit, Omitted, Closed) the stage maps to. Keep it aligned with the probability you chose.
Whether the stage counts as closed. Closed Won stages use 100 percent and Closed Lost stages use 0 percent.
- Changing a stage overwrites any manual probability a rep entered, so an override does not survive a later stage change.
- Removing the link between stage and probability stops the field updating automatically, which means reps must set probability by hand on every deal.
- Expected Revenue recalculates from Amount times Probability, so wrong defaults quietly distort weighted pipeline and forecasts.
Trust & references
Cross-checked against the following references.
- Opportunity FieldsSalesforce
- Sample Opportunity Management FormulasSalesforce
Straight from the source - Salesforce's reference material on Probability.
Hands-on resources to go deeper on Probability.
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 is Probability on an opportunity?
Q2. How is probability typically set?
Q3. Why does probability matter?
Discussion
Loading discussion…