What should a weekly pipeline review answer?

Jason Mesiarik
Founder and CEO, Management OS
The short answer

A weekly pipeline review exists to make decisions. It settles which deals get help and from whom, and which leave the forecast. The team's next week follows from those choices. It should show what changed since the last review and why, including what the buyer did. When it only reads the CRM back, it has become a status meeting.

8 min read · Checked 10 Oct 2026 · 5 sources

Why must a weekly pipeline review earn its time?

A pipeline review puts every seller's deals in front of the manager at once, and it takes time from everyone in the room. The return depends on what happens inside it.

In a study published in 2012, Simone Kauffeld and Nale Lehmann-Willenbrock videotaped 92 regular team meetings and coded what people said. Teams whose meetings held more problem solving and action planning were more satisfied with those meetings, and better meetings went with higher team productivity. Constructive interaction was related to the organization's success 2.5 years later. Criticizing and complaining showed links in the other direction, and stronger ones. The study shows association.

A review that decides nothing leaves each seller to decide alone. In a 2018 field study of one large multinational's industrial salesforce, Robert Mayberry, James Boles and Naveen Donthu found that sellers kept committing effort to opportunities "with little or no chance of being won." Without targeted help from managers, the authors concluded, sellers will keep spending scarce time on deals they cannot win.

92
videotaped team meetings: more problem solving and action planning went with higher team productivity.
Kauffeld and Lehmann-Willenbrock, 2012 · association only

What questions show whether your pipeline review is working?

Ask these about your own review once it has run for a while. Each one tests what the review produced. The deal work stays with the managers and sellers.

  1. What decision did the last review lead to?

    A review earns its place through what changes after it. Ask the manager who runs it what the last one decided. Listen for an answer that comes quickly and matches what the sellers tell you. A manager who describes the discussion when you asked for the decision is running a meeting that informs people and leaves the next move to chance.

  2. What changed since the last review, and what caused it?

    A pipeline that looks the same as last week either has no news or has news nobody brought. The value sits in the change and its cause. In a 1985 lab study, Garold Stasser and William Titus found that group discussion dwelt on facts members already shared. When the facts favoring the strongest of three candidates were split among the four members of each group, 18% of 38 groups chose that candidate, against 83% of 18 groups where everyone held every fact. The members were university students choosing a mock student body president. A review that rereads the screen everyone can already see spends its time on shared facts. Listen for news only the seller could have brought, and notice when a stalled deal appears every week with nothing new to say.

  3. Which deals need help, and from whom?

    A review should send help to specific deals from specific people, such as a manager walking a site with the seller or an operations lead answering a buyer's scope question. Listen for requests that name the person and the deal. Sellers may ask less often than their manager expects. In four studies published in 2010, Vanessa Bohns and Francis Flynn found that people in a position to help underestimated how much embarrassment keeps others from asking, so they expected more requests than came. The studies looked at asking for help in general, outside sales. A review where nobody needs help may have sellers who would rather not say so in front of the room.

  4. Which deals should leave the forecast?

    Taking a deal out of the sales forecast is a decision, and a review that never makes it carries weight it cannot see. Sellers hold on for understandable reasons. The 2018 Mayberry study found the pull to keep investing was stronger among less able sellers, so the people who most need a second view are the least likely to step back on their own. Listen for deals that leave the forecast during the review, each with a reason the leader can repeat. When the forecast after the review matches the forecast before it, the review never touched it.

  5. What do sellers get out of the review?

    Sellers give the review their time, and it should give something back, such as help on a stuck deal or a decision they were waiting for. Ask a few sellers what the last review gave them. In two surveys of working adults, with 201 and 785 people, Steven Rogelberg and colleagues found in 2010 that satisfaction with meetings predicted overall job satisfaction, even after accounting for other parts of the job such as pay and supervision. The link was stronger for people who attended more meetings. Both studies were surveys, so they show association. A seller who describes the review as a report to management has told you who it serves.

The question under all five

"If we cancelled the next review, what decision would not get made?"

It comes last because it gathers the five above into one test. A review that produces decisions and sends help to deals has a quick answer. If nothing would wait, the meeting has become a status update, and its time belongs back with the sellers and their buyers.

What are the signs of a useful weekly pipeline review?

Good signs

  • The manager can say what the last review decided.
  • Deals leave the forecast during the review, and everyone hears why.
  • Most of the talk is about what changed and why.
  • Help reaches the deals it was promised to.
  • Sellers bring the deals they are worried about.

Warning signs

  • Sellers read their CRM entries aloud.
  • The same deals come up week after week with the same next step.
  • The forecast leaves the room exactly as it came in.
  • Each review starts as if the last one never happened.
  • Sellers treat the review as a deadline for updating the CRM.

Case study Fictitious numbers

A PE-backed janitorial services company has 14 sellers and two front-line managers. Sellers renew janitorial and day-porter agreements and bid on new multi-site contracts. The VP of Sales has held a weekly pipeline review for two years. Before the new quarter starts, she reads the notes from the last ten reviews.

Across those ten reviews, sellers walked through a deal 120 times. In 104 of those walk-throughs, the deal ended where it started. Twelve ended with a named person asked to help. Four ended with a deal taken out of the forecast.

Deal walk-throughs
120
across the last ten reviews
Ended where they started
104
same deal, same next step
Ended in a decision
16
12 got help, 4 left the forecast
What 120 deal walk-throughs produced
  • A named person asked to help (12)
  • Taken out of the forecast (4)
  • Ended where it started (104)

Two renewals slipped out of the quarter while the forecast carried both until the final week.

The same renewals came up week after week with the same next step. Two of them slipped out of the quarter, and the forecast carried both until the final week. When she asks sellers what the review gives them, the most common answer is a chance to show leadership their CRM is current. Two sellers refer to it as the readout.

She puts the closing question to both managers. Neither can name a decision the next review would make that would otherwise wait. She keeps the review. Her next conversation with the managers starts with the two renewals that slipped, and with what the review would have had to decide for the team to act on them in time.

FAQ

What is the purpose of a pipeline review?

A pipeline review turns what the team knows about its open deals into decisions. The main ones are which deals get help and which leave the forecast. It is also where a manager hears what changed since the last review and why. A review after which no deal is handled any differently has worked as a report, and the CRM could have delivered that without the meeting.

What is the difference between a pipeline review and a forecast review?

A pipeline review looks across open deals and decides where help and attention go. A forecast review looks at the deals expected to close in the period and settles the number the leader will stand behind. The two share deals and evidence, and they often overlap. Each should still end in its own decisions, and the second depends on the honesty of the first.

Why do pipeline reviews turn into status meetings?

Reading the CRM aloud feels productive and asks little of anyone. Discussion drifts toward what everyone already knows, as Stasser and Titus found in a different setting, and new or uncomfortable news takes effort to raise. Sellers who see a weak deal draw criticism learn to keep the next one quiet. Over time the meeting keeps its place on the calendar and loses its decisions.

Can a dashboard replace a pipeline review?

A dashboard can show where every deal sits and what moved, often faster than a meeting can. It cannot agree to send a manager to a buyer or persuade a seller to let a deal go. Those choices need the people who own the deals. A good dashboard frees the review to spend its time on decisions, which is the part only the team can do.

Sources

  1. Meetings Matter: Effects of Team Meetings on Team and Organizational Success (Simone Kauffeld and Nale Lehmann-Willenbrock, Small Group Research, April 2012) checked 10 Oct 2026
  2. An escalation of commitment perspective on allocation-of-effort decisions in professional selling (Robert Mayberry, James Boles and Naveen Donthu, Journal of the Academy of Marketing Science, September 2018) checked 10 Oct 2026
  3. Pooling of Unshared Information in Group Decision Making (Garold Stasser and William Titus, Journal of Personality and Social Psychology, 1985) checked 10 Oct 2026
  4. "Why didn't you just ask?" Underestimating the discomfort of help-seeking (Vanessa Bohns and Francis Flynn, Journal of Experimental Social Psychology, 2010) checked 10 Oct 2026
  5. Employee satisfaction with meetings: A contemporary facet of job satisfaction (S. G. Rogelberg, J. A. Allen, L. Shanock, C. Scott and M. Shuffler, Human Resource Management, 2010) checked 10 Oct 2026

Ask these questions of your own number.

Management OS tells the revenue leader where to act to hit the number: which deals are real, who needs coaching and how, and where your own involvement moves it.

Or start a 30-day trialCard required. Cancel before day 30 and pay nothing.