Every forecast call uses the same categories: Commit, Best Case, Upside. Every forecast call treats them as if they mean something consistent. They don't. In most organisations, Commit means "I hope so," Best Case means "if the buyer returns my call," and Upside means "I met them once at a conference."
The categories are not the problem. The problem is that nobody has defined what evidence moves a deal into each category. Without evidence criteria, the categories become containers for rep confidence levels — and rep confidence is the least reliable predictor of deal outcomes.
What the Categories Should Mean
Commit
Definition: This deal closes in the forecast period if nothing goes wrong.
That's a high bar, and it should be. A commit deal should have all of the following confirmed — not assumed, confirmed:
The economic buyer has verbally agreed to proceed. The commercial terms are substantially agreed. The procurement/legal/security processes are either complete or underway with a known timeline. The buyer has confirmed the close date in their own words.
If any of these are missing, the deal is not a commit. It might be close. It might be likely. But commit should mean something specific, and that specific thing is: "The only way this doesn't close is if something unexpected happens."
Most organisations have commit deals where the buyer hasn't confirmed the timeline, legal hasn't started, or the economic buyer hasn't been involved. These deals are Best Case at best. Putting them in Commit inflates the number and erodes trust in the category.
Best Case
Definition: This deal closes in the forecast period if something specific goes right.
The key word is "specific." The rep should be able to name the exact thing that needs to happen: "The legal review completes by the 20th," or "The VP of Engineering approves the budget in Thursday's meeting," or "They choose us over CompetitorX after the final presentation on the 15th."
If the rep can't name the specific thing, the deal doesn't belong in Best Case. It belongs in Upside or Pipeline — because the rep doesn't actually know what needs to happen, which means they can't influence it.
Upside
Definition: This deal could close in the forecast period, but multiple things need to go right, and the rep cannot control all of them.
Upside is the honest category for deals where the buying process is genuinely underway but the timeline is uncertain. The buyer is engaged, the problem is real, there's budget — but there are multiple dependencies and the close date is the rep's best guess, not the buyer's confirmed plan.
Why the Categories Break Down
Three things destroy forecast categories in practice:
1. No shared definition. If you ask five reps what "commit" means, you'll get five answers. Without a written, enforced definition — backed by evidence criteria — the categories are just labels people apply based on gut feeling.
2. Social pressure. Managers who need a bigger commit number to make their rollup work will pressure reps to move deals from Best Case to Commit. This isn't about forecast accuracy anymore. It's about making the forecast call survivable. The number goes up, the confidence goes down, and the category becomes meaningless.
3. No consequences for miscategorisation. When a commit deal doesn't close and nobody examines why it was in Commit in the first place, the message is clear: the categories don't matter. Call it whatever you want. Nobody will check.
How to Make the Categories Real
Write Down the Evidence Criteria
For each category, define the specific buyer actions or conditions that qualify a deal. Not rep activities. Buyer actions. Then make those criteria visible — printed on the wall, embedded in the CRM, reviewed in every pipeline review.
Here's a starting point:
Commit requires: Economic buyer verbal confirmation, commercial terms agreed, procurement/legal timeline confirmed by the buyer, close date confirmed by the buyer (not assumed by the rep).
Best Case requires: Champion confirmed, problem and budget confirmed, one specific named dependency remaining, buyer-confirmed activity scheduled to resolve it.
Upside requires: Qualified opportunity with engaged buyer, multiple dependencies remaining, no buyer-confirmed close date.
Review the Categories, Not Just the Deals
In your weekly review, don't just ask "will this close?" Ask "does this deal meet the criteria for the category it's in?" If it doesn't, move it. Every time. This is the enforcement mechanism that makes the categories meaningful.
Track Category Accuracy Over Time
After each quarter, look at what actually closed versus what was in each category. What percentage of Commit deals actually closed? What percentage of Best Case converted? This historical data tells you two things: whether your criteria are right, and which reps categorise accurately versus optimistically.
A team where 90% of Commit deals close has meaningful categories. A team where 50% of Commit deals close has a labelling problem that no amount of pipeline coverage can fix.
The Real Problem Underneath
Forecast categories are a symptom of a deeper question: does your organisation value honest forecasting or comfortable forecasting? If the forecast call rewards reps who hit their commit number and punishes reps who miss it — regardless of whether the miss was foreseeable — then the categories will always be gamed.
Make it safe to forecast honestly, define what each category means in evidence terms, and enforce those definitions consistently. The categories will start to mean something. The forecast will start to be useful. And the board will stop hearing a number that nobody in the building believes.
For the complete framework that turns forecast categories into evidence-based commitments — including the 38 diagnostic questions — download the Pipeline & Forecast Framework. It gives you the system for making every forecast conversation honest.