Pulse ← Library
Pulse Coaching

How do you run a pipeline review that isn't just status updates?

Kory WhiteCurated by Kory White · Fractional CRO, CRO Syndicate
👍 Yup or 👎 Nope — vote this up its category:
📅 Published · Updated

Direct Answer

A pipeline review stops being a status update the moment you stop asking "where is this deal?" and start asking "what would have to be true for this deal to close, and what are you doing this week to make it true?" The core move is to coach the next action, not the CRM stage.

Run it as a deal-coaching session, not a roll-call: pick the 3-5 deals that matter, pressure-test the evidence behind each forecast using a qualification framework like MEDDIC, and leave every rep with a committed next-best-action and a date. The manager's job in the room is to make reps think, not to recite numbers everyone can already read in Salesforce.

If you find yourself reading the dashboard out loud, you are running a status update, and you should stop.

How do you run a pipeline review that isn't just status updates?

Why This Happens — Diagnose Before You Coach

Most pipeline reviews degrade into status updates for a predictable reason: it is the path of least resistance for both sides. The rep narrates the CRM, the manager nods, nobody is exposed, and an hour disappears. Before you redesign the meeting, diagnose *why* yours is broken, because the fix differs by root cause — skill, will, knowledge, or system.

A skill gap looks like reps who genuinely do not know how to qualify, so they describe activity ("I sent the proposal") instead of evidence ("the economic buyer confirmed budget"). A will problem looks like reps who happy-ear every deal because an honest pipeline is a scary pipeline.

A knowledge gap is a manager who has not defined what "qualified" means, so there is no shared bar to coach against. A system problem is structural: the meeting has 14 people and 60 deals, so there is physically no time to coach anything — it can only ever be a status sweep.

flowchart TD A[Pipeline review feels like status updates] --> B{Do reps describe activity or evidence?} B -->|Activity only| C{Do they KNOW how to qualify?} B -->|Evidence| D{Is the forecast still inflated?} C -->|No| E[SKILL gap: teach MEDDIC, drill qualification] C -->|Yes but avoid it| F[WILL gap: make honesty safe, coach pipeline hygiene] D -->|Yes| F D -->|No| G{Is there time to coach in the meeting?} G -->|No, too many deals/people| H[SYSTEM problem: shrink scope, tier the deals] G -->|Yes| I{Has manager defined 'qualified'?} I -->|No| J[KNOWLEDGE gap: publish the bar, then coach to it] I -->|Yes| K[Run deal-coaching, not roll-call]

Run this diagnosis before your next review. If the answer is system or knowledge, no clever questioning technique will save you — you have to fix scope and definitions first.

The Coaching Conversation

The shift from status to coaching lives in the questions you ask. Use the GROW model (Goal, Reality, Options, Will) to keep yourself from solving the deal for the rep. Your goal is to make the rep do the thinking out loud. Below are verbatim questions to use in the room — copy these into your 1:1 notes.

Open by reframing the room. Say: *"We're not doing a status update today. I can read the CRM. Bring me the three deals you most want to win this quarter and the one you're least sure about. We're going to figure out what moves them."*

Goal — make them commit to an outcome. Ask: *"What do you actually believe will happen with this deal, and by when?"* Then the killer follow-up: *"What's your confidence on a 1-to-10, and what would make it a 9?"* The gap between their number and a 9 is your coaching agenda.

Reality — pressure-test the evidence, not the story. Use MEDDIC as your checklist and ask the questions that expose air in the forecast:

When a rep says "they love it," do not accept it. Say: *"Love is not a buying signal. What did they *do* that proves it — a meeting they set, a stakeholder they pulled in, a date they gave you?"*

Options — let them generate the next move first. Resist solving it. Ask: *"What are two things you could do this week to advance it?"* and *"If I gave you one extra hour with this account, where would you spend it?"* Only after they have proposed something do you add your idea — and frame it as a question: *"What would happen if you asked the economic buyer for a mutual close plan directly?"*

Will — lock the commitment. Close every deal with: *"So what's the single next action, and when will it be done?"* Write it down. Next week, the meeting opens with that commitment, not a fresh status tour. That accountability loop is what converts a review into coaching.

The Coaching Plan / Cadence

A pipeline review is one beat in a weekly rhythm, not a standalone event. The meeting only works if it is fed by call reviews and 1:1s and followed by accountability. Treat it as a loop.

Weekly cadence that holds up:

flowchart LR A[Observe: review a real call recording] --> B[Diagnose: skill/will/knowledge/system] B --> C[Coach: GROW questions in the review] C --> D[Practice: role-play the next move] D --> E[Measure: did the next action happen?] E --> F[Repeat next week, open with the commitment] F --> A

For a new manager inheriting a status-update culture, run a 30/60/90: first 30 days, shrink scope to top deals and ban dashboard-reading; next 30, install MEDDIC self-scoring and call reviews; final 30, push accountability so reps run their own deal-coaching and you only inspect the exceptions.

Drills & Role-Play

Coaching questions only stick if reps practice the answers somewhere safe. Build these reps in.

What to Measure

Quota is a lagging indicator. If you only measure attainment, you find out you have a problem a quarter too late. Track leading indicators that prove the coaching is changing behavior:

Common Mistakes Managers Make

FAQ

How long should a pipeline review be? For a deal-coaching review, cap it at 45 minutes and 3-5 deals. Anything longer almost always means you have slipped back into status-update mode, sweeping every deal instead of coaching the ones that matter. Do broad coverage async in the CRM; reserve the meeting for the deals where your questions can actually change the outcome.

Should pipeline reviews be 1:1 or group? Both, for different jobs. Run honest, exposing deal-coaching in 1:1s where a rep can admit a deal is weak without losing face. Use small-group reviews to spread tactics — when one rep multi-threads a deal well, the room learns it.

Avoid large all-hands reviews; they force status updates because there is no time to coach anyone.

How do I stop reps from sandbagging or happy-earing the forecast? Make honesty cheaper than inflation. Reward the rep who pulls a dead deal early instead of punishing them, and use the "9 or it's a 1" drill plus MEDDIC evidence checks so confidence has to be defended, not asserted.

When reps see that an honest pipeline gets help and an inflated one gets exposed, the behavior corrects itself.

What's the difference between a pipeline review and a forecast call? A forecast call answers "what will we close?" — it is inspection for the number. A pipeline review answers "what will we *do* to close it?" — it is coaching for the behavior. Keep them separate; blending them turns coaching into negotiation over the commit number.

How do I run this with a hybrid or remote team in 2027? Lean on AI call-coaching tools like Gong or Chorus so the review is grounded in recorded reality rather than memory, and shorten the live meeting to the coaching itself. Async pre-work (CRM updates, self-scoring, one flagged call) does the inspection; the live time — even remote — is spent only on the questions that move deals.

My reps just give status anyway. How do I break the habit? Change the opening line and the first question. Ban dashboard narration out loud, and open with "what's your confidence on a 1-to-10 and what would make it a 9?" The question physically cannot be answered with a status update, so it forces the room into coaching from minute one.

Bottom Line

The one move that converts a status update into a real pipeline review is coaching the next action instead of the current stage. Pick a few deals that matter, pressure-test the evidence with MEDDIC and GROW questions, and send every rep out with a committed next-best-action you will inspect next week.

Read the CRM on your own time; spend the meeting making reps think.

Sources

*Sales coaching for pipeline reviews — how to coach pipeline reviews that aren't status updates, sales manager coaching guide, deal-coaching framework, rep coaching playbook, and a pipeline review coaching playbook for 2027.*

Keep reading
Was this helpful?  
⌬ Apply this in PULSE
Free CRM · Revenue IntelligenceAudit pipeline, score reps, ship the fixPulse CheckScore reps on the metrics that matter
Related in the library
More from the library
sales-coaching · coachingHow do you coach a rep to navigate a buying committee?sales-coaching · coachingHow do you structure a weekly sales coaching 1:1?sales-coaching · coachingHow do you coach a rep to improve their cold-call connect rate?sales-coaching · coachingHow do you coach reps using Gong or Chorus call recordings?sales-coaching · coachingHow do you coach reps to improve their lead-to-opportunity rate?sales-coaching · coachingHow do you coach a rep who's stressed about hitting quota?sales-coaching · coachingHow do you coach reps to manage their own energy and time?sales-coaching · coachingHow do you coach a rep on a stalled six-figure deal?sales-coaching · coachingHow do you coach a rep with great results but low activity?sales-coaching · coachingHow do you coach reps to keep their pipeline 3x covered?sales-coaching · coachingHow do you coach a rep to improve their business acumen?sales-coaching · coachingHow do you coach product knowledge to a brand-new salesperson?sales-coaching · coachingHow do you coach a remote sales team effectively?