A pipeline review meeting is a weekly team session, usually 45 minutes, in which a sales manager and their reps check whether the pipeline is real and pick the deals that need work this week. The frontline manager runs it. Done well, it ends with a shortlist of deals and a planned buyer conversation for each one.
This is the team version. For reviewing one rep's book on one page, use the pipeline review template. Both sit inside our guide to deal coaching.
The job of the meeting
The pipeline review has two outputs: an honest picture of the book and a short list of deals that need a deal review this week. Individual deals get fixed in the deal review that follows.
- Minutes 0 to 5The number and coverage
- CRM stage next to evidence stage
- Minutes 5 to 18What moved, and last week
- Buyer actions only
- Did the planned conversations happen?
- Minutes 18 to 23The disagreements
- CRM stage ahead of evidence
- Minutes 23 to 38One deal in depth
- Two reps, one deal each
- Minutes 38 to 45Shortlist and commitments
- Two deals per rep for a deal review
- Planned conversations read back
The usual failure is the recap. Each rep recites their deals, next steps and forecast, the hour ends, and nobody can say what changed. Gong's guide to pipeline reviews describes the same meeting, where the manager has "no idea if they got anything out of the last hour". The fix is to move the recap out of the meeting entirely, which is what the prep rule below does.
Before the meeting: the prep rule
Every rep stages their open deals by buyer evidence before the meeting, in a shared sheet, and marks each deal where the CRM stage and the evidence disagree. The meeting starts from the sheet and nobody reads their deals aloud.
Buyer evidence means something the buyer said or did that the rep can point to. The ladder we use: the buyer described the problem in their own words; a named person put a number on it; the buyer said which of their criteria the solution meets; the signer has been on a call; the buyer walked the rep through approval steps; a dated buyer step is on the calendar. The first rung without evidence is the real stage. Fifteen minutes of prep per rep is typical once the habit is set.
The 45-minute pipeline review, step by step
Step 1. The number and coverage (minutes 0 to 5)
Manager says: where the team stands against target, what is closed, and the pipeline by evidence stage, next to the CRM stage. One slide or one screen.
Good looks like: the team hears the gap between CRM-stage pipeline and evidence-stage pipeline. That gap is the meeting's agenda.
Step 2. What moved (minutes 5 to 13)
Manager says: "Only deals where the buyer did something this week. One sentence each: the deal, and what the buyer did."
Good looks like: "Harrowby: the operations lead joined Tuesday's call and asked for references." A sentence about what the rep did ("I sent a follow-up") does not count.
Step 3. Last week's planned conversations (minutes 13 to 18)
Manager says: "Last week we planned these conversations. Did each one happen, and what did the buyer say?"
Good looks like: most happened, and the ones that did not have a reason and a new date. A team that skips this step learns that plans are optional.
Step 4. The disagreements (minutes 18 to 23)
Manager says: "These deals have a CRM stage ahead of their evidence stage. For each, is the CRM wrong, or is evidence missing from the sheet?"
Good looks like: some deals move back a stage in the CRM on the spot, with a note on why. Others gain evidence the rep had forgotten to record.
Step 5. One deal in depth (minutes 23 to 38)
Working one real deal teaches more than talking about the pipeline in general. With a full team there is not time for one deal per rep every week, so rotate: two reps each week bring one deal for seven minutes each.
Manager says: "Tell us the deal from the buyer's side. Team, ask only questions the buyer's words or actions can answer."
Good looks like: the team finds the gap, and the rep leaves with the opening line of the next buyer conversation, said out loud in the room. Other reps hear how a peer's deal was staged, which often teaches them something for their own deals.
Step 6. The shortlist (minutes 38 to 42)
Manager says: "These are the deals that get a one-on-one deal review this week."
Do: pick the deals where a conversation this week changes the outcome, and only as many as the manager has review time for this week. Count the slots before the meeting; two per rep is common. Deals waiting on a buyer date months away get a check-in date instead.
Good looks like: every rep knows which of their deals will be reviewed and when.
Step 7. Commitments (minutes 42 to 45)
Manager says: "Read back the conversations you are planning this week, with dates."
Good looks like: a list in the shared sheet that Step 3 will read next week.
A worked example (illustrative)
The team, accounts and figures are fictional.
A manager runs a six-rep team with a $1.2M quarterly target. Monday, 9:00.
Step 1. Closed: $410,000. Commit in the CRM: $520,000. Commit by evidence (a dated buyer step on the calendar): $260,000. The gap of $260,000 is the morning's real subject.
Step 2. Four deals moved. Jo: "Tolvern, procurement sent their vendor form." Sam: "Brightwell, Anita in Finance asked for the one-page summary." Two reps report activity of their own and get asked what the buyer did; neither had a buyer action.
Step 3. Of last week's seven planned conversations, five happened. Kai's call with the Kelderby COO was moved by the buyer; new date Thursday. Priya did not call Callowfield's maintenance lead; she will today.
Step 4. Three deals sit in Commit with no dated buyer step. Two, worth $140,000 between them, move to Best Case, so CRM commit drops to $380,000. The third has a signed pilot schedule the rep had not added to the sheet; it stays.
Step 5. This week's two reps are Jo and Tomas. Tomas brings Eskdown: CRM Commit, evidence one rung lower because nobody who signs has spoken to him. The team asks who signs, what the champion said the problem costs and whether the champion has a reason to bring Finance in. Tomas leaves with an opening line for the champion: "Ruth, you said late shipments cost about $8,000 a month. Before this reaches Finance, can we make sure that is the number they hear?"
Step 6. The manager has blocked twelve review slots this week, so twelve deals go on the shortlist, two per rep, each with a time.
Step 7. Nine planned conversations are read back with dates.
Forty-five minutes, and CRM commit has gone from $520,000 to $380,000, much closer to the $260,000 the evidence supports. The forecast call that afternoon will be shorter.
Adjusting the format to the team
The 45-minute version suits a front-line team of six to ten reps meeting weekly. Three situations call for changes.
A new team or a new manager. Run the review one-on-one for the first month, 30 minutes per rep, using the same seven steps on a single book. The manager learns each rep's deals and how they describe them, and the team format starts with that knowledge in place.
A long sales cycle. When deals take six months or more, little moves week to week. Keep the weekly cadence for Steps 1, 3 and 6, which stay useful, and do the full review with Step 5 every second week.
A team above ten reps. Step 2 and Step 4 run long. Split the team in two for the review, or ask each rep to post their moved deals and disagreements in writing the day before so the meeting only takes questions on them.
Whichever version you run, keep Step 3 at the start. A pipeline review that never checks last week's planned conversations teaches reps that the plan is a formality.
Pipeline numbers worth bringing to the meeting
Step 1 needs a few numbers on one screen. These four tell the team the most about whether the book is healthy, and none of them needs a forecasting tool.
| Number | What it shows | What to do when it looks wrong |
|---|---|---|
| Coverage by evidence stage | Pipeline counted only where buyer evidence backs the stage, against the remaining target | If coverage looks healthy by CRM stage and thin by evidence, Step 4 gets more time this week |
| Deals with no dated buyer step | Deals where nothing is on the buyer's calendar | Treat them as stalled until a date exists, and put the largest on the shortlist |
| New pipeline this week | What entered the book, by rep | A team busy closing often stops creating. Two quiet weeks in a row is a conversation in the one-on-one |
| Age in stage | How long each deal has sat at its current evidence rung | Deals far past the team's usual time in a stage are candidates for Step 5 |
Keep the same four every week. Changing what the team sees each Monday makes it hard to notice a trend.
Questions to ask at each stage
The spotlight in Step 5 works best when the team asks the question that tests the deal's current rung. A short list by stage, all answerable from the buyer's words or actions:
| Evidence rung | The question to ask |
|---|---|
| Problem described | "How did the buyer describe the problem, in their words?" |
| Cost stated | "Who put a number on it, and what was the number?" |
| Criteria confirmed | "Which of the buyer's own criteria did they say we meet?" |
| Signer on a call | "When did the person who signs last hear the case, and what did they ask?" |
| Approval steps walked | "Who did the buyer say approves this after the signer, and in what order?" |
| Dated buyer step | "What is on the buyer's calendar, and what happens if it moves?" |
If the rep answers with what they did, ask the question again. The pattern settles in a few weeks, and reps start preparing their answers that way before the meeting.
Team review or one-on-one?
Both formats have a job. The team review checks the whole book against the same rules, keeps planned conversations visible to everyone, and lets reps learn from each other's deals in Step 5. A one-on-one review goes deeper on one rep's deals and suits topics a rep would not raise in front of peers, such as a deal they misjudged badly.
Most teams run the weekly team review described here, then use the one-on-ones that follow it to work the shortlist. Some managers drop the team format and run only one-on-ones. That can work for a small team, but the manager then has to carry the shared rules alone, and reps stop hearing how their peers stage deals.
Where it goes wrong
The meeting becomes the recap. Reps read their deals aloud because nobody prepared the sheet. Fix: a rep without a sheet gets no airtime. The prep rule only works if the manager holds it for two or three weeks.
Activity counted as movement. "I sent three follow-ups" is reported as progress. Fix: Step 2 accepts buyer actions only.
Nobody checks last week. Plans are made and never revisited, so reps stop making real ones. Fix: Step 3 is fixed in the agenda and runs first after the number.
Fixing deals in the room. The manager coaches every deal that comes up and the meeting runs to 90 minutes. Fix: Step 5 gets two deals. Everything else goes on the shortlist for a one-on-one deal review.
The shortlist never gets reviewed. The meeting picks twelve deals and the manager has time for four. Fix: count the review slots before Step 6 and cap the shortlist there. A deal that misses the cut gets a check-in date.
Covering the deals the meeting cannot reach
The meeting produces the shortlist; the deal reviews on that shortlist are where deals move. With six reps and two deals each, that is twelve deal reviews a week on top of the meeting, and the manager's skill on each one matters (Dahling et al. 2016, via our kickoff field study).
Our AI sales experts take some of that load. Each rep brings a shortlisted deal to Caty and talks it through by voice or video on a call, or by typing when they can't talk. She checks the buyer's words against the team's method, names what is missing and plans the next conversation. That changes Step 4 most: Bryce, the manager's coach, shows the manager the gap between CRM commit and commit by evidence before Monday, so the 45 minutes go on the deals that need a human. For the one-on-one format, see how to run a deal review. To set this up across a team, talk to us.
FAQ
How do you run an effective pipeline review meeting?
Run a fixed 45-minute agenda on deals each rep has staged by buyer evidence beforehand. The agenda runs: the number, deals where the buyer did something, last week's planned conversations, deals whose CRM stage is ahead of the evidence, one or two deals in depth, the shortlist for deal reviews and this week's commitments.
How long should a pipeline review meeting be?
A pipeline review meeting should take about 45 minutes for a team of six to ten reps, held weekly. Longer meetings usually mean deals are being recapped or coached in the room. Move recaps into prep and coaching into one-on-one deal reviews, and the meeting fits.
What questions should you ask in a pipeline review?
Ask questions that only the buyer's words or actions can answer. Ask what the buyer did this week, whether last week's planned conversation happened and what the buyer said, and which deals have a CRM stage ahead of their evidence. On the spotlight deal, ask who signs and what number the buyer put on the problem.
What is the difference between a pipeline review and a forecast call?
A pipeline review checks whether the deals are real and picks which need work. A forecast call takes the result and commits to a number for the period. The pipeline review should happen first each week so the forecast is built on deals whose stage was checked.
Should reps present their whole pipeline in the meeting?
No, reps present only the deals that need the room. They stage their whole pipeline in a shared sheet before the meeting. The meeting then spends its time on deals that moved, deals whose stage is in doubt and one or two deals in depth. Reading every deal aloud is a common reason pipeline meetings run long.