Forecast Categories Explained: Commit, Best Case, and Pipeline

Ask a rep why a deal is sitting in "Commit" and you'll sometimes get an honest, evidence-based answer and sometimes you'll get "because I really want it to close this quarter." Both answers get logged identically in the CRM. Forecast categories only work as a management tool if everyone applying them is using the same evidence bar, and in most sales organisations, nobody's ever actually written that bar down.

The Confidence Ladder

Forecast categories are a confidence ladder, not a status update. Each rung represents a genuinely different level of certainty that a deal will close within the current period — and, critically, Salesforce's own documentation confirms the category is a separate field from opportunity stage, editable by the deal owner independently of where the deal actually sits in the sales process. That's a deliberate design choice — stage tells you where a deal is in the process; forecast category tells you how confident the rep is it'll actually close, which are related but genuinely different questions.

Rung 1: Pipeline

What it means: Early-stage, still being worked, with meaningful uncertainty about whether it closes at all this period, let alone on the original timeline.

Realistic close rate: A relatively small share of deals sitting in Pipeline will actually close within the current period, this category exists specifically to hold deals that are real and being worked, but far from confirmed.

Where it goes wrong: Deals sit here indefinitely without a clear point at which they graduate or get disqualified, quietly inflating the raw pipeline total without ever contributing anything reliable to an actual forecast number.

Rung 2: Best Case

What it means: The deal is qualified, has a documented plan to close, but genuinely still has real work left before it's a safe bet. A scenario where the deal could close if things go well, not one where it's already largely decided.

Realistic close rate: Meaningfully higher than Pipeline, but still well short of certain, this is the category for deals with a plausible path to closing this period, not deals a rep is confident about purely on optimism.

Where it goes wrong: This is where "happy ears" forecasting lives, a rep hears mild interest from a buyer and logs the deal as Best Case based on enthusiasm rather than evidence like a confirmed timeline, budget, or next step actually scheduled.

Rung 3: Commit

What it means: Genuine, high confidence the deal closes this period, typically because the remaining steps are procedural rather than substantive: contracts are being finalised, or a verbal agreement is already in place and only needs signing.

Realistic close rate: This is the category leadership and finance should be able to build a number around with real confidence, deals here should only slip in exceptional, largely unforeseeable circumstances, not as a routine occurrence.

Where it goes wrong: Sandbagging in the opposite direction, a rep keeps a deal in Best Case even once it's genuinely Commit-ready, either to protect themselves against a surprise slip or to create room to "beat forecast" later. This is just as damaging as overclaiming, since it makes the forecast artificially conservative and erodes trust in the number from the other direction.

Rung 4: Closed

What it means: Won. No ambiguity, revenue that's actually landed, not projected.

The Off-Ramp: Omitted

What it means: Explicitly excluded from the current period's forecast, a close date has genuinely pushed out, the deal has gone unresponsive, or it's a renewal or house account that shouldn't count toward new-business forecasting in the first place.

Where it goes wrong: Without a clearly defined Omitted category, deals that should have been pulled from the current forecast simply sit uncounted in Pipeline or Best Case instead, quietly distorting the total rather than being explicitly and visibly set aside.

Why This Ladder Breaks Down in Practice

The categories themselves are simple. What breaks is the evidence bar each rep applies before moving a deal up a rung. Without a documented, agreed standard, which specifically justifies Commit versus Best Case, two reps looking at genuinely similar deals will place them in different categories based on personality alone: an optimistic rep sandbags nothing and inflates Best Case, while a cautious rep holds genuinely Commit-ready deals back out of habit.

Salesforce Ben's practical guidance on the topic makes exactly this point, how each category is actually defined can and should vary by business and sales cycle, but that definition needs to be explicit and shared with the whole sales team, not left to individual interpretation. Without that shared definition written down somewhere, forecast categories stop functioning as a confidence signal and start functioning as a Rorschach test for each rep's personality.

Two Specific Failure Patterns Worth Naming

Downgrade avoidance. Moving a deal from Commit back down to Best Case feels, to most reps, like publicly admitting they were wrong. The result is that deals often stay in an overly optimistic category well past the point where the evidence has actually changed, because nobody wants to be the one to move it down. Teams with genuinely accurate forecasting normalise downgrades explicitly, reframing them as forecasting doing its job correctly, not as an admission of failure.

Category-stage mismatch drift. Because forecast category is technically independent of stage, it's possible — and surprisingly common — for a deal to sit at an early stage while still being marked Commit, simply because a rep is confident, or for a late-stage deal to sit in Pipeline because nobody updated the category after the deal progressed. Left unmonitored, this drift quietly undermines the entire point of having two separate fields in the first place, since the category is meant to add information beyond what stage alone tells you, not simply duplicate or contradict it.

Building Forecast Category Discipline

Write the evidence bar down for each category, specifically enough that two different reps would place the same deal in the same bucket. "Commit requires a signed verbal agreement and a scheduled contract date," not "Commit means you feel good about it." Review category assignments in a regular forecast call, specifically interrogating any deal that's sat in the same category for multiple review cycles without moving, since stalled category placement is often as informative as the category itself. And track category accuracy over time, what percentage of deals marked Commit in a given period actually closed, since that single number tells you more about whether your forecast can be trusted than any other metric in the process.

A Forecast Is Only as Honest as the Evidence Behind It

The categories were never the hard part. Getting every rep to apply the same evidence bar before moving a deal up a rung is, and that's a discipline problem, not a CRM configuration problem.

Digital Squad's data analytics work builds the reporting layer that makes this discipline visible rather than assumed — tracking forecast category accuracy over time, flagging deals that have stalled in the same category for multiple review cycles, and giving RevOps and sales leadership a clear, evidence-based read on which categories can actually be trusted this quarter. If your Commit number has a habit of quietly slipping every period, that's a data problem worth diagnosing properly, not just a forecasting conversation to have again next quarter.