The forecast call and the pipeline review answer different questions on different horizons. The forecast call asks what closes in the current period and what proves it. The pipeline review asks whether the pipeline being built and maintained will support the periods that follow. Teams that collapse them into one meeting almost always sacrifice the second, because deals closing this month shout louder than deals that do not exist yet.
What each meeting owns
| Dimension | Forecast call | Pipeline review |
|---|---|---|
| Horizon | Current period | Next two to four quarters |
| Unit of analysis | Named deals with in-period close dates | Segments, sources, stages, and cohorts |
| Core decision | Commit, best case, or omit | Where to invest creation effort and what to remove |
| Typical cadence | Weekly | Weekly for creation, monthly for full book |
| Output | A number leadership will defend | A coverage and quality plan |
Why merging them costs you both
Current period pressure crowds out everything else. Once a call opens with the commit list, the remaining agenda becomes negotiation over three deals, and nobody returns to whether the third quarter has enough qualified pipeline to be worth forecasting at all.
The data each meeting needs is also different. The forecast call runs on deal-level evidence, and the sharpest input is close date movement. ORM's analysis of customer data identifies a rep changing the close date as the strongest deal slippage signal, with a deal that slips from one quarter to the next becoming less likely to close even while it sits in commit. That is a deal-level fact. The pipeline review runs on aggregate facts instead, including how much of the book has gone untouched. Across ORM's customer base, more than 10% of pipeline typically has not been touched in 12 months.
How to sequence them without doubling meeting load
Keep the forecast call to deals dated in the period and hold a hard line on evidence. Keep the pipeline review focused on creation, aging, and mix, and judge coverage on composition rather than a single multiple. A book at 3.5x coverage concentrated in aged deals or the wrong segment is weaker than a thinner book with live buying processes behind it, which is the argument in why the 3x pipeline coverage rule is wrong.
If calendar time is genuinely scarce, shorten the forecast call by requiring written submissions before it starts, and use the time you recover for the review of pipeline coverage quality. The forecast call protects this quarter. The pipeline review protects the ones you have not started yet.
For the full walkthrough, see the deep dive on this topic.
Frequently Asked Questions
What is the difference between a forecast call and a pipeline review?
Time horizon and unit of analysis. The forecast call looks at named deals with close dates inside the current period and decides which category each one belongs in. The pipeline review looks at the whole book, including deals dated well beyond this quarter, and decides whether creation and quality support future targets.
Can you run both in one meeting?
You can, and most teams that try end up doing the forecast call properly and the pipeline review badly. Current quarter deals are urgent, so they consume the clock. Future quarter health is important and never urgent, which is why it needs a protected slot of its own.
Which meeting comes first in the week?
Run the forecast call first while the deal detail is fresh, then the pipeline review with leadership later in the week. The forecast call surfaces which deals slipped out of the period, and slipped deals are an input to the coverage picture the pipeline review has to judge.
Who attends each one?
Forecast calls stay small, usually the rep and their direct manager, with a leadership roll-up separately. Pipeline reviews need sales leadership plus marketing and RevOps, because the levers that fix a creation gap sit outside the sales team.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like forecast call vs pipeline review into prescriptive action for your team.
Schedule a Demo