A pipeline review should change the deal.

At 9:03 on Tuesday morning, a sales manager opens the CRM and asks about Northstar.

The rep starts from the beginning. They met the operations lead in May. The demo went well. Finance has questions. A proposal is out. The buyer is "positive," and the deal should close this quarter.

Nine minutes later, the manager knows the story. She still does not know whether finance has seen the proposal, what it objected to, who can approve the project, or when anybody will speak next.

The pipeline review has become a reading of the CRM with added adjectives.

A useful review has a smaller job. It finds the few deals where management attention could change an outcome, tests the claims attached to those deals, and ends with a decision. The routine update should happen before the meeting.

Put the status in a pre-read

Close's pipeline review guide asks reps to summarize what has happened, what comes next, what must happen to close, and the expected timeline. Those are sensible fields. They are also fields a manager should be able to read before the call.

Ask each rep to update a short review record by the previous afternoon:

• current stage and close date;
• what changed since the last review;
• last meaningful customer interaction;
• next customer-facing step and date;
• main risk or missing information;
• help needed from the manager.

Keep it short. A clean six-line record is better than a slide deck because it makes missing information obvious.

The record will never contain everything. It only needs enough truth for the manager to decide where to spend time.

If the team arrives with half the fields blank, do not spend 30 minutes reconstructing the deal. Name the missing context, assign the update, and move on. Repeated blanks are a process problem to solve outside the review.

Review exceptions, not every open opportunity

Salesforce recommends keeping a pipeline review between a rep and manager, with an exception for deals worked by several reps. Its suggested 30-minute agenda concentrates on three large opportunities.

Deal size is one way to choose. Change and risk are often more useful.

Put a deal into this week's review when:

• the close date, amount, or stage moved;
• the buyer missed or postponed a commitment;
• there is no dated customer-facing next step;
• a new stakeholder, objection, or competitor appeared;
• the opportunity has gone quiet;
• the rep needs a decision, introduction, or resource;
• the CRM claim no longer matches the latest conversation.

A large, healthy deal with a confirmed next step may need 60 seconds. A smaller deal that has exposed a broken qualification habit may deserve eight minutes. Review time should follow the decision to be made.

Use a 30-minute decision agenda

Here is a format that works for a manager and one rep:

Do not let the first complicated deal consume the meeting. If it needs a whiteboard and four other people, create a separate deal session. The pipeline review should reveal that need, not absorb it.

Forecast negotiation belongs elsewhere too. A rep is less likely to surface a real concern if every concern immediately becomes an argument about the number. Use the review to understand deal health. Use the forecast call to commit the number.

Ask questions that require evidence

"How do you feel about the deal?" invites a feeling.

Ask questions that can be answered with something the buyer said, did, accepted, or scheduled.

Start with, "What changed since last week?" If nothing changed, ask why the deal still deserves the same stage and close date.

Then ask what the buyer did. A seller sending a proposal is activity. A buyer inviting security to a review is progress.

"What are we assuming?" is useful when a rep says "they should," "I think," or "probably." Stop on the biggest guess and turn it into a question for the customer.

Ask who could stop the deal and what that person cares about. A friendly contact helps, but finance, IT, legal, or operations can still say no without ever appearing in the rep's notes.

Get specific about the next customer commitment. "Follow up next week" is a seller task. A useful answer names who will do what, with whom, and by when.

Finish by asking what help would change the outcome. The manager may need to join a call, find technical proof, approve a commercial move, or challenge the rep to walk away.

These questions are not a script. A manager may use two on one deal and all six on another. The test is whether the answer changes the plan or the team's confidence in it.

Keep buyer evidence beside the CRM claim

The problem with a stale pipeline is rarely the stage field alone. The stage may say "proposal" while the last call contains an unresolved implementation concern and no agreed review date.

For each reviewed deal, keep a small evidence trail:

The evidence does not need to be a transcript pasted into the CRM. A short note tied to the latest conversation is enough. It lets the next manager, rep, or forecast call see why the claim exists.

Grain's 2026 pipeline review guide makes a similar case for grounding reviews in customer conversations. The useful part is not having more recorded material. It is being able to check whether the buyer ever confirmed the timeline, problem, or next step the team is relying on.

End every deal with a written change

A review should leave a visible mark. One of these should change:

• the next action, owner, or due date;
• the stage, close date, amount, or forecast category;
• the stakeholder map;
• the risk and mitigation;
• the manager's commitment;
• the decision to remove the deal.

Write it while the reasoning is fresh. If the manager promises a security resource and the rep promises an introduction request, both belong in the record. The next review can then begin with what happened to those commitments.

Notes from buyer conversations supply the evidence. The review turns that evidence into decisions and tasks. The CRM preserves both, so next Tuesday does not begin with the same story.

A pipeline review template

Copy this into the CRM, a shared document, or the manager's review view:

• Account and rep
  Name the opportunity owner and account.
• Stage, amount, and close date
  Use the current CRM values.
• What changed
  Record movement since the last review.
• Last meaningful buyer action
  Use something the buyer said, did, accepted, or scheduled.
• Next customer commitment and date
  Name who will do what, with whom, and by when.
• Strongest evidence and largest assumption
  Keep the case for the deal beside the gap in it.
• Decision made
  Write the stage, strategy, resource, or qualification change.
• Rep and manager actions
  Give each commitment an owner and due date.

Do not reward length. A useful answer is specific enough that another manager could understand the decision without hearing the rep retell the deal.

Automate the collection, keep the judgment

The preparation is repetitive. Collecting the last meeting, latest email, open task, stage change, close-date change, and overdue next step can be automated.

The decision still belongs to the team.

Software can flag that a buyer never confirmed a date. It should not silently decide that the opportunity is dead. It can draft the meeting summary and create the follow-up task. The rep and manager should decide whether the evidence changes the stage, forecast, or strategy.

That division saves time without pretending a model owns the customer relationship.

Quick answers

What is a sales pipeline review?

A sales pipeline review is where a rep and manager work through the few opportunities that need attention. They check the evidence, make a decision, and write down who will do what next. Most teams hold one weekly or twice a month.

How long should a pipeline review meeting be?

Thirty minutes is a useful default for one manager and one rep. Review two or three exception deals rather than narrating every open opportunity.

Which deals should be reviewed?

Prioritize deals that changed, slipped, lost a next step, exposed a new stakeholder or objection, went quiet, or need a management decision. Healthy deals with current evidence may only need a brief check.

What should a pipeline review produce?

Each reviewed deal should leave with a decision, a customer-facing next step, an owner, and a date. Update any stage, close date, amount, stakeholder, risk, or forecast field that no longer matches the evidence.

Is a pipeline review the same as a forecast call?

No. A pipeline review examines deal health and helps a rep decide what to do. A forecast call rolls evidence into a revenue commitment. Separating the two makes it easier to discuss risk honestly.

What should be automated?

Automate the pre-read: recent conversation context, CRM changes, missing fields, overdue tasks, and deals without a dated next step. Keep stage, forecast, close-date, and strategy decisions reviewable by the rep and manager.

Research note: This guide builds on current pipeline-review guidance from Close, Salesforce, and Grain. LogicNotes added the exception rules, evidence table, decision agenda, review questions, and copyable record.