What is a forecast call supposed to produce?
A forecast call produces one number, a written list of the deals behind it, and a decision about the gap between that number and the target. Anything else is a status meeting.The failure mode is familiar. A manager reads deal names off a screen, each rep confirms what is already in the CRM, and the call ends with the same number it started with. No one committed to an action, so nothing changes before the next call.
Design the meeting around three outputs. The submitted number for the period. The deals that support it, named and dated. The specific plays that close the gap if the number is short. If a segment of the call does not move one of those three forward, it belongs somewhere else.
Who should be in the room?
Frontline managers, their reps, and one RevOps analyst who owns the model output. Keep it under twelve people.Roles matter more than attendance. The rep calls each deal and defends the date. The manager owns the segment number and is accountable for it upward. RevOps brings the algorithmic forecast and the historical variance so the room has something to argue against. A sales forecast built only from rep judgment inherits every optimism bias in the team.
Executives should read the output, not attend. A CRO in the room changes what reps say about their own deals.
What does a 45-minute forecast call agenda look like?
Four blocks, each with a fixed owner and a required output.| Block | Minutes | Owner | Required output |
|---|---|---|---|
| Number vs. plan | 5 | RevOps | Gap to target in dollars, model call vs. rep call |
| Changes since last call | 10 | Manager | Every deal that moved date, stage, or amount |
| Commit inspection | 20 | Reps | Confirmed or downgraded call per deal |
| Gap plan | 10 | Manager | Named actions with owners and dates |
The changes block is the highest-value ten minutes in the meeting. Meaningful movement on a deal is a change in stage, close date, or amount. Everything else is noise, and a deal with none of those changes since last week is not progressing regardless of what the activity log says.
What questions expose a soft commit?
Ask for buyer-side evidence, not rep confidence. Confidence is not a signal. Evidence is.Use a fixed question set so reps prepare for it:
- What is the next scheduled meeting with the buyer, and who confirmed it? - Who signs, and have they been in a conversation with us directly? - What is the customer's internal deadline, and why does it exist? - What has to be true in procurement or legal before the close date holds? - What did the buyer do in the last seven days that we did not ask them to do?
The last question does most of the work. Inbound buyer motion is the cleanest indicator that a deal is real. The earliest warning that a deal is dead is the absence of any signal at all: no data changing, no notes, no replies to email, no returned calls. Silence reads as neutral in a CRM and is close to fatal in practice.
What do you do when a rep moves a close date?
Downgrade the deal and say so on the call. A close date change is the single best predictor of deal slippage available in your CRM.When a deal slips from one quarter into the next, it is less likely to close, and that holds even when the rep leaves it in commit. Treat the date change as new information about probability, not as a scheduling adjustment.
Make the rule explicit so it is not a negotiation every week:
| Event | Forecast treatment |
|---|---|
| Close date moves within the quarter | Stays in category, flagged for next call |
| Close date moves to next quarter | Drops out of commit automatically |
| Second date move on the same deal | Drops to pipeline, requires manager sign-off to return |
| No stage, date, or amount change in 30 days | Excluded from the committed number |
How does the forecast call connect to the rest of the quarter?
The call inspects the visible pipeline, and the visible pipeline is only part of the quarter. Coverage on day one tells you less than most teams assume.Across ORM's customer base, pipeline coverage ranges from 1.4x to 5x with most companies near 3.5x, and roughly 20 percent of the value carrying an in-quarter close date on day one actually closes inside that quarter. The other 80 percent either slips, shrinks, or dies. That means a large share of the quarter has to be created and closed inside the quarter, and none of it is on the forecast call agenda in week one.
So run a parallel view. Track carry-over deals in the weekly call, and track in-quarter created business in a separate line item with its own owner. Teams that only inspect what is already in the CRM are managing the smaller half of the number. The 3x pipeline coverage rule hides this by making a single ratio feel like an answer.
How often should you run it and when do you change the cadence?
Weekly during the quarter, twice weekly in the final three weeks, and never as the only forecast input.Month three of a quarter closes more business than months one and two, and Q2 and Q4 typically outperform Q1 and Q3. Your inspection intensity should follow that curve rather than staying flat across thirteen weeks.
The deeper fix is timing. Getting the number right in the last week of the quarter helps no one, because by then the quarter has already happened. The value of a forecast call is concentrated in weeks one through six, when there is still enough time to build or rescue the gap. Run the same rigor early that most teams save for the end, and pair the call with a model that updates as conditions change rather than a spreadsheet rebuilt by hand each Monday. Manual forecasts typically reach about 90 percent accuracy on new and expansion business and take heavy manual effort to produce, which stops working as conditions change.
Frequently Asked Questions
How long should a weekly forecast call be?
Forty-five minutes for a single sales team, and no more than sixty for a segment roll-up with multiple managers. If the call runs longer, the meeting is doing CRM data collection that should have happened before it started. Cut the deal list, not the time.
Who owns the number on a forecast call?
The frontline manager owns the segment commit and defends it. Reps own their individual deal calls. RevOps owns the model output and the variance history that the room compares those calls against. The VP or CRO decides what gets submitted upward.
Should the forecast call review every deal?
No. Review commit deals, best case deals above a value threshold, and any deal where the close date moved since the last call. Everything else is monitored by exception. Reviewing the full pipeline every week guarantees that the deals that matter get five minutes each.
What is the difference between a forecast call and a pipeline review?
A forecast call decides what number you will submit for the current period. A pipeline review assesses funnel health and coverage for future periods. Running them in the same hour means the current quarter always eats the time and the next quarter never gets built.
How do you stop reps from sandbagging on the forecast call?
Track called number against closed number by rep over several quarters and publish the variance. A rep who consistently lands 20 percent above their commit is managed differently from a rep who lands 20 percent below. Once the pattern is visible, the incentive to hide upside disappears.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo