What Are Sales Forecast Categories, and Why Do They Drift Out of Sync?
Sales forecast categories are the buckets that sort every open deal by how likely it is to close inside the current period, and most teams let them drift because the buckets were never defined. The common set is Pipeline, Best Case, Commit, Closed, and Omitted. A deal moves up the ladder as confidence rises, and the rollup of Commit plus a slice of Best Case becomes the number a manager carries into the forecast call.The categories only work if every rep fills them the same way. That is where most orgs break. A sales stage tells you where a deal sits in the process. A category tells you the rep's judgment about whether it lands this period. Those are different axes, and a deal can be late-stage and still belong in Pipeline if the close date is a quarter out. When a team treats category as a mood ring instead of a contract, the forecast inherits every rep's private definition of confidence.
Why Does Commit Mean Something Different to Every Rep?
Because almost nobody writes down what Commit requires, so each rep fills it from gut feel. To one rep, Commit is a countersigned order form. To another, it is a warm call and a good feeling. Both deals land in the same column, and the manager rolling them up has no way to tell the signed deal from the hopeful one.The cost shows up at quarter end. In our data, a deal that slips its close date from one quarter to the next is less likely to close, even when it is sitting in Commit. The rep moving the close date is the clearest deal-slippage signal we track, and the Commit label does not protect against it. Coverage math makes the gap worse. Of the pipeline dated to close in a quarter, measured on the first day of that quarter, only about 20% actually closes inside the quarter. Eighty percent of the value the calendar promised on day one does not arrive on time. If your Commit column runs on the same optimistic dating, it inherits the same miss.
What Hard Entry Criteria Define Each Forecast Category?
Every category needs objective gates a manager can check without trusting the rep's optimism. Write them as conditions that are either true or false, then require all of them before a deal earns the label. Here is the definition set I hand teams as a starting point.| Category | What it claims | Entry criteria, all must be true | In the submitted number |
|---|---|---|---|
| Commit | Closes this period | Close date in the period and unchanged for two weeks; economic buyer confirmed; pricing and terms agreed; order form or procurement in motion; no open blocker owned by the customer | Yes, at full value |
| Best Case | Could close with one break | Close date in the period; champion confirmed; proposal delivered; a single named risk with a dated mitigation step | Upside, not the base |
| Pipeline | Qualified, not near | Opportunity qualified; a next step booked on the calendar; meaningful activity in the last 30 days | No |
| Closed Won | Signed | Countersigned order or purchase order received | Yes, as actuals |
| Omitted | Out of the forecast | Disqualified, pushed beyond the period, or stale past the activity threshold | No |
How Do You Stop a Deal From Riding in Commit on Autopilot?
Require fresh evidence to stay, not only to enter. A category is a claim with an expiration date. At ORM we count meaningful activity as a change in stage, close date, or amount, and a deal that shows none of those is going quiet. Silence is the earliest risk signal we see, earlier than any negative note, because a buyer who has stopped moving the deal has usually stopped buying.Two enforcement rules keep the column honest. First, age out stale deals. More than 10% of the average pipeline has not been touched in 12 months, and stale deals do not belong in a forward number no matter what category they carry. We apply a 12-month rule for most customers so that dead weight drops out on a schedule. Second, treat a close-date change as a demotion trigger, not a clerical edit. When a rep pushes the date, the deal leaves Commit until it re-earns every gate. Both rules retire the standing assumption that a label, once granted, is permanent.
Are Forecast Categories the Same as the Forecast?
No. Categories are inputs to the forecast, not the forecast itself. A clean Commit column tells you what the team believes will close from the pipeline you can see. It says nothing about the revenue that will be created and closed inside the period, or about deals pulled forward from later, and it quietly overstates value on the deals it does contain. Most deals close for less than their CRM amount. We see pipelines with an average deal size of $80,000 whose closed-won deals average $40,000, so a category rollup taken at face value books revenue that never shows up.Hard entry criteria fix the input. They make Commit mean one thing, and they strip the stale and slipping deals out so a model has clean signal to work from. That is where the categories earn their keep. Once the buckets are disciplined, the same stage, close-date, and amount changes that gate them can be read by a model to weight each deal and project the period forward, instead of trusting a column of hand-labeled confidence. Categories set the language. The forecast is what you build once every rep speaks it the same way.
Frequently Asked Questions
What are the standard sales forecast categories?
The common set is Pipeline, Best Case, Commit, Closed, and Omitted. A deal moves up the ladder as the rep's confidence in a same-period close rises. Commit at full value plus a portion of Best Case usually becomes the number a manager carries into the forecast call, while Pipeline and Omitted stay out of it. The categories only produce a reliable forecast if every rep applies the same entry criteria to each bucket.
What is the difference between a forecast category and a sales stage?
A sales stage marks where a deal sits in the sales process, from qualification through negotiation. A forecast category marks the rep's judgment about whether the deal closes inside the current period. They are separate axes. A deal can sit in a late stage and still belong in Pipeline if its close date falls in a future period, and an early-stage deal never belongs in Commit no matter how large it is.
What criteria should a deal meet before it goes in Commit?
A commit deal should have a close date inside the period that the rep has not moved recently, a confirmed economic buyer, agreed pricing and terms, paper or procurement already in motion, and no open blocker owned by the customer. If any one of those is missing, the deal is Best Case at most. Writing the gates down is what makes commit mean the same thing across the team.
Why do reps put deals in Commit differently?
Because most teams never define what Commit requires, so each rep fills it from personal confidence. One rep commits only a signed order, another commits a promising conversation, and the rollup treats both as the same deal. Objective entry criteria remove the interpretation. When Commit is a checklist of facts rather than a feeling, the variance between reps collapses and the forecast gets more accurate.
Are forecast categories the same as the forecast?
No. Categories are inputs. A Commit rollup describes what the team expects to close from visible pipeline, but it ignores revenue that will be created and closed inside the period, ignores deals pulled forward from later, and tends to overstate value because many deals close for less than their CRM amount. Disciplined categories give a forecasting model clean signal, and the model turns that signal into the number.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo