Forecast category
Concept
A forecast category is a label on a Dynamics 365 Sales opportunity (pipeline, best case, committed, omitted, won or lost) that decides which forecast column includes its amount and signals confidence.
Description
A forecast category is a label on an opportunity in Dynamics 365 Sales that expresses how confident the seller is that the deal will close. It also decides which column of the forecast grid includes the opportunity's amount, so the forecast can reflect the real state of the pipeline. The available values are pipeline, best case, committed, omitted, won and lost.
Each value has a defined meaning. Pipeline is the default and marks early or stalled deals. Best case marks deals that are progressing, for example when proposals have been sent, but where no commitment exists yet. Committed marks deals where the customer has given a verbal or contractual commitment. Omitted removes an opportunity from all forecast totals. Won and lost are set automatically when an opportunity is closed. According to the documentation, these two values should not be picked by hand, because doing so can make the opportunity vanish from the forecast or distort rolled-up values.
In daily use, the field is changed on the opportunity form. Sellers adjust the category as the customer situation develops, for instance moving a deal from pipeline to best case once a proposal is out, and to committed once a commitment is given. Because managers in the hierarchy see totals that include these choices, the category affects how the forecast is rolled up across a team. The documentation notes that the feature must be enabled by an administrator, and the described steps apply to the standard Sales Hub and Sales Professional apps.
The label matters because forecasting depends on the quality of the underlying sales data. The episode "Dynamics 365 Forecasting - Simply Explained" says that even sophisticated forecasting technology cannot compensate for inaccurate sales data. It names an outdated close date, incorrect expected revenue and an unrealistic forecast category as examples of errors that can flow directly into the forecast. The episode recommends that sellers keep opportunity amounts, expected close dates, ownership and forecast categories current whenever the customer situation changes, and summarizes the point as: accurate forecasting starts with accurate opportunity management.
The same episode also stresses that human judgment still matters. Sales data cannot capture every detail of a customer relationship, so the category a seller chooses is a judgment about confidence rather than an automatic calculation. In practice, this means the forecast category is only as reliable as the discipline applied to updating it, and a forecast built from stale or optimistic categories will mislead the managers who rely on the rolled-up totals.
Typical decisions around the forecast category include when to promote a deal from pipeline to best case or committed, and when to use omitted to keep an opportunity out of the totals entirely. Choosing omitted is different from closing the deal: it removes the opportunity from forecast totals while it remains an open record. Closing the opportunity as won or lost is the route that sets those categories correctly, which avoids the distortions described for manual selection.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What are the forecast category values in Dynamics 365 Sales? (AI)
The values are pipeline, best case, committed, omitted, won and lost. Pipeline is the default, and won and lost are set automatically when an opportunity is closed.
What does the omitted forecast category do? (AI)
Omitted removes an opportunity from all forecast totals. It is used to keep a deal out of the forecast without closing it.
Should won or lost be selected manually as a forecast category? (AI)
No. The documentation says won and lost are set automatically on closing and should not be picked by hand, since doing so can make the opportunity vanish from the forecast or distort rolled-up values.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: