A commit deal needs a date the buyer owns.

Monday's forecast call reaches an $180,000 opportunity.

The rep has it in Commit. The buyer likes the product, the demo went well, and the close date is the last day of the quarter.

The manager asks what the buyer has agreed to do next.

There is no dated action. Procurement has not seen the order form. The person who controls the budget has not joined a call. The close date came from the seller's plan, not the buyer's calendar.

Nothing about the opportunity is imaginary. It may close. But the CRM does not yet support the word Commit.

Forecast categories work when they make a claim the rest of the company can inspect. They fail when Pipeline means early, Best Case means hopeful, and Commit means the rep would rather not move the date.

Stage and category answer different questions

Salesforce describes forecast categories as categories within the sales cycle, tied to opportunity stages. Its standard set includes Pipeline, Best Case, Commit, Omitted, and Closed. Some teams also use Most Likely.

An opportunity stage describes where the deal is in the sales process. A forecast category describes the seller's current claim about whether it will close in the forecast period.

Those claims are related, but they are not identical.

Two opportunities can sit in contract review while carrying different forecast categories. One buyer has approved the commercial terms and booked a Friday signature review. The other has sent the contract to legal with no owner, meeting, or deadline. The stage is the same. The evidence for the quarter is not.

Clari makes this distinction explicit: stage tracks progress through the sales process, while category communicates the seller's confidence about the period. Clari also warns that two reps can use Commit while relying on very different interpretations.

That is the real design problem. A category name alone does not create a shared forecast.

Give each category an inspectable meaning

The definitions below are deliberately plain. Adapt them to your sales cycle, then add the evidence a manager expects to see.

Omitted

The opportunity is excluded from the current forecast. It may be a renewal handled elsewhere, a duplicate, a deal with no credible path this period, or another case your team has agreed not to count.

Omitted should include a reason. Otherwise it becomes a quiet place to hide opportunities nobody wants to discuss.

Pipeline

The opportunity is real and active, but the buyer has not established a credible path to close this period.

The team may have confirmed a problem and a relevant use case. It may even have a target date. Pipeline says the timing remains unproven.

Best Case

The opportunity could close this period if named conditions are resolved.

Those conditions should appear in the CRM. Perhaps finance still needs to approve the business case, security needs to accept one control, or the buying committee has to choose between two vendors on Thursday. Best Case is not a softer version of Commit. It is a list of work that still has to go right.

Commit

The seller expects the opportunity to close this period and can show why.

At minimum, the record should contain a buyer-owned date, the remaining purchase steps, the people responsible for them, and the known risks. A mutual action plan is useful when the deal is complex. A short written sequence may be enough for a simpler sale.

The buyer does not have to promise that nothing will change. The team does have to know what happens between today and signature.

Closed

The outcome has happened. Closed Won and Closed Lost belong in actuals, not in the forecast argument.

Run the Commit test

Before moving a deal into Commit, ask the rep to show the path without retelling the entire opportunity.

The useful entries contain dates, owners, decisions, and unfinished work. Another manager can read them and challenge the category without asking the rep to reconstruct three calls from memory.

If the buyer has not accepted the timing, the deal may still deserve Best Case. If nobody can name the remaining conditions, it belongs in Pipeline until the team learns more.

Keep the reason beside the category

A dropdown cannot explain itself. Add a short category reason beside it.

For example:

That reason should change when the category changes. Keep the previous value, the date, who changed it, and the evidence behind the move.

This history answers questions that a current dropdown cannot:

• Did the opportunity enter Commit before the economic buyer approved the spend?
• How long did it remain in Best Case?
• Which condition caused the date to slip?
• Did the seller move the category after new buyer evidence, or just before the forecast call?

The history is also useful after the quarter. Teams can compare the evidence present in deals that closed with the evidence missing from deals that slipped.

Do not let stage mapping make the decision

Salesforce supports mapping opportunity stages to forecast categories. That mapping is helpful as a default. It keeps a newly created opportunity from starting with an empty category and gives reporting a consistent structure.

It should not make the final judgment for every deal.

If every opportunity in negotiation automatically becomes Commit, the sales process has quietly replaced forecast judgment. A stage can tell you that pricing was presented. It cannot tell you whether the buyer accepted the commercial path, whether procurement has an owner, or whether the close date belongs to anybody outside the sales team.

Use stage mapping to suggest a category. Let the owner adjust it when the deal-specific evidence says otherwise. Require a reason for moving into Commit or moving out of it.

Make the weekly call about changes

Gong describes a forecasting rhythm built around daily awareness and a deeper Monday review of targets, progression, and deal likelihood.

The CRM should carry the status before the meeting. The forecast call can then focus on what changed.

Review four groups:

1. Deals newly moved into Commit.
2. Deals moved out of Commit or pushed to another period.
3. Best Case deals with a near-term condition that could change the category.
4. Deals whose evidence has gone stale.

For each one, inspect the buyer action, the remaining condition, and the owner of the next move. End with an action or a category change.

Reading every open opportunity aloud wastes the very context the CRM was meant to preserve. A clean pre-read lets the meeting spend time on judgment.

Measure whether the categories mean anything

Do not borrow another company's benchmark. Start with your own history.

For each quarter or month, track:

• the share of Commit opportunities that closed in the stated period;
• the share of Best Case opportunities that moved to Commit and then closed;
• the average time an opportunity spent in each category;
• how often deals entered Commit and later returned to Best Case or Pipeline;
• the recorded reasons for slips, losses, and category changes.

Look at the evidence too. If Commit deals with a buyer-owned date close more often than Commit deals without one, the field is earning its place. If a required field has no relationship to decisions or outcomes, stop making reps maintain it.

Accuracy is not the only goal. A useful forecast should expose risk early enough for somebody to act. A perfectly documented miss on the final day of the quarter is still late.

Capture context without outsourcing judgment

Meeting notes, email summaries, and call recordings can help populate the record. They can find dates, named stakeholders, open questions, and buyer commitments that would otherwise remain in a notebook.

Automation should attach the source and mark what the buyer confirmed. It should not promote an opportunity to Commit because a phrase sounded positive.

The account owner still decides what the evidence means. The manager still owns the forecast standard. The system's job is to preserve enough context for that judgment to be visible and revisable.

Copy this forecast record

Forecast category: Omitted, Pipeline, Best Case, Commit, or Closed

Category reason: one or two sentences explaining why the current evidence supports the category

Buyer-owned date: the date and the buyer event that gives it meaning

Remaining conditions: decisions, approvals, reviews, or documents still required

Owners: the person responsible for each remaining buyer and seller action

Next buyer action: action, owner, and date

Known risk: the condition most likely to break the closing path

Source: meeting note, email, call moment, or document supporting the claim

Last confirmed: the date the buyer last confirmed consequential information

Category history: old value, new value, date, changed by, and reason

Keep the record in the opportunity. A forecast explanation stored in a separate deck becomes another version the team has to reconcile.

Quick answers

What are sales forecast categories?

Sales forecast categories group opportunities by their expected outcome in a forecast period. Common categories are Pipeline, Best Case, Commit, Omitted, and Closed. The exact names matter less than the evidence your team requires for each one.

What is the difference between sales stage and forecast category?

Stage tracks progress through the sales process. Forecast category expresses the current claim about whether the opportunity will close in the period. Deals at the same stage can carry different categories because their buyer timing and remaining conditions differ.

What is the difference between Best Case and Commit?

Best Case means the opportunity could close if named conditions are resolved. Commit means the seller expects it to close and can show a buyer-owned date, the remaining purchase path, responsible owners, and known risks.

Should forecast category update automatically from stage?

Use stage mapping as a default, not as the final decision. The opportunity owner should be able to adjust the category when buyer evidence differs from the stage default. Ask for a reason when a deal enters or leaves Commit.

How often should a forecast category change?

Change it whenever new buyer evidence changes the claim for the period. Review newly committed deals, slips, near-term Best Case conditions, and stale evidence each week. Do not wait for the forecast meeting to make a change everybody already knows is necessary.

Research note: This article draws on current forecast-category and operating guidance from Salesforce Help, the Salesforce Pipeline Forecasting guide, Clari, and Gong. LogicNotes added the buyer-owned-date test, category-reason history, inspectable-entry table, and CRM record.