A deal review works one deal down to its next buyer conversation. A pipeline review looks across one rep's book and picks the deals that need that work. A forecast call takes the result for the whole team and commits to a number.
All three involve deals, dates and the same CRM screen, which is why teams blur them. Each answers a different question, and the meetings only produce an honest forecast when they run in order. This piece sits inside our guide to deal coaching, which covers the deal review layer in depth.
The difference in one paragraph
The forecast call is about the number, the pipeline review is about the book, and the deal review is about the buyer. Only the deal review talks about what a specific person at the buyer has said and done. The other two meetings rely on that evidence and cannot produce it themselves. When a team skips the deal review, the pipeline review ranks the reps' opinions and the forecast call commits to them.
The three meetings compared
| Deal review | Pipeline review | Forecast call | |
|---|---|---|---|
| Scope | One deal | One rep's whole book | A team, region or company |
| Typical cadence | Weekly, per rep, one or two deals | Weekly or every other week, per rep | Weekly in-quarter |
| Who attends | Manager and rep | Manager and rep | Frontline managers up to sales leadership, often RevOps |
| Who talks most | The rep | The manager asks, the rep answers | Managers report up |
| Main input | Buyer evidence: quotes, emails, calendar entries | CRM stages, amounts, close dates, last activity | Roll-ups of pipeline by category (commit, best case) |
| Question it answers | What is this deal missing, and what is the next conversation? | Is there enough, is it real, where is it stuck? | What do we commit to this period? |
| Output | A planned buyer conversation with a date | A shortlist of deals that need a deal review | A number, with the swing deals named |
| Failure mode | Turns into a status update | Turns into a deal-by-deal recap | Turns into a debate about definitions |
A few notes on the table. The cadence row describes common practice and varies by team. RevOps attendance at the forecast call is common in larger organizations. The output row is the test. If a meeting ends without its output, it did not do its job, however long it ran.
The step-by-step formats are in how to run a deal review and the pipeline review template.
How the three meetings feed each other
The three meetings form a chain. Evidence goes up and attention comes down.
- 01Deal reviewOutput: the next buyer conversation
- 02Pipeline reviewOutput: the shortlist
- 03Forecast callOutput: the number
| Meeting | What it produces | Sends up | Sends down |
|---|---|---|---|
| Forecast call | The number | The swing deals that decide the quarter | |
| Pipeline review | The shortlist | Whether the book is real | Which deals need a deal review this week |
| Deal review | The next buyer conversation | Each deal's real stage, from what the buyer has done |
Going up: the deal review establishes each deal's real stage from what the buyer has done. The pipeline review uses those stages to judge whether the book is real. The forecast call commits to a number built from deals whose stage was checked.
Going down: the forecast call names the swing deals that decide the quarter. The pipeline review makes sure each swing deal gets a deal review this week. The deal review plans the conversation that moves it.
Commit means different things to a frontline manager, a regional VP and a CRO. Shared definitions help only if someone checks each deal against them, and that check is the deal review. "Commit" should mean a dated step sits on the buyer's calendar that only makes sense if they are buying, and the deal review is where a manager asks to see it.
This is why the forecast's accuracy is set two meetings before the forecast call. Teams trying to fix a forecast usually start at the call itself, with new categories or a new roll-up. The faster fix sits lower down: a deal review every week on each deal in commit, against a commit definition that the deal review checks. Our forecast accuracy guide covers how to write those definitions.
Where each meeting goes wrong
The deal review becomes a status update. Symptom: the rep reads the CRM aloud, the manager asks about the close date, and the meeting ends with "keep pushing". Fix: the rep tells the deal from the buyer's side, the manager asks for evidence behind each claim, and the meeting ends with the opening line of the next conversation.
The pipeline review becomes a recap. Symptom: the manager walks every deal in order and spends four minutes on each. The deals that need work get the same four minutes as the ones that do not. Fix: before the meeting, read each deal's stage as its last deal review set it, then spend the time only on deals where the CRM stage runs ahead of that evidence.
The forecast call becomes a definitions debate. Symptom: two managers argue about whether a deal belongs in commit. Fix: the argument belongs in the deal review that should have happened earlier in the week. If the deal has not had one, it goes in best case until it does.
The team runs one meeting for all three jobs. Symptom: a weekly hour where the manager collects the number, walks every deal and tries to coach one. None of the three outputs comes out of it. Fix: separate them, even if the deal review and pipeline review happen back to back with the same rep.
Questions for each meeting
Each meeting has its own questions. A pipeline review that asks deal review questions runs over time and never reaches the bottom of the book.
Deal review, one deal:
- What did the buyer say, in their words, and on what date?
- Who signs, and have they heard the cost of the problem?
- What is the next conversation, with whom, and what is the opening line?
Pipeline review, one rep's book:
- Is there enough pipeline to reach the number at the rep's usual win rate?
- Which deals have sat in one stage longer than your typical deal does?
- Where does the CRM stage run ahead of the buyer evidence?
- Which one or two deals get a deal review this week?
Forecast call, the team:
- Does every deal in commit meet the commit definition?
- Which swing deals decide the period, and when is each one's next buyer conversation?
- What moved since last week, and what caused the move?
The pipeline review questions get skipped most often. Coverage, time in stage and the gap between stage and evidence are what tell a manager which deals to pull into a deal review. More are in our list of questions to ask in a pipeline review.
One deal through all three meetings (illustrative)
The account, people and numbers are fictional. The week starts with the pipeline review because that is where a deal gets picked; the deal review then works it, and its result feeds the forecast call.
Monday, pipeline review. Dana's book has nine open deals, each with a stage her earlier deal reviews set from buyer evidence. The manager reads those stages against the CRM. Fenmore Supply, $60,000, sits in Commit in the CRM. Its last deal review recorded that the buyer has put a number on the problem and agreed the criteria, but nobody who signs has spoken to Dana. The CRM stage runs ahead of that evidence, so Fenmore goes on the shortlist.
Tuesday, deal review. Dana tells the deal. The gap: Fenmore's Finance Director has never heard the business case. The next conversation is with the champion, Ruth, asking to prepare the Finance Director meeting together. Dana says the opening line out loud: "Ruth, you said late shipments cost you about $8,000 a month. Before this reaches Finance, can we make sure that number is the one they hear?" Date: Wednesday.
Thursday, forecast call. The manager moves Fenmore from commit to best case and says why: no signer engagement yet, a meeting is being requested. The team's number drops by $60,000 and becomes more believable. Next week's forecast call asks whether the Finance meeting happened.
The deal itself stood still all week. By the forecast call, every meeting above the deal review reflected what the buyer had done.
Running the deal review layer for every rep
The pipeline review and the forecast call scale reasonably well; they are one meeting each, with good data. The deal review is the layer that does not scale, because it needs a manager's full attention on one deal at a time, and the manager's coaching skill matters too (Dahling et al. 2016).
Our AI sales experts take that layer. In the Fenmore week, Dana could have talked the deal through with Caty on a call before Tuesday's review; she checks it against the team's method, names what the buyer evidence is missing and plans the next conversation. Every rep can bring a deal that way, in the team's methodology, and type it when they cannot talk.
For the manager, Bryce gives a Monday read of the team: which deals need attention this week and which carry buyer evidence. The pipeline review's shortlist can start there, and he coaches the manager on the 1:1 and the forecast call too. See how deal execution works or talk to us about running it across a team.
FAQ
What is the difference between a deal review and a pipeline review?
A deal review works one deal down to its next buyer conversation; a pipeline review looks across one rep's whole book to decide which deals need that work. The deal review asks what the buyer has said and done. The pipeline review asks whether there is enough pipeline, whether it is real and where it is stuck.
What is the difference between a pipeline review and a forecast call?
A pipeline review is a manager and one rep checking that rep's book. A forecast call is managers and sales leadership committing to a number for the team. The pipeline review picks which deals need a deal review; the forecast call adds up the checked deals and names the ones that will decide the period.
Should deal reviews and pipeline reviews be separate meetings?
Yes, even if they happen back to back with the same rep. A pipeline review needs to move quickly across the book and a deal review needs depth on one deal. Combining them usually means every deal gets four minutes and none gets a planned next conversation.
How often should each meeting happen?
Most teams run a weekly deal review per rep on one or two deals, a weekly or every-other-week pipeline review per rep, and a weekly forecast call during the quarter. Cadence varies by team. The order matters more: that the deal reviews happen before the forecast call each week.
Who should attend a forecast call?
A forecast call usually brings together frontline managers, their sales leaders and often RevOps, who prepare the numbers and the definitions. Reps rarely attend. Their input comes through the pipeline reviews and deal reviews earlier in the week, which is why those meetings decide how honest the forecast is.