Sales Forecast Categories: What Each One Means and How to Use Them
Learn what Pipeline, Best Case, Commit, Closed and Omitted mean, how they differ from sales stages, and how to set rules that keep your forecast honest.
Sales forecast categories are labels that tell you how a deal is treated in your forecast for the current period. The five most common are Pipeline, Best Case, Commit, Closed and Omitted. Each says how likely an opportunity is to close in the forecast window, and together they let a manager roll individual deals up into a revenue number. They only work when everyone on the team applies them the same way, so most of this guide is about definitions, evidence and discipline rather than vocabulary.
TL;DR
- Forecast categories describe forecast treatment (how likely a deal is to close this period). Sales stages describe where a deal sits in the sales process. Keep them as two separate fields.
- The common set is Pipeline, Best Case, Commit, Closed and Omitted. Closed and Omitted are outcomes or exclusions, while the other three express confidence.
- Write objective entry criteria for each category so one manager’s Commit is not another manager’s Pipeline.
- Roll up each category separately, then review how deals move between categories week to week.
- Review evidence on every Commit deal: decision timing, approver, budget and a compelling event.
Table of Contents
- What forecast categories are
- The five standard categories
- Forecast category vs. sales stage
- Why categories break down in practice
- How to assign categories with objective criteria
- How categories roll up into the team forecast
- A weekly forecast review that keeps categories honest
- Our perspective
- Set up forecast categories in Strkr
- Common mistakes to avoid
- FAQ
- Sources
What forecast categories are
A forecast category is a bucket you assign to each open opportunity so the team can estimate when and how much revenue will arrive in the period being assessed. Salesloft’s guide is one example of this definition in use, and the idea is consistent across most revenue teams: a deal is not simply “worth $40,000”, it is worth $40,000 at some level of confidence, in some period.
That extra dimension is the whole point. Two deals with the same amount and the same stage can deserve very different treatment in the forecast. One has a signed order form waiting on a countersignature. The other has a champion who likes the product but has not mentioned budget. A category is where you record that difference.
The five standard categories
Names vary between teams and CRMs, but the logic is a ladder from least to most certain, with two special buckets at the edges.
| Category | What it means | Typical evidence | Counted in the number? |
|---|---|---|---|
| Pipeline | Qualified and open, but no strong signal of closing this period | Active conversation, need confirmed, no committed date | Tracked, not forecast |
| Best Case | Could close this period if things go well | Buyer engaged, timeline plausible, one or more gaps remain | Upside |
| Commit | The rep and manager expect it to close this period | Approver identified, budget confirmed, decision date inside the window | Yes, the call |
| Closed | Won or lost during the current period | Signed contract, or a recorded loss | Won amounts are actuals |
| Omitted | Lost, dropped or unqualified, excluded from forecasts | Disqualified, duplicate or dead | No |
The definitions of Closed and Omitted match how Salesloft describes them: Closed covers deals designated closed-won or closed-lost in the current period, and Omitted covers lost or dropped opportunities that are unqualified and left out of forecasts.
Pipeline
Pipeline is the default home for an opportunity that is real but not yet predictable. It is useful for coverage math, because it shows how much early-stage volume you are carrying into future periods. It is not a prediction for this period. If you want the mechanics behind that coverage view, our explainer on what a sales pipeline is covers opportunities, stages and coverage ratios.
Best Case
Best Case is the upside layer. These deals have momentum and a believable path to closing inside the window, but something is still unresolved: a legal review, a second stakeholder, a budget that has not been confirmed. Teams use Best Case to answer “what is the ceiling if the quarter goes well?” without promising it.
Commit
Commit is the call. When a rep puts a deal in Commit, they are telling their manager they would be surprised if it did not close this period. Because it carries the most weight, it is also the category most prone to wishful thinking, which we cover below.
Closed
Closed is not a forecast, it is a result. Including it in the category list lets one report show the closed-won amount, what remains to be won and what the full range looks like, all in the same view.
Omitted
Omitted keeps junk out of your numbers without deleting history. A duplicate, a contact who left, or a deal the buyer has ended can be removed from every forecast roll-up while the record stays available for analysis.
Forecast category vs. sales stage
This is the most common source of confusion, and the cause of most bad forecasts. A sales stage describes where a deal is in your sales process: discovery, demo, proposal, negotiation. A forecast category describes how the deal should be treated in the forecast. SBI Growth’s forecasting guide says the two should be defined separately, and its reasoning holds up in practice.
Here is why they must stay independent:
- A deal in Negotiation can be a poor Commit if the buyer has gone quiet for three weeks.
- A deal in Proposal can be a strong Commit if the buyer has a hard deadline and an approved budget.
- A rep should be able to move a deal from Commit to Best Case after a bad call without rewinding its stage, because the process step the deal reached did not change; only your confidence did.
If you tie category to stage automatically (every Proposal is Best Case, every Negotiation is Commit), you are really running a weighted pipeline, not a category forecast. That is a legitimate method, but it is a different one. For the full range of approaches, see our overview of what sales forecasting is and how revenue forecasting extends it.
Why categories break down in practice
The ladder looks tidy on a slide. In a live quarter, three failure patterns show up again and again.
Inconsistent definitions. If every manager defines Commit differently, the roll-up mixes incompatible numbers. SBI Growth’s perspective is that accuracy depends on objective, shared definitions, otherwise one manager’s Commit is another manager’s Pipeline.
Category drift to the end of the period. Deals sit in Pipeline for weeks, then jump straight to Commit in the last days. The category adds no information because it only reflects what has already happened.
Sandbagging and optimism. Some reps hold deals back to protect a number they already hit. Others commit everything with a pulse to look confident. Neither is dishonest in intent, but both distort the signal. The fix is evidence, not exhortation.
How to assign categories with objective criteria
The practical remedy is a written set of entry criteria for each category, applied the same way to every deal and separate from stage. SBI Growth recommends vetting opportunities against a defined set of questions covering the customer’s challenge, a compelling event, the capabilities required, success metrics, decision timing and who must approve.
Turn that into a checklist your team can actually use:
- Pipeline: the need is confirmed and a qualified contact is engaged. No requirement for a date.
- Best Case: everything in Pipeline, plus a stated business problem, a rough timeline inside the period and a known path to the decision maker.
- Commit: everything in Best Case, plus the approver identified and engaged, budget confirmed, a decision date inside the period and a compelling event that explains why the date is real.
- Closed: a signed order form, or a recorded closed-lost reason.
- Omitted: disqualified, duplicate or no longer a buying opportunity, with a reason code.
Few checklists are perfect on day one. Salesloft recommends writing the definitions collaboratively in a sales-process playbook, so the revenue team shares ownership of them and applies them consistently. We agree, and it is the same reason we suggest a documented sales playbook with a named owner.
Make the criteria testable
A good criterion is something you can check in the CRM without asking the rep how they feel. “Champion is confident” is an opinion. “Approver has attended a call and a decision date is recorded” is a fact. Wherever you can, convert judgment into a field that is either filled or empty.
How categories roll up into the team forecast
A forecast is a sum of deal amounts grouped by category, owner and time period. The roll-up usually works in three layers:
- Rep level. Each rep’s open deals closing in the period are summed by category: Closed so far, Commit, Best Case and Pipeline.
- Manager level. The manager reviews each rep’s submission, may adjust it, and sums the team. The manager’s Commit is their own view, not simply the sum of the reps’ Commits.
- Company level. Leadership sums the managers’ numbers by category and compares them with quota.
The most common way to read the result is as a range. A simple view looks like this:
| View | How it is built |
|---|---|
| Floor | Closed |
| Likely | Closed + Commit |
| Ceiling | Closed + Commit + Best Case |
Worked example with made-up numbers: a team has $310,000 closed, $180,000 in Commit, $240,000 in Best Case and $900,000 in Pipeline for the quarter. The floor is $310,000, the likely number is $490,000 and the ceiling is $730,000. Pipeline is excluded because it is not an expectation for this period. If the quota is $600,000, you can see immediately that the team needs roughly $110,000 of Best Case to convert, and you can ask which specific deals those are.
Track historical conversion by category too. If your Commit deals have closed at a consistent rate over several quarters, you can apply that observed rate to the current Commit total instead of treating it as 100%. SBI Growth lists historical conversion data, regular forecast reviews and data hygiene among the practices that improve accuracy. Clean records matter here, so a routine like CRM hygiene is part of the forecasting system, not a separate chore.
Once the forecast is credible, finance can use it. Teams planning cash on the back of expected bookings can feed the numbers into a cash flow forecast calculator to see how a Commit slip would affect the next 90 days.
A weekly forecast review that keeps categories honest
Categories only stay useful if someone inspects them on a schedule. A review that works for most teams of 5 to 30 sellers takes 30 to 45 minutes and follows a fixed order:
- Movement. Which deals moved between categories since last week, and why? Every move up needs evidence, and every move down needs a reason.
- Commit inspection. For each Commit deal, check approver, budget, decision date and compelling event against your criteria.
- Best Case gaps. For each Best Case deal, name the one thing that would make it Commit and who owns it.
- Slipped deals. Any deal that missed its date gets a new date and a reason, or moves out of the period.
- Omitted cleanup. Dead and duplicate deals are removed so they stop inflating the pipeline.
The movement review is the most valuable step. Tracking how deals travel between categories shows you which reps are consistently early or late, and which criteria are too loose.
Our perspective
We build Strkr for teams that are tired of forecasting in spreadsheets stitched to a CRM that does not match their process. From what we see when teams switch from other systems, the category labels are rarely the problem. The problem is that the rules behind them live in someone’s head, or in a slide nobody opens.
Our view is that the category should be a first-class field that sits next to the stage, with its own criteria, and that those criteria should be fields in the record, not opinions. Because Strkr supports custom objects and fields, a team can model the exact evidence it requires for Commit (approver, budget confirmed, decision date, compelling event) on the deal itself, and then report on it. Strkr AI forecasting works on top of that structure, so a forecast reflects how your team actually sells instead of a generic template.
We also believe a forecast should be inspectable. If a number cannot be traced to specific deals and specific evidence, it is a guess with a formula around it. Pair categories with a short, written definition set, a weekly movement review and clean data, and most of the drama goes out of quarter-end.
, Josh
Set up forecast categories in Strkr
If you want categories, stages, evidence fields and forecasting in one workspace, Strkr is built for that. Pro is $59 per month per seat and Starter is $29 per month per seat, with the full plan list on our pricing page. Flows let you automate parts of the review, such as flagging a Commit deal with no decision date, without writing code. If you are exploring how automation fits, our guide to CRM automation explains triggers and routing.
Common mistakes to avoid
- Using categories as a mood ring. If a category changes because of how a call felt rather than what was learned, it is noise.
- Putting everything in Commit. Commit should be a small, defensible set. If it routinely exceeds quota by a wide margin, the criteria are too loose.
- Mixing category and probability. A category is not a percentage. If you also use weighted probabilities, define them separately and review both.
- Skipping the Omitted bucket. Dead deals left in Pipeline inflate coverage and mislead everyone.
- Changing definitions mid-quarter. Revise criteria between periods so you can compare results fairly.
FAQ
What is the difference between Commit and Best Case?
Commit means you expect the deal to close in the period and can show the evidence: an engaged approver, confirmed budget and a real decision date. Best Case means it could close if the remaining gaps resolve. Treat Commit as your forecast call and Best Case as upside.
Are forecast categories the same as sales stages?
No. A stage shows where a deal is in your sales process, while a category shows how the deal is treated in the forecast. Keeping them separate lets a rep lower confidence in a deal without pretending it went backward in the process.
How many forecast categories should a team use?
Most teams use five: Pipeline, Best Case, Commit, Closed and Omitted. Fewer categories are easier to apply consistently, so add more only if you can write an objective rule for each one.
How do I improve the accuracy of category-based forecasts?
Start with shared written definitions and objective criteria, separate from stage. Then review Commit deals against evidence weekly, track movement between categories and compare each category’s results to history. Clean CRM data underpins all of it.
Sources
- Guide to Improve Accuracy in Forecasting and Pipeline Management, SBI Growth
- Sales Forecast Categories & Revenue Guide, Salesloft