Forecast Category Definitions Template: Commit, Best Case, Pipeline, Omitted

Why do forecast categories need written definitions?

Because without them, commit means a different thing in every region and the roll-up adds numbers that are not comparable. One manager treats commit as deals with a signed order form pending countersignature. Another treats it as deals they feel good about. Both submit a number labeled commit, and the CRO adds them together as though they measure the same thing.

The document below fixes that. It is one page, it lives where reps can find it, and it gets referenced during forecast calls by name. Governance sounds heavy for a page of definitions, but the alternative is a forecast where the largest source of error is vocabulary rather than market conditions.

What do the four categories mean?

Each category is defined by evidence a third party could verify, not by rep sentiment. Those four numbers are starting targets you set, not rates anyone observed across the market. Replace them with your own measured close rates after one period, then publish those alongside the definitions and measure against them every period after that. When commit closes at 72 percent, the problem is not that reps are optimistic. The problem is that the commit definition is not being enforced, and the number the business plans against is inflated by a predictable amount.

What evidence should commit require?

Four conditions, all of them, with no partial credit.

The economic buyer has engaged directly rather than through a champion relaying messages. The approval path is known, including procurement, security, and legal, with named owners for each step. The close date has been confirmed by the buyer, typically through a mutual plan, rather than assigned by the rep. The deal amount matches an issued quote at that value.

That last condition catches a common failure. Pipeline values are frequently higher than what deals actually sign for, and a pipeline carrying an average deal size of 80K that produces closed-won deals averaging 40K will miss its number even at healthy volume. Requiring the commit value to match an issued quote closes most of that gap before it reaches the forecast.

Write the four conditions on the page as a checklist. A rep should be able to answer yes or no to each one in under a minute.

How do categories relate to pipeline stage?

Stage describes the buyer's progress. Category describes the probability of closing in this period at this value. Keep them separate. Systems that auto-assign category from stage produce the error in the first row constantly. If your CRM enforces that mapping, break it. The two fields answer different questions, and collapsing them into one means the forecast inherits every stage hygiene problem in the pipeline.

Who can change a category, and how is that recorded?

Reps set the initial category, managers can move it in either direction with a written reason, and everything above that level is an explicit override rather than a record edit.

The failure mode here is silent adjustment. A director who applies a mental haircut of 15 percent on the way up has removed information from the forecast without telling anyone which deals it applies to. When the period closes, nobody can tell whether the haircut was right, so nobody learns anything.

Record adjustments as their own line: the amount, the deals it applies to, the reason, and the person who made it. After two quarters you will know which adjusters are consistently correct and which ones are adding noise. That record is also what lets you separate a forecasting problem from a coverage problem when a number misses.

How do you keep the definitions honest over time?

Measure the close rate of each category every period and publish the results by team. Definitions decay quietly. A team under pressure starts moving deals into commit that would have been best case a quarter ago, and no policy document prevents that on its own.

Watch the close date change count alongside the category. At ORM the rep changing a close date is the strongest single signal of deal slippage, and a deal that slips from one period to the next is less likely to close even when it remains in commit. A commit deal that has already been pushed twice should trigger a review of whether it still meets the four conditions, because usually one of them stopped being true and nobody updated the category.

Also worth watching: seasonality changes what a healthy commit ratio looks like. The third month of a quarter is typically stronger than the first two, and Q2 and Q4 usually run stronger than Q1 and Q3. Comparing this quarter's commit conversion against last quarter's without accounting for that pattern will send you chasing a problem that is not there.

What does the one-page document contain?

Four category definitions, the commit checklist, the change rules, and last period's actual close rate per category.

That last item is what makes reps take the page seriously. Definitions alone read as policy. Definitions next to the numbers they produced last quarter read as evidence. When the page says commit closed at 94 percent last period, everyone understands what the word is supposed to mean.

Review the page once a quarter, change it rarely, and date every version. A definitions document that changes every month makes historical comparison impossible and you lose the ability to say whether forecast accuracy is improving. For the surrounding practices that make these definitions stick, start with sales forecasting best practices.