A sales director reviews the Dynamics 365 Sales AI-generated predicted forecast for a business unit and finds it does not match the sum of opportunities the team has manually marked as Committed. The predicted total is higher and shifts week to week even when no committed opportunities changed stage. A consultant is asked to explain the discrepancy. What is the correct explanation?
Select an answer to reveal the explanation.
Short Explanation
These two numbers are answering different questions, so it makes sense they do not match. The Committed total is basically a seller's promise about a hand-picked set of deals, updated only when someone consciously changes that tag. The predicted figure is the model constantly re-weighing the entire open pipeline based on how likely each deal is to close and for how much, so it drifts week to week even if nobody touched the committed deals at all. That drift is not a bug or a stale cache catching up, and it is not one number being frozen while the other is somehow the only trustworthy one; both are live, they just measure different things. The useful mental model is a weather forecast versus a signed contract: the contract does not move once signed, but the forecast keeps updating as conditions change, and comparing the two directly will always look inconsistent even when both are working exactly as intended.
Full Explanation
The correct answer is D. The AI-generated predicted forecast is calculated by applying win-probability weighting across the full set of open opportunities in the pipeline, not just the subset a seller has manually tagged as Committed. Because any open opportunity's estimated revenue or predicted likelihood can shift week to week as new activity, engagement, or data comes in, the aggregate predicted figure moves even when the Committed-tagged opportunities themselves are untouched. This is expected behavior reflecting two different, complementary views of the pipeline: a seller-driven category and a model-driven probability estimate. Option A is incorrect because the predicted forecast updates continuously as underlying opportunity data changes, not on a fixed quarterly cache cycle. Option B is incorrect because the Committed category is a seller-managed field that can be updated at any time; it is not frozen at record creation. Option C is incorrect because closed-won opportunities are excluded from open-pipeline predictions once closed, and there is no manual purge step required to remove them from the current forecast calculation.