Stage describes where a deal is in the sales process. Forecast category describes how likely the rep thinks it is to close this quarter. The two answer different questions and both are needed to build an honest forecast.
A sales forecast category is a confidence label applied to each open deal that controls how it rolls up into the forecast. The five standard categories are Pipeline, Best Case, Commit, Closed, and Omitted. Reps set the category based on judgment, managers can override it, and the number for the quarter is built by summing deals in each category. The category lives alongside the deal stage, not instead of it.
The five standard categories, what each one commits the rep to, and the one rule that keeps the forecast honest.
A forecast category is a single field on each open deal with values like Pipeline, Best Case, Commit, Closed, and Omitted. It tells the forecast roll-up which bucket to put the deal in. Stage tells you where the deal is in the sales motion. Category tells you how confident the rep is that it closes this quarter.
The rep sets the category each week because they have the real customer context. The manager can override it in the forecast call when they see a deal the rep is being too optimistic or too conservative about. The override is tracked separately so leadership can see which reps run hot and which run cold.
A deal can be in late-stage Negotiation and still be Best Case if the champion just left. A deal can be in Qualification and already be Commit if the customer sent a signed PO ahead of procurement. Stage reflects the pipeline motion. Category reflects what the rep is willing to put their name on this quarter.
The quarterly forecast is built by summing deal amounts in each category. Commit plus Closed is the floor. Commit plus Best Case plus Closed is the ceiling. Pipeline is the universe of deals that could still fall into one of those buckets. Omitted is deliberately excluded so bad-fit deals do not pollute the number.
Reps review their open deals every Monday, set categories, and submit a forecast number. The number is locked for the week so the Friday pipeline review has a stable baseline. The next Monday the cycle repeats. Over a quarter the trend shows whether the forecast is firming up or sliding, which is the signal leadership watches.
A healthy forecast tracks each rep's Commit accuracy over time. Reps who commit $100k and close $95k are trusted. Reps who commit $100k and close $60k get coached. The category is a prediction market inside the company, and the only way it works is if the history is kept and reviewed, not reset each quarter.
Every forecasting CRM ships with roughly the same five categories, though the names differ a little by vendor. The definitions below are the common ones. The rule to carry across all of them: a category is a statement about confidence this quarter, not about how important the deal is or how far along it is in the sales process.
The deal is real and the rep is working it, but the close date and the outcome are still soft. Early-stage deals, deals with multiple unknowns, deals waiting on a decision from the customer. Pipeline deals count toward coverage ratios but not toward the forecast commit. Most open deals live here most of the time.
The deal could close this quarter if the stars align. Champion is engaged, pricing is in the ballpark, procurement is tracking, but a few things still need to go the rep's way. Best Case is the stretch band. Leadership adds it to Commit to see the ceiling of a reasonable quarter, not the floor.
The rep is willing to say "this closes this quarter." Everything the rep controls is in place: the champion, the budget, the signatures routed, the procurement timeline. If a Commit deal slips, the rep owns the miss and the manager will ask why. This is the number the forecast is actually built on.
The deal is signed and booked this quarter. Closed-Won flows into revenue, Closed-Lost drops out of the forecast. Some CRMs split this into Closed-Won and Closed-Lost as separate categories, others treat it as one. Either way, these deals are off the open board and into the ledger.
The deal is in the CRM so activity still logs against it, but it is deliberately kept out of the forecast. Reasons include deals pushed to next quarter, deals with the wrong product, deals the rep is pursuing but does not expect to land. Omitted is honest hygiene, not hiding. It says "I see it, I just do not count it."
Commit plus Closed-Won is the floor the rep bets on. Commit plus Best Case plus Closed-Won is the aspirational ceiling. Pipeline shows what might graduate into those buckets by quarter end. Omitted is excluded entirely. Leadership looks at all three bands plus the gap between them to judge how firm the quarter is.
The single most common mistake in forecast design is making the category a function of the stage. "If the deal is in Proposal, set it to Best Case." That rule looks tidy and destroys the forecast, because a deal in Proposal with a dead champion is not Best Case and a deal in Qualification with a signed PO is not Pipeline. Stage and category answer different questions and must be set independently.
Stage reflects the sales motion: Qualification, Discovery, Proposal, Negotiation, Closed. It is a process marker that drives next-step logic, deal-desk routing, and conversion-rate reporting. Stage is relatively objective. A deal is in Proposal if the proposal has been sent. The rep does not get to vote on that.
Category reflects the rep's judgment about confidence and timing. It is informed by stage but not derived from it. A late-stage deal can be Best Case if the champion left. An early-stage deal can be Commit if the customer verbally agreed and procurement is a formality. Category is the human read on the data.
When stage and category disagree, there is a story worth hearing. A late-stage Pipeline deal signals something is stalling. An early-stage Commit deal signals an unusual catalyst. The forecast call is where managers probe those gaps. If category is just the stage in different clothes, that signal is gone.
Some teams try to automate category from stage: Proposal becomes Best Case, Negotiation becomes Commit. On paper it looks like discipline. In practice it eliminates the rep's judgment, hides the risky deals in late stages, and lets the manager pretend they have a forecast when they have a pipeline report with new labels. Avoid.
The one automation that is safe: when a deal moves to Closed-Won, flip the category to Closed-Won. When it moves to Closed-Lost, flip the category to Closed-Lost. Those stages are terminal and factual. Every other category transition belongs to the rep or the manager.
Across any quarter you should see Commit deals concentrated in late stages, Best Case spread across mid and late, and Pipeline weighted toward early. If every late-stage deal is Commit and every early-stage deal is Pipeline, the forecast is a stage report. If the categories move independently, the forecast is a judgment call.
A forecast category is only useful if it is reviewed on a cadence. One category set at the start of the quarter and left alone is a forgotten field, not a forecast. The weekly rhythm below is what every mature revenue team runs some version of, and it is where the category earns its place on the deal record.
Each rep walks their open deals and sets or confirms the category for the week. Deals that moved toward close go up a tier (Pipeline to Best Case, Best Case to Commit). Deals that slipped go down a tier or push to next quarter. New information about champions, procurement, and competitors drives the change.
The rep submits a forecast number for the quarter: Commit, Best Case, and the expected close. Submitting locks the number for the week so the Friday review has a stable baseline. The system records the submission with a timestamp so trend reporting can show whether a rep's number is firming up or sliding week over week.
Managers run 1-on-1s against the submitted forecast. Why is this Negotiation deal still Pipeline? Why is this Discovery deal Commit? The conversation is about the gap between stage and category, which is where the risk and the opportunity actually live. Overrides get applied in the manager's roll-up.
The team gathers to walk the Commit and Best Case lists. Each deal gets a current state and a next step. The roll-up to leadership happens Friday afternoon with the week's locked number. The number ships upward as the team's forecast, with manager overrides visible so leadership can see the human adjustments.
Chart Commit week over week across the quarter. A healthy curve starts low and climbs smoothly to the final number. A curve that spikes in the last two weeks is late-month shuffling: deals magically becoming Commit because the quarter is ending. That pattern is a signal that the earlier weeks were not honest.
The retrospective compares each rep's Commit to actual Closed-Won. Reps who committed $100k and closed $95k are reliable. Reps who committed $100k and closed $60k need coaching on judgment, not on effort. Over four quarters a trust score emerges and leadership knows whose number to add straight to the plan.
Most teams install the five categories, roll them out at a kickoff, and discover a quarter later that the forecast is still off by double digits. The problem is rarely the tool. It is one of the patterns below. Catch these early and the categories do the work they were designed for.
Already covered above, worth repeating because it is the most common failure mode. If Proposal always equals Best Case and Negotiation always equals Commit, you have renamed stage. The rep's judgment is gone and the forecast tracks pipeline velocity, not confidence.
Deals that lived in Best Case all quarter suddenly become Commit in the final two weeks. The quarter closes, the number lands, and nobody flags the manipulation. Over multiple quarters this is how a team loses credibility with the board. The weekly category history is the audit trail that catches it.
Reps keep every bad-fit deal in Pipeline because deleting feels like admitting defeat. The pipeline bloats, coverage ratios look great, and the forecast is noise. Omitted is the honest answer: the deal is real, it is not closing, I am keeping it visible for context. Teach reps to use it without penalty.
A manager sees a rep's Commit of $100k, decides it is really $75k, and reports $75k upward without telling the rep. The rep thinks they are on plan and gets sideswiped at quarter end. Overrides must be visible to the rep so the conversation happens before the quarter closes, not after.
If the CRM only shows the current category and not the history, there is no way to see the shuffling, the slips, or the week-over-week firming. The field becomes a point in time instead of a trend. Every mature forecast tool stores the full history so the retrospective can be done against the facts.
If reps commit $100k every quarter and close $60k with no consequence, Commit becomes aspirational. The category only works if there is accountability on the back end: the retro, the trust score, the coaching conversation. Without those, Commit is just a louder version of Best Case.
A forecast category is not a sticky note. It is a field with a specific set of behaviors in the CRM: visible on the deal, editable by the rep, overridable by the manager, auto-flipped on close, logged in history, and summed in the forecast report. The checklist below is what to look for when a CRM claims to support forecast categories.
A single picklist field with the five standard values plus any custom values the team wants (some teams split Closed into Closed-Won and Closed-Lost). The field is visible on the deal detail, editable inline on the pipeline board, and required before a deal is considered forecast-eligible.
A built-in forecast view that sums deal amounts per category, per owner, per team, per quarter. The three bands (Commit, Best Case, Pipeline) are the headline numbers. Omitted shows separately so leadership can see what the rep deliberately set aside. The report filters to the current quarter by default.
Managers can override a rep's category in the forecast view. The override is stored distinctly from the rep's submission so both are visible. The rep gets notified. The forecast number ships upward with the override applied, and the retro compares both numbers against the actual result.
When the rep submits a forecast for the week, the Commit number is frozen for that cycle. Mid-week changes to deal data are recorded but do not retroactively alter the submitted number. The lock creates the week-over-week trend that managers and leadership read to judge whether the forecast is firming or sliding.
Every category change is recorded with the old value, the new value, the user who made it, and the timestamp. The deal timeline shows the full category history alongside stage changes, so the retro can reconstruct exactly when a deal moved from Pipeline to Best Case to Commit and whether the moves tracked reality.
The one safe automation: when stage moves to Closed-Won, category flips to Closed-Won. When stage moves to Closed-Lost, category flips to Closed-Lost. No other automation touches category. The rep's judgment is the input everywhere else, which is the point of having the field in the first place.
Strkr ships forecast categories, weekly submit-and-lock, manager overrides with full history, and the pipeline board the Monday review runs on. One tool for the whole revenue motion. Published pricing. No add-on for forecasting.
A forecast category is a confidence label on each open sales deal. The five standard values are Pipeline (in flight, uncertain), Best Case (upside if things fall right), Commit (the rep stakes their credibility), Closed (already won or lost), and Omitted (visible but excluded from the forecast). The category tells the forecast report which bucket to put the deal in when it rolls up.
Stage describes where a deal is in the sales process (Qualification, Discovery, Proposal, Negotiation, Closed). Category describes how confident the rep is that it closes this quarter. The two are set independently. A late-stage deal can be Best Case if the champion left. An early-stage deal can be Commit if the customer verbally agreed. Treating one as a function of the other collapses them and defeats the purpose.
The rep sets the category each week because they have the real customer context. The manager can override the category in the forecast call when they see a deal the rep is being too optimistic or too conservative about. Both the rep submission and the manager override are stored distinctly so leadership can see where human judgment adjusted the raw number.
Commit means the rep is willing to say this deal closes this quarter. Everything the rep controls is in place: the champion is engaged, the budget is confirmed, the signatures are routed, procurement is tracking. If a Commit deal slips, the rep owns the miss and the manager asks why in the retro. Commit plus Closed-Won is the floor the forecast is built on.
Best Case means the deal could close this quarter if the stars align, but a few things still need to go the rep's way. Pricing could still move, procurement could stall, a competitor could re-enter. Best Case is the stretch band. Leadership adds it to Commit to see the ceiling of a reasonable quarter, not the floor.
Omitted keeps a deal visible in the CRM for activity and context while deliberately excluding it from the forecast number. It covers deals pushed to next quarter, deals the rep is pursuing but does not expect to land, and deals with the wrong product or scope. Omitted is the honest alternative to deleting the record or leaving it in Pipeline where it pollutes the coverage ratio.
Weekly. The common cadence is reps update categories Monday morning, submit a locked forecast Monday afternoon, managers probe gaps in mid-week 1-on-1s, the team runs a Friday pipeline review, and the roll-up ships to leadership Friday afternoon. The week-over-week trend in Commit is what reveals whether the quarter is firming up or sliding.
The five concepts are standard: Pipeline, Best Case, Commit, Closed, Omitted. The names and the exact behavior vary slightly by vendor. Salesforce uses this exact set as its default forecast categories. HubSpot and most modern CRMs use the same five with occasional renaming. If a CRM does not support a configurable forecast-category field with manager override and category history, the forecast layer is not finished.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
