Pipeline stage and forecast category are the two fields teams most often collapse into one. Stage describes where a deal sits in the sales process. Forecast category describes whether it is expected to close in the current period. A deal can be deep in negotiation and still belong outside this quarter's number, and only two independent fields can say that.
Two questions, two fields
Stage is a statement about the buyer's progress. It is set by evidence and governed by exit criteria, and it moves in one direction most of the time. Category is a statement about timing and confidence. It is set by judgment, it changes weekly, and it moves in both directions freely.
The clean division looks like this. Stage answers "how far has this gone." Category answers "does it land by the end of the period." Mixing them means losing the answer to one of the two questions.
Why automatic mapping destroys information
Deriving category from stage is common and it makes the category field redundant. Once every negotiation-stage deal is automatically commit, the field reports the stage under a second name, and the rep's read on timing has nowhere to live.
It also fails on both interesting cases. A signed-off deal waiting on a buyer's fiscal-year start sits in a late stage and does not land this period. A deal created three weeks into the quarter with an urgent, funded requirement sits in an early stage and does land. Manual categorization captures both. A mapping table captures neither.
The judgment layer is the point
Category exists to hold information the CRM cannot infer: what the champion said on Tuesday, whether legal is genuinely queued, whether the buyer's approver just changed jobs. That is the layer a sales forecasting process is supposed to extract from the field, and it disappears the moment the field is automated.
The tradeoff is that judgment needs calibration. Track commit accuracy by rep over several quarters. A rep whose commit lands 95% of the time and one whose commit lands 60% of the time are submitting the same word with different meanings, and the aggregate number is unreadable until you know which is which.
What the record shows about in-period deals
Treat the day-one view of the quarter skeptically. ORM finds that roughly 20% of the pipeline carrying in-quarter close dates on the first day of the quarter actually closes in that quarter, which leaves 80% of the value dated into the period unrealized inside it. Close date is an intention, and category is where the intention gets stress-tested.
Two habits follow. Re-categorize after every close-date change rather than at the end of the month, since the close-date edit is the strongest available signal of deal slippage. And report category and stage side by side in pipeline reviews, because the deals sitting in an unexpected combination of the two are where the misses come from, and finding them early is most of the work in forecast accuracy.
Frequently Asked Questions
What is the difference between forecast category and pipeline stage?
Stage answers where the deal is in the process. Forecast category answers whether it lands in this period. A late-stage deal with a close date next quarter belongs in a late stage and outside the current commit, and only two separate fields can express that.
Should forecast category be set automatically from stage?
No. Auto-mapping makes the category a restatement of the stage and deletes the rep judgment the category exists to capture. The mapping also breaks on the two cases that matter most: a late-stage deal that will not land this period, and an early-stage deal that will.
What are the standard forecast categories?
Commit, best case, pipeline, and omitted are the common set, with closed as the terminal value. Commit means the rep will personally stand behind the deal landing in the period. Best case means it lands if things go well. The definitions have to be written down, because the words carry different meanings across teams.
Why do commit deals still slip?
Because commit records a person's judgment at a point in time, and the conditions underneath it change. ORM finds that a deal slipping from one quarter to the next is less likely to close even when it sat in commit, so a slipped commit deserves harsher treatment than a fresh one of the same size.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like forecast category vs pipeline stage into prescriptive action for your team.
Schedule a Demo