Forecast categories describe where opportunities sit in a sales team's confidence and process model. Salesforce's standard categories include Pipeline, Best Case, Commit, Omitted, and Closed, with an optional Most Likely category; cumulative rollups combine defined categories rather than applying one hidden percentage to the whole funnel. This lesson adapts the logic into clear base, upside, and open-pipeline views that executives can trace back to actual deals.

VISUAL LESSON

What you will learn

  1. 01Map stages and evidence to forecast categories.
  2. 02Construct transparent base and upside rollups.
  3. 03Explain forecast movement and overrides deal by deal.
Opportunity cards sort into pipeline, best-case, commit and closed layers that form transparent forecast bands
A forecast is more trustworthy when every scenario is a visible rollup of governed categories and deal evidence.

ILLUSTRATIVE WORKED EXAMPLE

Build an illustrative quarterly scenario

ClosedCompleted outcome
$200k
Commit openEvidence-backed commit
$150k
Best case openUpside candidate
$100k
Pipeline openNot in base or upside
$50k
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Move from stages to traceable scenarios

Map01Define category evidence

Connect each stage to Pipeline, Best Case, Most Likely if used, Commit, Omitted, or Closed and record exceptions.

Roll02Publish scenario formulas

For example, base equals Closed plus Commit; upside adds Best Case; open pipeline remains visible but separate.

Explain03Reconcile week-over-week movement

Attribute change to won, lost, new, moved in or out, amount change, close-date shift, or category override.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Stage evidence → forecast category → scenario rollup → movement bridge

EvidenceDeal and next event
CategoryPipeline to Closed
BridgeWhat changed and why

THE LEAD ATLAS METHOD

When forecast coverage is thin in a territory, Lead Atlas Data can research a custom list of business contacts specific to the missing categories, locations, and market for a governed new-pipeline campaign.See how custom list research works ↗
01

Define categories with observable evidence

Write what Pipeline, Best Case, Most Likely if used, Commit, Omitted, Closed Won, and Closed Lost mean in this business. Include required stage, customer action, commercial approval, next event, close date, and disqualifiers. A label such as Commit should not mean that the owner feels positive.

Map each opportunity stage to a default forecast category and publish the mapping. Salesforce allows category behavior and labels to be configured, so record the actual organization setup rather than assuming a universal stage-percentage table.

02

Separate open and closed amounts

Closed Won is an accomplished outcome within the reporting period; Commit and Best Case remain open risk. Preserve open amount, closed amount, currency, expected close date, product or service, owner, and category. Exclude Closed Lost and intentionally Omitted records from applicable forecast totals while retaining them in the audit trail.

Check duplicate opportunities, split ownership, multi-currency conversion, recurring versus one-time amount, schedule dates, and partial deals. A clean category model cannot fix inconsistent amount definitions.

03

Publish scenario formulas

Choose transparent rollups. An illustrative base may equal Closed plus open Commit; upside may add open Best Case or Most Likely according to the team's model; open pipeline remains a coverage view rather than forecast. Salesforce documents both single-category and cumulative rollups, so label which logic the report uses.

Do not multiply the entire pipeline by one arbitrary probability and call the output precise. If probability-weighted analysis is useful, publish it as a separate model with source, calibration period, cohort, and error history—not as a hidden replacement for category evidence.

04

Govern overrides and manager judgment

Allow an owner or manager to override a default category only with a reason, evidence, date, and next review. Common reasons may include customer-confirmed date, legal timing, capacity constraint, approved expansion, dependency, or known cancellation risk. Preserve the mapped category and override history.

Require review for large amounts, repeated category changes, pushed close dates, blank next steps, or a Commit without a scheduled customer event. Management adjustment can express judgment, but it should not erase the deal-level source.

05

Explain movement with a bridge

Reconcile one forecast snapshot to the next using Closed Won, Closed Lost, new opportunity, moved into period, moved out, amount increase or decrease, category change, close-date shift, and correction. Show base, upside, open pipeline, and gap to plan separately; describe uncertainty instead of promising the scenario.

Deliverable: forecast-category dictionary, stage mapping, amount and currency rules, base and upside formulas, open-pipeline view, override policy, high-value review list, weekly movement bridge, actual-versus-forecast history, error commentary, owner, and next forecast meeting date.

THE TAKEAWAY

Define categories with observable evidence, keep closed and open amounts separate, publish scenario formulas, require reasons for overrides, and explain forecast change through deal movement rather than optimism.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.