A pipeline review improves performance when it runs on coaching questions instead of status questions — and the difference is decided before the meeting starts, in how the manager prepares. A bad review is a status report where reps narrate and managers nod; a good one is a working session on the specific deals where evidence and story disagree.
The three types of pipeline review questions
Status questions (stop leading with these)
"Where are we on this deal?" "Did you hear back?" "What's the update?" Status questions produce narration — the rep recounts events, everyone listens, nothing changes. Worse, they train reps to prepare stories rather than evidence, because a good story satisfies a status question completely. The CRM should answer status questions before the meeting; asking them live burns the room's most expensive minutes on information transfer.
Evidence questions (build the meeting on these)
"What did the buyer commit to, in writing, and when?" "Who besides your champion has confirmed this timeline?" "What happens on their side between now and the close date, step by step?" Evidence questions convert deal review from narrative to inspection. They are answerable only with facts, which means gaps expose themselves without the manager playing prosecutor.
Coaching questions (finish with these)
"What would have to be true for this deal to close two weeks early?" "If you had to restart this deal today, what would you do differently?" "Which stakeholder do you understand least, and what's the plan?" Coaching questions develop judgment rather than extract information — and they are the part of the review that actually changes how the rep runs the next deal.
Prepare with a skeptical pre-pass
The manager's prep, not the meeting agenda, determines the review's quality. Run the pipeline through a structured challenge before the room fills.
Prompt: "You are a skeptical sales director preparing a pipeline review. For each deal: [PASTE PIPELINE WITH STAGES, CLOSE DATES, LAST ACTIVITY, NOTES]. Identify: (1) the three deals where the evidence least supports the forecast category, with the specific gap, (2) one evidence question per flagged deal, (3) any deal with no multi-threading activity in three weeks, (4) one pattern across the whole pipeline worth raising as a team coaching point."
Ten minutes of prep means the meeting opens on the three deals that matter instead of a round-robin through twenty that don't. Deals with clean evidence get thirty seconds of acknowledgment; the room's time concentrates where inspection changes outcomes.
Prompt: "For this flagged deal: [PASTE DEAL NOTES], write three coaching questions that develop the rep's judgment rather than extract status — questions about what would have to be true, what they would do differently, and which stakeholder they understand least. Phrase each as an open question with no embedded accusation."
Structure: inspect few, coach one, commit all
A working format for a one-hour team review: five minutes of pipeline math (coverage, movement since last week — from the CRM, not narration), thirty-five minutes on the flagged deals using evidence questions, ten minutes on the single team-wide pattern the pre-pass surfaced, and ten minutes of commitments — every rep leaves with one specific action per flagged deal, written down, reviewed first thing next session. The commitment loop is what separates a review that improves performance from one that merely audits it.
For reps: pre-run the review on yourself
Everything above inverts usefully for the individual rep. Run the skeptical pre-pass on your own pipeline the day before the review, and you walk in having already found the gaps your manager will find — with a plan attached to each instead of an explanation. "You're right that Meridian has no EB contact; I've asked my champion for the intro and the fallback is the CFO's staff meeting on the 20th" is a fundamentally different meeting than being discovered. Reps who self-inspect weekly report that reviews stop feeling like audits entirely, because there is nothing left to audit — only decisions to make together.
The tone that makes it work
Evidence-based reviews fail when they feel like cross-examination. Two habits protect the room: flag deals by evidence gap, never by rep suspicion — "the notes show no EB contact" lands differently than "I don't believe this close date" — and spotlight one strong deal each week with the same rigor, showing what good evidence looks like rather than only prosecuting weak deals. Reps who trust the standard start pre-running it on themselves, which is the end state a manager actually wants: a team whose pipeline self-inspects between reviews.
Frequently Asked Questions
How long should a pipeline review take?
One hour for a team of six to eight reps, concentrated on three to five flagged deals. Reviews that walk every deal equally run long and coach nothing.
Should pipeline reviews and forecast calls be the same meeting?
Keep them separate if you can. Forecast calls answer "what number do we submit"; pipeline reviews answer "how do these deals improve" — merging them makes the number defensive and the coaching disappear.
What if a rep consistently can't answer evidence questions?
That is a discovery-skills coaching signal, not a review problem. Move it to a 1:1 with call-level coaching; using the group review to expose the same rep weekly poisons the format for everyone.
Put It to Work
The skeptical pre-pass and evidence-question prompts are part of the sales coaching collection in the Promptifi library — 2,900+ prompts across 16 categories. Browse the library and prep your next review in ten minutes.