12 Pipeline Review
Questions That Actually
Move Deals Forward

The questions you ask in a pipeline review determine whether the review moves deals or merely collects status — and most reviews ask status questions ("where is this deal?") that get status answers, when they should ask forward questions ("what does this deal need to advance, and what will you do?") that surface action. A pipeline review's purpose is to move deals forward, and the questions are the tool: the right questions surface what is really going on with each deal, what is needed to advance it, and what the rep will do — driving action; the wrong questions (status questions) just collect where each deal is, which fills the review without moving anything. So the difference between a review that moves deals and one that recites them is largely the questions asked. This guide presents twelve pipeline review questions that actually move deals forward — questions that surface the real state, what is needed to advance, the risks, and the next commitment — along with why they work, how to use them, and the status questions to avoid. The throughline is that the right questions move deals: forward-oriented questions that surface what is really going on and what is needed to advance each deal drive action, while status questions just collect status — so a review built on the right questions becomes a working session that moves deals, not a status recap.

The reason the questions matter so much is that questions shape what a review produces — forward questions elicit the information and commitments that move deals, while status questions elicit only status — so changing the questions changes the review from passive to active. A status question ("where is this deal?", "what stage is it in?", "what's the status?") elicits a status answer (it's at the demo stage, the buyer is reviewing) — information about where the deal is, but not about what it needs or what will be done. A review built on status questions collects a lot of status but drives little action (each deal's status is reported, then the review moves on). Forward questions are different: they elicit the information and commitments that move deals. A question like "what specifically does this deal need to advance to the next step?" surfaces what is required (a stakeholder to engage, a concern to resolve), pointing to action. A question like "what will you do this week to move it, and by when?" elicits a commitment to a specific action. A question like "what could cause this deal to stall or be lost?" surfaces risk to address. These forward questions produce action (what is needed, what will be done, what to address), not just status. So the questions determine the review's output: status questions produce a status recap; forward questions produce action. This is why the questions are the key lever for making a review move deals — changing from status questions to forward questions converts the review from passive (collecting status) to active (driving action). The twelve questions below are forward questions of this kind, designed to surface what is really going on and what is needed to advance each deal. Using them in place of status questions is what makes the review move deals. The rest of this guide presents the questions, why they work, and how to use them. The questions are the tool; the right ones move deals.

Status Questions vs Forward Questions

The fundamental distinction is between status questions (which collect where a deal is) and forward questions (which surface what is needed to advance it and what will be done) — and a review moves deals only when built on forward questions. Status questions ask about the deal's current state: "Where is this deal?", "What stage is it in?", "What's the status?", "How's it going?" They elicit status answers — descriptions of where the deal is — which is information, but not action-driving information. A review of status questions collects each deal's status in turn (the rep-by-rep recap), filling the time without moving deals (knowing where a deal is does not move it). Forward questions ask about advancing the deal: "What does it need to advance?", "What's the risk?", "What will you do, by when?" They elicit action-oriented answers — what is required to move the deal, what could go wrong, what the rep will do — which point to and commit to action. A review of forward questions surfaces what each deal needs and elicits commitments to act, which moves deals. The distinction matters because the question type determines the review's output: status questions produce status (a recap), forward questions produce action (deals moving). So making a review move deals is largely a matter of asking forward questions instead of status questions — shifting from "where is this deal?" to "what does it need, and what will you do?" This shift is the key to the questions in this guide: they are forward questions, designed to surface what is really going on with each deal and what is needed to advance it, in place of the status questions that produce only recap. Recognizing the status-vs-forward distinction is the foundation for using the right questions: status questions feel natural (asking where a deal is) but produce recap; forward questions produce action, and are what a review should be built on. So the distinction between status and forward questions is the key insight: build the review on forward questions (what's needed, what's the risk, what will you do) rather than status questions (where is it), and the review moves deals instead of reciting them. The twelve questions below are forward questions of this kind.

The 12 Questions That Move Deals Forward

Here are twelve forward-oriented pipeline review questions — grouped by what they surface — that drive action on each deal.

• Real state of the deal: (1) What's actually happening with this deal right now? (2) Why will this deal close — what's the real reason the buyer would buy? (3) Is the buyer genuinely engaged, or has it gone quiet?
• What's needed to advance: (4) What specifically does this deal need to advance to the next step? (5) Is the right decision-maker engaged and bought in? (6) What's the buyer's decision process, and is there a clear path to a yes?
• Risk and what could go wrong: (7) What could cause this deal to stall or be lost? (8) Is there an unaddressed concern or objection? (9) Why might the buyer choose not to buy, or choose a competitor?
• The next action and commitment: (10) What's the single most important thing to do to move this deal, and what will you do this week? (11) By when will the next step happen, and what are you waiting on? (12) If this deal isn't going to close, should it stay in the pipeline?

Each question is forward-oriented — surfacing the real state, what's needed, the risk, or the next action/commitment — rather than just collecting status. Used in a review, they drive the discussion toward what each deal needs and what will be done, moving deals. You need not ask all twelve of every deal; ask the ones that surface what matters for each deal's situation.

Why These Questions Work

These twelve questions work because each surfaces something that drives action — the real state, what is needed, the risk, or the next commitment — rather than just collecting status, so the review built on them moves deals. The real-state questions (1–3) surface what is genuinely happening with the deal (not just its stage) — including the honest reason it would close and whether the buyer is really engaged — which cuts through optimistic assumptions to the deal's true state, the basis for managing it. The what's-needed questions (4–6) surface what the deal actually requires to advance (the next step, the decision-maker, the path) — pointing directly to the action needed, which is what moves the deal. The risk questions (7–9) surface what could go wrong (stalls, concerns, competitors) — which lets the review address risks before they kill the deal, protecting it. The next-action questions (10–12) elicit commitments to specific actions (what will be done, by when) and force the keep-or-kill decision (should this deal stay in the pipeline) — which produces the action and pipeline discipline that move deals and keep the pipeline honest. Together, the questions surface the deal's real state, what it needs, its risks, and the committed next action — which is exactly what moves a deal forward (you know the real state, address what is needed and the risks, and commit to the next action). They work because they are forward-oriented: each elicits action-relevant information or a commitment, not just status. This is in contrast to status questions, which surface only where the deal is — useful as a starting point but not action-driving. The questions also enforce honesty: asking why a deal will close, whether the decision-maker is engaged, and whether it should stay in the pipeline pushes past optimistic assumptions to the deal's real state and prospects, which is the basis for honest pipeline management. So these questions work because each surfaces something action-driving — real state, what's needed, risk, or next commitment — which together move the deal and keep the pipeline honest, unlike status questions that just collect where deals are. Build the review on these forward questions, and it moves deals; the questions are forward-oriented by design, which is why they work.

Using the Questions in the Review

Using the questions well means deploying them in the review to drive the discussion toward action on each deal — selecting the questions that surface what matters for each deal, and following the answers to decisions and commitments. A few principles for using them. Select the relevant questions per deal: you need not ask all twelve of every deal — ask the ones that surface what matters for that deal's situation (for a deal that may be stalling, the risk and what's-needed questions; for a deal nearing a decision, the path and next-action questions). The right few questions per deal keep the review focused and forward-moving. Follow the answers to action: the questions surface information (what's needed, the risk) and elicit commitments (the next action) — follow these to decisions and assigned actions, so the discussion produces action, not just answers. Push for honesty: the questions work best when answered honestly (the real reason it will close, the real risk, whether it should stay in the pipeline), so push past optimistic or vague answers to the real state — which the questions are designed to surface but which requires a manager willing to push. Use them to catch issues: the questions surface stalls, risks, and dead deals (the real-state and risk questions, and the keep-in-pipeline question), so use them to catch and address these (the stuck-deal and stalled-deal prevention). And keep it efficient: a review using the right few forward questions per deal can be efficient and productive (focused on action), unlike the long status recap. Used this way, the questions make the review a working session: the manager asks the forward questions that surface what each deal needs, follows the answers to decisions and committed actions, pushes for honesty, and catches issues — moving deals and keeping the pipeline honest. This is how the questions become the tool that makes a review move deals: deployed to drive the discussion toward action on each deal. So use the questions by selecting the relevant ones per deal, following the answers to decisions and committed actions, pushing for honesty, and catching issues — which turns the review into the deal-moving working session it should be. The questions are the tool; using them to drive toward action is what makes the review move deals. Ask the right forward questions, follow them to action, and the review works.

Avoiding the Status-Recap Questions

The flip side of using forward questions is avoiding the status-recap questions that produce only status — the "where is this deal?" questions that fill the review without moving anything, which tend to dominate by default. The status questions ("where is this deal?", "what stage?", "what's the status?", "how's it going?", "any update?") feel like the natural questions for a review (you are reviewing the deals, so you ask where they are) — and they are the default that produces the rep-by-rep status recap. But they produce only status: the answers describe where each deal is, which fills the review without surfacing what is needed or driving action. So a review dominated by status questions becomes the status recap that moves no deals — the failure mode. Avoiding it means consciously replacing the status questions with forward questions: instead of "where is this deal?", ask "what does it need to advance, and what will you do?"; instead of "what's the status?", ask "what's the risk, and what could cause it to stall?"; instead of "any update?", ask "what's the next step, and by when?" This conscious replacement is necessary because the status questions are the default that creeps in (they feel natural), so a deal-moving review requires deliberately asking forward questions instead. It also helps to recognize the limited role of status: a brief sense of where a deal is can be a starting point, but the review should quickly move from status (where is it) to forward (what does it need, what will you do) — not dwell on status. The discipline is to keep the review's questions forward-oriented, resisting the pull toward the status recap. So avoiding the status-recap questions means consciously replacing the natural-but-passive status questions ("where is this deal?") with forward questions ("what does it need, what will you do?"), recognizing that status questions are the default that produces the recap, and keeping the review's questions forward-oriented. This, combined with using the forward questions, is what keeps the review moving deals rather than reciting them. Avoid the status questions, ask the forward ones, and the review works. The status questions are the enemy of a deal-moving review; the forward questions are the tool — so deliberately ask the latter, not the former.

FAQ: Pipeline Review Questions