A forecast call question is a standard prompt a manager uses to test whether a deal has earned its forecast category. The purpose is to replace rep narrative with evidence. Every deal in the commit either survives the questions or drops a category before the call ends.
Questions That Test the Close Date
Start with where the date came from. A date the rep picked to satisfy a required field is a guess. A date the buyer confirmed against a procurement step or a budget cycle is a fact.
- Where did this close date come from, and has the buyer confirmed it? - What has to happen between today and that date, and who owns each step? - How many times has this date already moved?
ORM's data points to close-date changes as the strongest slippage signal on a deal. Once a deal slips from one quarter into the next, it becomes less likely to close even while it sits in commit. Count date changes per opportunity and treat the second one as an automatic demotion. See deal slippage for the underlying pattern.
Questions That Test the Amount
The amount field is the second place forecasts break. ORM finds that most deals close for less than the amount carried in the CRM. Take a pipeline averaging $80,000 per deal in average deal size against closed-won deals averaging $40,000. In that case half the forecast evaporates at signature.
- What discount does the buyer expect, and who has approved it? - Which line items has procurement already cut? - Is this number the full contract value or first-year revenue?
Questions That Test Buyer Engagement
The earliest warning on a deal is silence. ORM treats the absence of a signal as the first sign of trouble: no stage change, no amount change, no close-date change, no replies to email. A deal that looks stable because nothing has moved is not stable. It is stalled.
- When did the buyer last respond, and to whom? - Who else in the account has engaged since the last call? - What did the buyer ask us for most recently?
What to Do With the Answers
Answers mean nothing without consequences. Close the call with two lists. One holds every deal that changed category. The other holds every deal where the rep needs something from leadership by a named date.
Then measure. Compare each rep's commit against what actually closed and you get a personal conversion rate that makes the next call shorter and the number more defensible. Forecast accuracy by rep tells you whose answers to trust. For the standards that sit around the call itself, see sales forecasting best practices.
Frequently Asked Questions
What questions should a manager ask on a forecast call?
Ask where the close date came from, what has to happen before it, how many times it has moved, what the buyer will actually sign for, and when the buyer last responded. Every question should have a verifiable answer that lives outside the rep's head.
How do you tell whether a commit deal is real?
A real commit deal has a close date the buyer confirmed against a procurement or budget step, an amount that matches what the buyer has agreed to pay, and recent two-way contact with the buying group. Missing any of those, the deal belongs in best case.
Should reps answer forecast questions before the call?
Yes. Written answers submitted before the call turn the meeting into a decision forum instead of a data-gathering session. Managers arrive knowing which deals need pressure, and call time drops sharply.
How many questions should you ask per deal?
Three to five, applied identically to every deal. A fixed question set makes answers comparable across reps and lets you spot the deals where the story changes week to week.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like forecast call questions into prescriptive action for your team.
Schedule a Demo