Two numbers, two different signals
Committed pipeline is a human judgment; weighted pipeline is a mathematical estimate. Both belong in the same forecast review. Commit surfaces rep conviction and surfaced risk. Weighted pipeline shows what the stage probability model implies, independent of how the rep feels about the deal.A commit is binary at the deal level. A rep puts a deal in commit or does not. The sum of committed deals is the rep's forecast. Weighted pipeline is continuous, treating every open deal as a fractional contribution to expected revenue based on its stage multiplier.
How the two numbers interact in a forecast review
| Scenario | What it signals |
|---|---|
| Commit > weighted pipeline | Rep is optimistic beyond what stage probabilities justify; investigate deal quality |
| Commit < weighted pipeline | Rep is sandbagging or holding back deals they believe will close; probe the gap |
| Commit and weighted pipeline aligned | Rep confidence and historical conversion rates are consistent |
| Large single deal in commit not in weighted model | Check if stage probability is understated or deal is genuinely unusual |
Where each breaks down
Committed pipeline breaks down when managers reward optimistic calls and penalize conservative ones. Reps learn to over-commit, and the commit number becomes a best-case scenario instead of a credible call. Weighted pipeline breaks down when stage probabilities are set once during CRM configuration and never recalibrated against actual close rates. A 40% probability at Proposal stage may reflect the team's actual close rate from two years ago, not today's buyer behavior.
Both metrics depend on clean CRM hygiene. A deal sitting in the wrong stage inflates or deflates both the weighted total and the commit list simultaneously.
Using them together without conflating them
Run both in your weekly forecast review. Compare the commit number to weighted pipeline for each rep and for the roll-up. When they diverge by more than a threshold your team defines, drill into the specific deals causing the gap. Also cross-reference commit against the commit vs. best case framework to ensure reps are making clean, categorical calls rather than hedging.
Forecast accuracy should be tracked separately against commit and against weighted pipeline so you can determine which signal is more predictive for your team over time. Some organizations find commit more reliable; others find weighted pipeline outperforms human judgment consistently. Running that calibration is what actually improves your forecast process.Frequently Asked Questions
What is committed pipeline?
Committed pipeline is the set of deals a rep or manager is willing to call as closing within the forecast period. It is a judgment call. The rep is, in effect, staking their credibility on those deals. It does not account for probability; every deal in the commit bucket is treated as a 1 or a 0.
What is weighted pipeline and how is it calculated?
Weighted pipeline multiplies every open opportunity's value by its close probability to produce an expected value. If a deal worth $100K is at a 40% probability stage, it contributes $40K to weighted pipeline. The total weighted pipeline across all open deals is a statistical estimate of revenue, not a rep's call.
Which is more accurate for forecasting?
Neither alone is sufficient. Committed pipeline captures rep conviction and surfaced risk, but it is subject to sandbagging and optimism bias. Weighted pipeline removes the human filter but is only as accurate as the underlying stage probabilities, which are often set arbitrarily. The most accurate forecasts use both, then compare commit totals against weighted pipeline to identify conviction gaps and outlier deals.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like committed pipeline vs. weighted pipeline into prescriptive action for your team.
Schedule a Demo