What a Pipeline Review Is
A pipeline review is a regular, structured look at deal data between a sales manager and their reps. It checks deal health, surfaces risk, coaches strategy and protects forecast accuracy. It is the main way a team keeps its pipeline honest, and one of the most valuable half hours a sales manager spends each week.A good pipeline review is a coaching conversation, not an interrogation. It focuses on what the rep can control and what help they need.
How is a pipeline review conducted?
The most effective pipeline reviews follow a prioritized structure:
First 10 minutes: Commit deals. Review every deal the rep has committed to closing this quarter. For each: What has changed? Is the timeline holding? What specific evidence supports the commit categorization? Next 10 minutes: At-risk deals. Review deals flagged by time-in-stage alerts, risk scores, or recent negative signals. For each: What is blocking progression? What intervention can unblock it? Should this deal be downgraded or removed? Next 10 minutes: Best case and upside deals. Review deals that could close if things go well. What needs to happen to pull these into commit? What help does the rep need? Last 5 minutes: Pipeline generation. Is the rep creating enough new pipeline for next quarter? What prospecting activities are planned?Key questions for each deal:
| Question | What It Reveals |
|---|---|
| What happened since last review? | Whether the deal is progressing or stalled |
| What is the validated next step and date? | Whether the deal has forward momentum |
| Who is the champion and when did they last engage? | Whether internal advocacy is active |
| How many stakeholders are we engaged with? | Whether the deal is multi-threaded |
| What could prevent this from closing on time? | What risks need mitigation |
Why pipeline reviews matter for revenue teams
Pipeline reviews catch what the forecast cannot see yet. They improve forecast accuracy by checking deal data every week. They improve win rates by catching and addressing stuck deals early. They improve rep development by providing regular coaching on deal strategy.Without structured reviews, reps develop blind spots about their own pipeline. They hold onto dead deals too long. They miss risk signals that a second set of eyes would catch. Managers lose visibility into what is really happening in the pipeline, and the forecast becomes a guess.
How to run more effective pipeline reviews
- Use data to set the agenda, not the rep. Pull the review list from CRM data: deals with changed status, deals exceeding median time-in-stage, deals in commit, and new deals. Do not let the rep choose which deals to discuss. The agenda comes from the data. - Ask questions, do not make statements. "Have you engaged the CFO?" is better than "you need to engage the CFO." Questions force the rep to think through deal strategy. Statements create compliance without understanding. - Document actions and follow up. Every deal discussed should have a documented next action, owner, and date. Start the next review by checking progress on those actions. Reviews without follow-up teach reps that the conversation is performative. - Limit to 30-45 minutes. Longer reviews lose energy and focus. If a rep has too many deals to cover in 45 minutes, prioritize based on value and risk. Healthy, progressing deals do not need 10 minutes of discussion. See pipeline management for cadence design.
Common mistakes with pipeline reviews
Reviewing deals in alphabetical or chronological order. Prioritize by risk and value. The first deal reviewed should be the one most likely to impact the forecast, not the one that happens to start with "A." Pipeline scoring can set the review priority automatically. Turning reviews into forecast calls. Pipeline reviews are about deal strategy and coaching. Forecast calls are about the aggregate number. Combining them into one meeting means neither gets adequate attention. Run them as separate cadences.What should a pipeline review look for?
Change, more than state. A deal sitting in proposal is useful to know. Knowing it moved into proposal yesterday is more useful. ORM snapshots every customer's pipeline daily for this reason: the movement in a deal often says more than its current fields.| Signal | What it tells you |
|---|---|
| A pushed close date | The best single sign a deal will slip. A deal that moves from one quarter to the next is less likely to close, even in commit |
| Silence | No activity, no changing data and no notes. Often the earliest warning of all |
| A buyer who stops responding | No replies to email, calls or texts is a bad sign from the seller's side |
| An amount change | Up or down, by how much, and how late in the cycle it changed |
| No change in a year | ORM treats a deal with no change in stage, close date or amount for 12 months as stale |
Who should be in the room, and when?
The review works best when the conversations happen before it. The RevOps person accountable for the forecast should talk with sales leaders every day and certainly before the weekly call, and use those conversations to challenge the assumptions in the model. A forecast built in a vacuum misses what the field already knows.
Keep ownership clear. Reps own their deals, managers own the roll-up, regional leaders own their number and the CRO owns the company forecast. Run the same definitions and rules for every team. When the forecast keeps missing, change how deals are qualified, weighted and dated rather than pressuring people into a different number.
Frequently Asked Questions
What is the best early warning sign in a pipeline review?
A rep moving a close date. A deal that slips from one quarter to the next is less likely to close, even in commit. Earlier still is silence: no activity, no data changing and no notes, and a buyer who has stopped answering email and calls.
How often should pipeline reviews happen?
Weekly at minimum. The best teams run two types: a deal-level inspection (manager and rep, 30-45 minutes per rep) and a pipeline health review (leadership team, 30-60 minutes). The deal-level review focuses on individual deals. The health review focuses on aggregate metrics.
What questions should a manager ask in pipeline review?
The five essential questions: (1) What has changed since last week? (2) What is the next step and when? (3) Who are we engaged with on the buyer side? (4) What could prevent this deal from closing? (5) What do you need help with? These questions cover progression, engagement, risk, and coaching.
How long should a pipeline review take?
30-45 minutes per rep for deal-level reviews. Focus on deals that changed status, at-risk deals, and deals in the commit forecast. Do not review every deal in every session. Healthy, progressing deals need minimal review time.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline review into prescriptive action for your team.
Schedule a Demo