The standard pipeline review format looks like this: the manager opens a CRM report showing all open opportunities, asks the rep to walk through their top deals, the rep narrates each one, the manager asks a few clarifying questions, and the outcome is either reassurance or a commitment to follow up on specific deals before the next review. The forecast number is adjusted based on whatever the rep said.

This format has a fundamental structural problem: it produces the rep's current narrative about each deal, not an objective assessment of each deal's status. The rep who is naturally optimistic will present every deal in its most favourable light. The rep who is anxious about the quarter will hedge everything. The manager, who lacks independent signal about most of the deals, has limited basis for challenging either framing. The forecast that comes out of the review is a negotiated number built on conversation rather than data.

What a Signal-Led Review Looks Like

A signal-led pipeline review inverts the sequence. Before the rep says anything, the manager has already looked at three objective signals for every deal in the pipeline: the date of the last two-way engagement with the prospect (not the last time the rep reached out — the last time the prospect responded), how many times the close date has been moved, and whether the deal has advanced in stage since the last review.

These three signals do not tell the manager everything. But they do tell the manager which deals deserve scrutiny and which ones are progressing as expected. A deal at stage 3 with the prospect's last response 14 days ago and the close date moved once is a deal that warrants a specific conversation. A deal at stage 4 with active email exchange this week and no close date changes does not — it is on track until there is evidence it isn't.

Starting from signals rather than rep narrative means the manager enters the review with informed questions rather than open ones. "The last two-way contact on Acme was 12 days ago — what happened after the proposal went out?" is a more useful question than "how are things going with Acme?" The first question cannot be answered with narrative alone. The second one can.

The Three Categories Every Deal Belongs To

At the end of a signal assessment, every deal in the pipeline should be sortable into one of three categories: active and progressing (the signal supports the rep's confidence assessment), at risk (the signal is inconsistent with the stage or the rep's confidence), and stalled or dark (the signal indicates the deal has lost momentum and needs intervention).

The pipeline review should spend most of its time on the second category — at-risk deals — rather than on active ones (which don't need much discussion) or truly stalled ones (which need a rescue plan, not a review). The active deals should be acknowledged and briefly confirmed. The stalled ones should be assigned specific next steps or formally disqualified. The at-risk ones are where a manager's attention produces the most value: they are still recoverable, and the right conversation can either produce a credible plan to advance them or a well-founded decision to remove them from the forecast.

The Questions That Produce Useful Answers

The questions that produce useful information in a pipeline review are specific and evidence-referencing. "When did the prospect last respond to you directly — not a read receipt, an actual reply?" is useful. "What was the content of that reply?" is useful. "Has the economic buyer been personally engaged in any interaction?" is useful. "What is the agreed next step and what is the specific date?" is useful.

The questions that produce narrative rather than data are the ones most commonly asked: "How are you feeling about this one?" "Do you think they're going to close?" "What's your confidence level?" These questions invite the rep to share their emotional state about the deal rather than its objective condition. The emotional state is not irrelevant — an experienced rep's instinct is real information — but it should come after the evidence, not instead of it.

What a Useful Pipeline Review Produces

A well-run 45-minute pipeline review should produce three specific outputs. First, a revised forecast number — not the number the rep reported last week with marginal adjustments, but a number built from the deals that have the signal support to justify their stage and probability. Second, a list of three to five deals requiring specific action this week — with the action defined clearly enough that the rep knows exactly what they are going to do and the manager knows exactly what to hold them accountable for at the next review. Third, a list of deals to formally disqualify — deals that have been in the pipeline for more than two stage durations without progressing, that have gone dark and not responded to re-engagement attempts, or where the champion has left and no replacement contact has been established.

Formal disqualification should be treated as a positive outcome of a pipeline review, not a negative one. A rep who removes five stalled deals from their pipeline and replaces them with five fresh qualified opportunities will close more revenue than a rep who maintains fifty deals and can actively manage none of them well.

◆ Pipeline Review Redesign — Do This Before Your Next Review

Before the review: Pull the three objective signals for every deal — last two-way contact date, number of close date pushes, stage advancement since last review. Sort deals into three categories: progressing (green), at-risk (amber), stalled (red). Print or share this before the rep walks in.

During the review: Spend 5 minutes maximum on green deals — confirm they are on track and move on. Spend the majority of time on amber deals — ask evidence-referencing questions, not narrative ones. For each red deal, decide in the meeting: rescue attempt with specific action, or formal disqualify.

Close the review with three outputs: (1) A revised forecast number built from deals with signal support. (2) A list of 3–5 deals with specific defined actions and dates. (3) A list of deals to formally disqualify before the next review. These should be written down and shared, not held in the manager's memory.

At the next review: Open with the action list from the previous review. What happened on each item? This creates accountability without surveillance — the rep knows what they committed to, and the manager knows exactly what to ask about. Reviews that don't start with previous commitments breed the narrative-update culture that makes them ineffective.

A pipeline review is only as good as the signals it starts from. If the starting point is always what the rep says, the review will always be shaped by how the rep tells the story. If the starting point is objective signal data, the conversation that follows will be more specific, more honest, and more useful.