// GuidesHow-to
Forecast categories explained (commit, best case, pipeline) and a 45-minute forecast call
Short answer
Forecast categories sort open deals by how sure you are they close in the period. Commit means you would put your name on it, best case means one named thing still has to go right, pipeline means real but too early to count, and omitted (not forecasted in HubSpot) means out of this period’s number. Salesforce ships Pipeline, Best Case, Commit, Omitted and Closed; HubSpot ships Not forecasted, Pipeline, Best case, Commit and Closed won; Salesforce sets the category from the stage, HubSpot does when “Automate forecast categories” is on, and it stays until someone changes it. The rep proposes from buyer-side evidence and you challenge, a committed deal silent for 14 days leaves commit, and the weekly call takes 45 minutes for eight reps because it covers only what changed.
What are forecast categories, and what does each one mean?
A forecast category is a confidence label on an open deal for one period, usually the quarter. The stage says where the deal is in your process; the category says whether it counts in this period’s number. Salesforce sets it from the stage through a mapping, and HubSpot does when its “Automate forecast categories” switch is on, so the label means nothing until your team agrees what evidence each one requires.
| Category | What it means | Evidence required | Who moves it |
|---|---|---|---|
| Commit | You would put your name on it closing in the period. It is in the number. | A buyer-side event behind the close date, the signer engaged, paper moving, buyer activity in the last 14 days. | The rep, with evidence. You can take it out. |
| Best case | It can close in the period; one named thing still has to go right. | A dated next step inside the period, a champion, an amount from a quote the buyer has seen. | The rep, once the missing thing is named. You, when a commit deal’s evidence lapses. |
| Pipeline | Real and qualified, too early to count in this period. | A qualified need, a contact who can buy, a plausible timeline. | The CRM, from the stage. Up only with evidence. |
| Omitted (Salesforce), Not forecasted (HubSpot) | Out of this period’s number: dated later, lost, or on hold. | None. The deal keeps its stage. | Either of you, the day the date leaves the period. |
| Closed (Salesforce), Closed won (HubSpot) | Won inside the period. Counted, not forecast. | A signed order. | The CRM, at closed won. |
Most likely is a fifth label some teams add between best case and commit, and both CRMs support it. Add it only if your forecast is reported at that level.
Tip
Two deals, two categories
Say a rep has a $60k deal dated June 27 in commit. The buyer’s legal team opened the MSA on Monday and their VP named the week of June 22 for signature. It stays in commit. Her $35k deal, also in commit, has had no reply since a demo 16 days ago; the last change on the record was the rep moving the date. It leaves commit until the buyer does something.
What are the forecast categories in Salesforce and HubSpot, and how does each set them?
Both CRMs can assign the category from the deal stage through a mapping your admin controls (in HubSpot, once “Automate forecast categories” is on), and both use nearly the same words. The differences are the name of the uncounted bucket and where a rep changes the category by hand.
| Meaning | Salesforce | HubSpot |
|---|---|---|
| In the number | Commit | Commit |
| Could close, one thing missing | Best Case | Best case |
| Real but early | Pipeline | Pipeline |
| Out of this period | Omitted | Not forecasted |
| How it is set | From the opportunity stage, through the stage-to-category mapping | From the deal stage, by a workflow, when “Automate forecast categories” is on |
| Changing it by hand | Depends on how your admin set up the Forecast Category field | Users, from the deal record |
| Where the forecast lives | The Forecasts page | The forecast tool, Professional or Enterprise tiers |
Salesforce’s help article puts it in one sentence: “The standard forecast categories are Pipeline, Best Case, Commit, Omitted (not included in forecasts), and Closed.” Admins can add Most Likely and rename the rest. Trailhead’s forecasting setup unit adds that “Each opportunity stage aligns to a forecast category,” through a default mapping on the Stage field that admins adjust.
HubSpot’s forecast setup article defines commit as “deals that have a high likelihood of closing and have been committed to the forecast,” and says users can update it by hand on the deal record. With “Automate forecast categories” on, HubSpot updates the property when a deal changes stage (HubSpot’s default deal properties). The forecast tool needs Sales Hub or Service Hub Professional or Enterprise.
Rollups are not categories. Salesforce can show each column on its own or cumulatively, where Commit includes closed deals too, so ask which one your Forecasts page shows. A manager’s adjustment there changes the forecast amount only; per the same Trailhead unit, adjustments “don’t change the underlying opportunity data.”
Who decides the category, and what does commit require?
The rep proposes, from evidence the buyer produced, and you challenge. The stage mapping is only a starting point; a deal that reaches negotiation lands in commit on its own, and that is where the label most often lies.
Three rules keep it honest. A category move needs a reason from the buyer’s side, in one sentence, logged on the deal. The rep can move a deal up; you can move one down, never up. And commit is scored. At quarter end, the share of each rep’s committed deals that closed is their commit accuracy.
Commit criteria: all of these, or it is best case
- A buyer-side event behind the close date. A signature slot, a budget meeting, a go-live they named. Quarter-end alone is a guess.
- The signer is engaged. The economic buyer has said yes, or the meeting where they will is booked inside the period.
- Paper is moving. Contract, security review or procurement has started, with a named owner on their side.
- The amount is a quote the buyer has seen, not the number from stage one.
- Buyer activity within 14 days. A reply, a meeting, or a change to stage, date or amount that came from them. ORM’s rule is that the rep shows buyer engagement before the next snapshot, or the deal leaves commit.
- More than one contact. Single-threaded can be best case. It is not commit.
- No open condition you do not control. Budget unapproved, legal not started, a procurement freeze.
What moves a deal down a category?
Write the down-moves as rules, so they happen between calls and nobody has to be the bad guy. Each names a trigger you can see in the CRM; adjust the thresholds to your data.
| Trigger | Move | Why |
|---|---|---|
| Close date pushed past the end of the period | Out of this period’s number; re-forecast in the next | Per ORM, a deal that has slipped a quarter closes less often, commit or not. |
| Close date pushed a second time inside the period | Commit to best case | The first date was a guess; the second is a guess with a history. |
| No buyer activity for 14 days on a committed deal | Commit to best case, unless the rep shows buyer engagement | Silence is the earliest warning, and nobody volunteers it. Run it off a report. |
| No logged activity past your stale threshold (7 days on a cycle under 30 days, 14 for 30 to 90, 21 for over 90) | Down one category | A rule of thumb, adjust to your data. |
| Champion left, or the signer changed | Down one category, then re-qualify | The evidence behind the category left with them. |
| The buyer says “not this quarter” in any form | Out of this period’s number the same day | A category is not a negotiating position. |
Watch out
The category is not the place to argue about the number
Moving a rep’s deal down quietly, or trimming the total in the room, leaves no trace of who was right. ORM’s prohibition: “No manager haircut applied in the room, because the adjustment becomes untraceable and rep-level accuracy scoring stops working.” Record your judgment as an adjustment in the forecast tool and keep the rep’s category on the deal.
The 45-minute weekly forecast call agenda
Forty-five minutes for a team of eight reps, whole team, deltas only. ORM Technologies’ guide sets both the length and the test: “If it runs longer, it has turned into a deal review.” The number is locked before the call, the call examines the snapshot, and unchanged deals get no airtime.
| Block | Minutes | What is said | Question |
|---|---|---|---|
| The locked number | 0–3 | You read the snapshot taken before the call: closed, commit, best case, gap to target. Nobody edits it in the room. | “Where does the number stand, and how big is the gap?” |
| Category, date and amount moves | 3–18 | Each rep, only the deals whose category, close date or amount changed since last week, with the buyer-side reason. Two minutes per rep. | “What did the buyer do or say that moved this?” |
| Silent commits | 18–28 | Your report of committed deals with no change to stage, date or amount in 14 days. Evidence of buyer engagement, or the deal leaves commit. | “What has the buyer done in the last two weeks?” |
| Upgrades | 28–35 | Best-case deals a rep wants to move up, read against the commit checklist, and what must happen by when. | “What would have to be true by Friday for this to be commit?” |
| The gap plan | 35–43 | Where the gap closes from: carry-over deals, deals created and closed inside the period, pull-forwards, with a name on each. | “Which deals close the gap, and who owns each one?” |
| Read-back | 43–45 | Moves recorded, owners and dates confirmed, deal reviews booked separately. | “What changed in the number today?” |
Call format adapted from ORM Technologies’ weekly forecast call guide. ORM’s own agenda runs four blocks (delta review, silent deals, an assumption check on win rate, deal size and cycle length, and a gap plan) with RevOps in the room. Without RevOps, the assumption check becomes a monthly look at three trend lines. The gap plan keeps ORM’s test: it names the deals that close the gap, and a bare dollar figure still to find does not count as a plan.
- No coaching in front of the group; strategy gets its own deal review.
- No editing the number live; in ORM’s format the snapshot is fixed before the call and only reviewed in it.
- No deals outside the period; next quarter’s belong in the pipeline review.
Three steps put it in place.
- Week 1. Agree the commit checklist, send the deltas checklist the day before, run the six blocks with the minutes visible.
- Week 2. Add the silent-commit report and the down-move rules. Expect commit to shrink; that is the label becoming true.
- Quarter end. Score each rep’s commit (committed deals that closed ÷ committed deals) next to your adjusted number.
What should reps prepare? The deltas checklist
Only the deltas. ORM’s answer to what reps prepare fits in one line: category moves, changed close dates with the reason, and committed deals with no buyer contact for a week. Send the checklist the day before.
Each rep, the day before
- Category moves since last week, each with the buyer-side reason in one sentence.
- Close dates that changed, with the buyer event behind the new date. No event, and the date is a guess.
- Amounts that changed, and what the new number is based on.
- Committed deals with no buyer contact in the last week, named before the report names them.
- Closed won and lost since last week, one line each.
- Upgrade candidates, best-case deals that meet the commit checklist.
You, the morning of the call
- Lock the snapshot: closed, commit, best case and the gap, per rep and for the team.
- Run the silent-commit report: committed deals with no change to stage, date or amount in 14 days.
- Pull the pushed dates: close dates moved since last week, and deals pushed twice this period (deal slippage has the recipe).
- Do the gap math: target minus closed minus commit, then the same with best case.
How diffi helps
diffi is not a forecast rollup. The categories, the submission and the number for the CRO live in Salesforce or HubSpot, and diffi does not write to either. It does the delta pre-read. It reads your CRM and turns changes into plain facts: a close date pushed or slipped into the next quarter, a stage regressed, an amount changed and, from Salesforce, a deal with no change for 21 days. Before the call, ask it what changed this week, or open the deal-risk signals; each answer shows its evidence and links to its sources. The 14-day silent-commit report, the category decision and the gap plan stay with you. Book a demo to see your own pipeline’s deltas before the next call.
See it on your own teamForecast call vs pipeline review: keep them apart
The forecast call is about this period’s number and what changed. The pipeline review is about whether the inventory behind future periods is real. Merge them and, as ORM warns, this period’s number takes the time and coverage never gets discussed. Run the pipeline review one rep at a time, 30 minutes, with its own pre-read, and set coverage for later periods there with your own ratio rather than 3x.
Frequently asked questions
What is the difference between commit and best case in a sales forecast?
Commit is a deal you would put your name on closing inside the period, with the signer engaged, a buyer-side event behind the close date, paper moving and buyer activity in the last 14 days. Best case is a deal that can close in the period with one named thing still to go right. If the rep cannot name the thing, the deal is pipeline.
What are the forecast categories in Salesforce?
Pipeline, Best Case, Commit, Omitted (not included in forecasts) and Closed, per Salesforce’s help article. Admins can add a Most Likely category and rename the others. Each opportunity stage maps to a category, so the category changes with the stage unless someone changes it by hand or the mapping is adjusted.
What are the forecast categories in HubSpot?
Not forecasted, Pipeline, Best case, Commit and Closed won, set from the deal stage when “Automate forecast categories” is on and editable on the deal record (HubSpot’s forecast setup article). The forecast tool needs Sales Hub or Service Hub Professional or Enterprise.
Who decides a deal’s forecast category, the rep or the manager?
The rep proposes it from evidence the buyer produced, and the manager challenges it. The manager can take a deal out of commit and should never put one in. A manager who disagrees with the total records an adjustment in the forecast tool rather than editing the rep’s categories, so the two can be compared at quarter end.
How long should a weekly forecast call be?
Forty-five minutes for a team of eight reps, per ORM Technologies, and only if it covers deltas: deals whose category, close date or amount changed, committed deals with no buyer activity, upgrades and the gap plan. If it runs longer, it has become a deal review, which belongs in a separate meeting.
What should reps prepare before the forecast call?
Only the deltas. Category moves with the buyer-side reason, close dates that changed and the buyer event behind each, amounts that changed, committed deals with no buyer contact in the last week, and the best-case deals they want to move up with the evidence. Nothing on unchanged deals.
What is the difference between a forecast call and a pipeline review?
The forecast call is about the number for this period and what changed since last week, with the whole team and deltas only. The pipeline review is about whether the inventory behind future periods is real, one rep at a time, with its own pre-read. Combining them lets this period’s number take the time and pushes coverage off the agenda.