A weekly pipeline review is a recurring check-in where the team reviews open deals, flags at-risk opportunities, and forecasts the next 30 days ( Salesforce). This guide walks through the three standing checks that the same source lists for every week, and shows where each one fits in the meeting.
Key takeaways
- cover open deals, at-risk flags and the next 30 days in every weekly review.
- run the same three standing checks each week: CRM hygiene, 1:1s grounded in real data, and dashboards visible to the whole team, so the same list is used every time.
- open the record for each deal on the agenda before the meeting starts, and write down the few details the team needs in order to discuss it.
- use each 1:1 to talk through the actual deal record instead of a general impression of the pipeline, and note which action came out of the conversation.
- when a check gets skipped, name it at the start of the next review and say why it was skipped, so the gap stays visible to everyone.
Why the weekly pipeline review needs a fixed rhythm
A fixed rhythm matters because the three standing checks work as a set only when they run in the same slot each week. A consistent slot tells sellers when their records need to be current, so the review starts from the same kind of information every time. Changing the slot from week to week makes it harder to keep the checks in place.
According to Salesforce, weekly pipeline reviews, even 30 minutes long, also keep the team aligned on priorities. A short meeting can be a practical starting point for a team that has not yet built the habit, and a longer one is a choice the team makes for itself.
Two publisher points anchor this guide. The table shows each one with the wording the publisher uses.
| Publisher | Documented point | Source wording |
|---|---|---|
| Salesforce | Weekly items for the pipeline review | Every week: CRM hygiene checks, manager 1:1s grounded in real data, dashboards visible to the whole team. |
| Mindtickle | Stalled B2B purchases | Forrester's State of Business Buying, 2024 reports that 86% of B2B purchases stall at some point before closing |
A printed copy of the three checks, kept with the meeting notes, gives the team one reference to read from each week.
Before the review: check the CRM data and the shared view
The first check is the data. According to Salesforce, 76% of SMB customers say their teams operate off the same CRM view. That figure is a reason to agree on one shared view of the pipeline, not a benchmark for your team, because it describes SMB customers in general.
Before the meeting, open each deal on the agenda and read its record from start to finish. A useful practice is to choose the few details on each record that the team needs in order to discuss the deal, and to write that list down. The list should stay short enough to finish before the meeting starts. For the notes themselves, see sales call review notes.
Each seller can confirm, before the review, that every open deal they plan to bring is in the shared view. A deal that appears in one seller's notes but not in the shared view can be added or removed ahead of the meeting, so the discussion uses one set of records. The data check is also a good place to notice a deal with no recent update, and a short note on that deal can be added before the meeting.
Service handoffs need a check of their own. If a deal moves between a sales owner and a service owner, the two people can confirm that they are looking at the same record before the review begins.
During the review: open deals, at-risk flags and the next 30 days
A useful order is to start with open deals, move to at-risk flags, and close with the next 30 days.
The 86% figure from Mindtickle, drawn from Forrester's 2024 report, describes B2B purchases, not the deals on your own list, so it is a reason to check flags rather than a forecast for your pipeline.
Buying groups add another reason to check. According to Mindtickle, the average B2B purchase today involves 13 stakeholders. When a deal is flagged, the seller can count the people named on it and note which of them they have spoken with recently. A deal with many people involved has more people to coordinate, so the flag should name the coordination gap.
Each flagged deal benefits from one sentence that states the reason for the flag. Writing that reason into the record lets the next review see whether it changed.
According to Salesforce, the review forecasts the next 30 days. A useful habit is to limit the look-ahead to deals the team can name, with one owner for each. For each deal in the look-ahead, the owner can say whether the next step falls inside the 30 days or beyond them. A deal with no dated next step can be marked in the record, so the next review starts from that gap instead of discovering it in the meeting.
Illustrative example: one 30-minute review
Suppose a team of 5 sellers has 10 open deals on the agenda. Before the meeting, the manager spends 2 minutes on each record and writes down the 3 details the team needs. In the review, the team gives about 10 minutes each to at-risk flags, to the next 30 days and to the open-deal list. Any flag with no dated next step is marked in its record. This example is illustrative only and is not a benchmark.
After the review: 1:1s grounded in real data
Each manager 1:1 can open with a named deal and its current record, rather than a general impression of the quarter. That record gives both people the same starting point for the conversation.
Before a 1:1, the manager can open the seller's open deals in the shared view and pick one record to discuss, rather than reading the whole list aloud. A single record gives the conversation a clear subject and keeps the time spent on it focused. For a fuller agenda, see Sales One-on-One Agenda for Coaching Software Sellers.
Each 1:1 can end with one or two actions, and each action can be tied to the deal record where it should show up. At the next review, the team can check whether each action appears in that record, and name any action that did not.
The 1:1 is kept apart from the team status update. The status update covers the whole team using a shared view, while the 1:1 covers one seller and their own deals. Holding the two in different slots keeps each conversation on its own subject.
Coaching belongs inside the 1:1, and the deal record gives the manager a specific moment to discuss. One stage decision on the deal, explained by the seller, is a practical place to begin the conversation.
According to Salesforce, effective sales coaching can increase sales performance by up to 8%. The figure is a ceiling, not a guaranteed gain for any one team. It is a reason to treat the 1:1 as a regular place to practice coaching on real deals.
If a 1:1 surfaces a stage change, the seller can update the record before the next review, so the change is visible to the whole team at that meeting.
Dashboards the whole team can see
According to Salesforce, dashboards visible to the whole team are one of the three weekly items. For this check, the question is whether the seller and the manager can see the same dashboard during the review.
Before the meeting, the manager can agree on which dashboard the team will open and write its name at the top of the agenda. Each seller can confirm that they can open that dashboard before the meeting starts, so the first minutes of the review are not spent on access.
During the review, the manager can read the dashboard figures in the same order as the agenda, so the discussion moves from records to numbers without jumping back and forth. Opening the same dashboard for everyone keeps the discussion on one set of numbers. A shared dashboard also does not correct records that are out of date, so the record check still comes first.
If a seller asks for a different view, the manager can check whether the difference comes from a record that needs updating or from a question about the deal. Settling the record first, and then returning to the dashboard, keeps the review in order.
A figure that prompts a question can be written in the notes with the deal's name beside it. That note then carries into the 1:1 for the seller who owns the deal.
Keep the dashboard list short. One dashboard named at the top of the agenda is enough to begin, and a second one can be added only after the team has used the first for several reviews.
Mistakes that turn the review into a status meeting
A common drift is a review that becomes a list of updates with no checks. Watch for these patterns:
- reading deal names aloud without opening the records first.
- skipping the at-risk flags because the list looks healthy.
- treating the 1:1 as a status update instead of a conversation about one deal.
- letting a skipped check go unnoticed for several weeks.
A manager can spot each one by reading the three checks aloud at the start of the meeting.
Another pattern is a review that runs past its slot without any decision about the open items. Ending each review by listing the open items and an owner for each keeps the next meeting focused. Each seller can also get a fixed slot in the review, with any deal that needs a longer conversation moved into a separate 1:1.
If time runs short, protect the at-risk flags first, since they show which deals need a conversation this week. The open items can then carry into the next review with their owners named.
Your next step is to put the three standing checks, CRM hygiene, 1:1s grounded in real data, and team dashboards, on the agenda of your next pipeline review, and to note which one you skipped.
Related guides: Check 7 deal fields before your next coaching review · Deal stage progress: 7 checks for weekly coaching · Exit criteria: 5 checks for sales pipeline stages.
FAQ
What does a weekly pipeline review cover?
It covers open deals and at-risk opportunities, and it forecasts the next 30 days, according to Salesforce.
How long should the weekly review take?
Even a 30-minute review keeps the team aligned on priorities, according to Salesforce, so the length can fit the team's needs.
Why check CRM data every week?
Because CRM hygiene checks are on the weekly list, according to Salesforce, the check belongs on the agenda every week.
Can the review help with coaching?
Yes. According to Salesforce, weekly pipeline reviews help managers spot coaching opportunities before they become missed quotas. Effective sales coaching can increase sales performance by up to 8%, according to the same source.