Answers

What is a pipeline review?

Pipeline reviews live between the forecast call and the deal review. They are shorter than both, repeat weekly, and exist to force a stage-by-stage audit so that soft deals get surfaced before they rot in the pipeline instead of after.

Short answer

A pipeline review is a short weekly meeting, usually 20 minutes, where a sales manager walks a rep or team through every open deal stage by stage, pressure-tests health against the forecast, and coaches on the deals most likely to slip. It is not a forecast call and it is not a deal review. The forecast question is which number lands, the deal review question is how to win one deal, and the pipeline review question is which deal are we losing.

Key points

What matters most.

The six rules that define a pipeline review, what it tests, and how it differs from the forecast call that lives on the same calendar.

The meeting

Twenty minutes, weekly, one rep or one team.

A pipeline review runs twenty minutes on a weekly cadence. Any shorter and the stage walk gets rushed. Any longer and the meeting turns into a deal review in disguise. The slot can be a 1:1 between a manager and a single rep, or a team block where each rep gets a few minutes. The cadence is non-negotiable, because the whole point is that no deal goes more than a week without a second set of eyes.

The question

Which deal are we losing?

A pipeline review exists to answer one question: which deal are we losing. The forecast call asks whether the number lands. The deal review asks how to win a specific opportunity. The pipeline review asks the manager to point at the deals that look healthy on paper but are actually drifting. If the review ends and nobody has named a slipping deal, the meeting failed.

Not a forecast call

Different question, different seat at the table.

Forecast calls roll numbers up to the VP or CRO. The seat at the table is the rep's commit against the quota, and the deliverable is a committed number for the quarter. Pipeline reviews stay inside the manager-rep layer, run weekly, and produce coaching actions, not numbers. Running them as the same meeting is the single most common reason first-line managers burn out their reps.

Not a deal review

Breadth beats depth, every week.

A deal review goes deep on one opportunity for an hour. A pipeline review goes a mile wide across the whole book for twenty minutes. The manager is checking for stage accuracy, next-step freshness, and risk signals, not building a close plan. If a deal needs real strategy work, the manager flags it in the pipeline review and books a dedicated deal review later in the week.

The audit

Stage by stage, no skipping.

The manager walks every stage from top to bottom. Discovery deals get checked for pain and next step. Evaluation deals get checked for champion and economic buyer. Proposal deals get checked for a close date that is not fiction. Each stage has three or four questions. The audit is boring on purpose, because the deals that slip are usually the ones a rep stopped looking at.

The filter

MEDDPICC score decides who gets the airtime.

A full-book walk never fits in twenty minutes, so the manager uses a qualification score to triage. Deals with a weak MEDDPICC score, a stale next step, or a close date in the past get airtime first. Deals that score clean move fast. The score is a filter, not a verdict, and the manager still spot-checks a few clean deals to make sure the rep is not grading themselves generously.

The agenda

What runs inside the 20-minute slot.

A pipeline review has a tight agenda because the slot is short on purpose. The manager opens with the top of the funnel so new deals get calibrated early, walks the middle stages where most slippage hides, and ends with the closing bucket where the forecast lives. The last few minutes are for the deals the manager wants to escalate into a dedicated deal review. The structure below is the default; the manager flexes it when the pipeline shape changes week to week.

Open · 2 min

Scoreboard and the one slipping deal.

The manager opens with the headline numbers from the rep's book: coverage ratio against quota, number of deals added this week, number of deals pushed. Then the manager asks the rep to name the one deal they are most worried about. That deal gets a flag and comes up again at the end. Two minutes, no small talk, because the slot is twenty.

Top of funnel · 3 min

New deals, pain, and next step.

The manager walks every deal added since the last review. Each one gets three questions: what is the pain in the buyer's words, what is the next step on the calendar, and does the stage match the discovery that actually happened. Three minutes is enough because the deals are young. Catching a bad stage here saves the manager from fighting it four weeks later.

Middle stages · 7 min

Where deals go to drift.

The middle of the funnel gets the biggest block, because this is where soft deals hide. Each deal is checked for champion, economic buyer, decision criteria, and a next step booked on the calendar. If any of those four are missing, the deal gets flagged. The manager does not try to fix the deal in the moment; the fix is a coaching action the rep owns for the week.

Closing stages · 5 min

Close date, paper, and procurement.

Deals in proposal or negotiation get checked for a close date the buyer has actually agreed to, paper status, and procurement or security blockers. The manager is looking for close dates that have moved more than twice, redlines sitting with legal, or security questionnaires nobody has started. Five minutes is tight, so the agenda favors blockers over strategy here.

Risk and escalation · 2 min

What goes into a dedicated deal review.

The manager picks the one or two deals that need real strategy work and books them into a separate deal-review slot later in the week. The slipping deal from the opening flag usually ends up here. The pipeline review is not the place to fix a deal; it is the place to notice one needs fixing. Two minutes to decide and move on.

Coaching close · 1 min

Two actions the rep owns before next week.

The last beat is the manager naming two specific coaching actions the rep owns before next Monday. Not five, not ten; two. A multi-threading move on one deal, a close-date pressure test on another. The rep repeats the two actions back so there is no ambiguity, and they get logged against the deals in the CRM so next week's review opens with the follow-up.

Cadence and format

How often, who shows up, and in what shape.

The cadence of a pipeline review is the thing most teams get wrong. Weekly is the floor. Bi-weekly is a signal that the manager is coaching too thinly, and monthly is almost always a forecast call pretending to be a pipeline review. The format flexes between a manager-rep 1:1 and a team block depending on headcount, pipeline size, and the maturity of the sales motion.

Weekly 1:1

The default for most teams.

The most common format is a 20-minute weekly 1:1 between the manager and each rep, usually attached to the top of a longer weekly 1:1. It gives every rep a focused slot and keeps the audit frequent. The downside is the manager has to run one review per rep per week, which gets expensive at eight-plus reps on a team.

Team block

Each rep gets five minutes.

Larger teams run a 45-minute team block where each rep walks their top deals for five minutes while the rest listen. The upside is cross-team learning: reps hear how the manager pressure-tests other books. The downside is the slower reps get less airtime, so the manager still owes them individual catch-ups when a deal needs more depth.

Pod review

Rep plus SE plus manager.

On more complex deals, the pipeline review includes a sales engineer so technical risk gets flagged in the same slot as commercial risk. Thirty minutes instead of twenty, and the review stays per-rep rather than team-wide. Good fit for enterprise motions where every deal has a technical workstream running in parallel.

Pipeline council

Monthly, cross-team, VP-led.

A pipeline council is a monthly meeting one level above the weekly review. The VP sits with first-line managers to look at coverage, mix, and the shape of the pipeline across the team. It replaces nothing. Each manager still runs their weekly reviews with their reps; the council is pattern work, not deal work.

Office hours

Open coaching between reviews.

Some teams add an optional weekly office-hour slot where any rep can bring a deal for a quick second opinion. It is not a replacement for the pipeline review, and nobody is required to show up. It is a release valve for deals that cannot wait seven days for the next scheduled slot, especially in fast-moving transactional motions.

Quarterly reset

Once a quarter, zoom out.

Once per quarter, the manager and rep spend 60 minutes instead of 20 and treat the review as a reset: closed-lost analysis, stage-definition calibration, average-deal-size drift, and whether the rep's book shape matches their quota. It is still a pipeline review, just the version where the agenda is permission to zoom out.

How managers get it wrong

The failure modes that break pipeline reviews.

Pipeline reviews fail in predictable ways. Managers merge them with the forecast call and the whole meeting collapses into number negotiation. They let a single deal eat the slot and twelve others go unaudited. They coach instead of audit, or audit instead of coach, when the slot was designed for both. Every failure mode below shortens the time the review spends on the deals that are actually slipping, which is the whole point of the meeting.

Merged with forecast

Both meetings become neither.

The manager runs pipeline review and forecast call as one meeting. The rep spends the whole slot defending the commit number, and no deal gets audited. The rep leaves without coaching, and the manager leaves without a clear sense of which deals are slipping. Split the meetings, even if that means fifteen minutes and five minutes instead of twenty combined.

One-deal sinkhole

A single deal eats the twenty minutes.

A rep brings a dramatic deal to the top of the slot and the manager spends the whole review on it. Twelve other deals get zero airtime. The fix is a hard split: three minutes maximum on any one deal inside the review, and anything deeper gets booked into a dedicated deal review later in the week.

No stage audit

The manager trusts the CRM stage.

The manager accepts whatever stage the rep set in the CRM and never pressure-tests whether the discovery actually happened. Stage inflation is the single most common pipeline problem, and the pipeline review is the one meeting where it should get caught. If the manager is not asking what happened in the room, the stage is probably wrong.

Coaching without data

Opinions beat the audit.

The manager runs the whole review on vibes: which rep sounds confident, which deal feels real. No qualification score, no next-step check, no close-date history. The reps who talk well get coached up and the reps who talk less get missed. The audit is the data; the coaching is the output.

No action logged

The slot ends with vague homework.

The manager closes with 'push on the Acme deal' and nothing lands in the CRM. Next week nobody remembers what was agreed. The two coaching actions should get logged against the specific deals before the review ends, so the next slot opens with a concrete follow-up instead of a reconstructed memory.

Skipped weeks

The cadence breaks and the audit dies.

The manager skips a review when the week is busy. One skip becomes two, and within a month the pipeline stops getting audited at all. The slipping deals that would have been caught in week two go unflagged until the forecast call in week five, which is where quarters go to die. The slot is sacred; move it, do not skip it.

Run every pipeline review on data your reps did not have to type in.

Strkr auto-updates stage, next step, and MEDDPICC fields from call transcripts and email threads, so pipeline reviews open on real signals instead of CRM theatre. One login for CRM, calling, and the forecast that runs off them.

People also ask

Related questions.

What is a pipeline review?

A pipeline review is a short weekly meeting where a sales manager walks a rep or team through every open deal stage by stage, pressure-tests health against the forecast, and coaches on the deals most likely to slip. The slot is usually twenty minutes. The question the meeting exists to answer is which deal are we losing. It is not a forecast call, where the question is whether the number lands, and it is not a deal review, where the question is how to win a specific opportunity.

How is a pipeline review different from a forecast call?

A forecast call rolls numbers up to the VP or CRO and produces a committed number against quota. A pipeline review stays inside the manager-rep layer and produces coaching actions against specific deals. The forecast call is about the quarter; the pipeline review is about the week. Running them as the same meeting is the single most common reason first-line managers burn out their reps, because the slot collapses into number negotiation and no deal ever actually gets audited.

How is a pipeline review different from a deal review?

A deal review goes deep on one opportunity for an hour and produces a close plan. A pipeline review goes a mile wide across the whole book for twenty minutes and produces a flag list. If a deal in the pipeline review needs real strategy work, the manager books a dedicated deal review later in the week. The pipeline review is not the place to fix a deal; it is the place to notice one needs fixing.

How long should a pipeline review be?

Twenty minutes for a weekly 1:1 between a manager and a rep. Any shorter and the stage walk gets rushed. Any longer and the meeting turns into a deal review in disguise. Team blocks run 45 minutes with each rep getting a five-minute walk. Pod reviews with a sales engineer on complex deals run thirty. Quarterly resets run sixty. The default is twenty, and most teams underrun the slot before they overrun it.

How often should pipeline reviews happen?

Weekly is the floor. Bi-weekly is a signal the manager is coaching too thinly, and monthly is almost always a forecast call pretending to be a pipeline review. The whole point of the cadence is that no deal goes more than a week without a second set of eyes. Skipping a review is more expensive than running a bad one, because the slipping deals that would have been caught go unflagged until the forecast call, which is where quarters go to die.

What is on the agenda for a pipeline review?

A tight six-beat agenda inside the twenty minutes: open with the scoreboard and the one slipping deal (2 min), walk the top of the funnel for new deals (3 min), audit the middle stages where deals drift (7 min), check closing-stage blockers (5 min), flag deals that need a dedicated deal review (2 min), and close with two specific coaching actions the rep owns before next week (1 min). The structure flexes week to week as the pipeline shape changes.

How does MEDDPICC fit into a pipeline review?

MEDDPICC is a filter, not a verdict. A full-book walk never fits in twenty minutes, so the manager uses the qualification score to triage. Deals with a weak score, a stale next step, or a close date in the past get airtime first. Deals that score clean move fast through the review. The manager still spot-checks a few clean deals, because reps grade themselves generously, and the score is only as honest as the data the rep put in.

Who should attend a pipeline review?

The default attendees are the first-line manager and the rep. On more complex deals, a sales engineer joins so technical risk gets flagged in the same slot as commercial risk. Team blocks include every rep on the team. Pipeline councils, which run monthly instead of weekly, bring the VP or CRO together with first-line managers to look at coverage and mix across the whole team. VPs sitting in on every weekly review is a signal that the first-line managers are not trusted, not a sign of healthy coaching.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.