How to Run a Weekly Pipeline Review in CRM: Questions, Views, and Actions

A weekly pipeline review works when the CRM does most of the talking. The manager opens a saved view, the deals appear in a fixed order, and the conversation is about evidence rather than narration. When that setup is missing, the meeting turns into a tour of each rep’s memory: deals get described in the best possible light, close dates get defended, and nothing in the record changes afterward. The difference between those two versions of the same hour is mechanical: which views are prepared in advance, which fields reps must update beforehand, which questions get asked at each stage, and whether decisions made in the room get written back into the CRM before anyone leaves.

This is a management cadence problem more than a reporting problem. Salesforce’s own guidance on pipeline reviews puts the ceiling at 30 minutes, splits the time across roughly three problem deals, and reserves the last block for action items. That structure holds up in practice because it forces prioritization. You cannot inspect 40 open deals in half an hour, so the CRM has to decide which ones deserve the airtime.

What a Weekly Pipeline Review Covers Inside the CRM

Teams often run one meeting and expect it to do three different jobs, so it helps to define the boundaries before designing the agenda. A pipeline review inspects the health of a rep’s whole book: how much open pipeline exists, how it is distributed across stages and months, what has stopped moving, and whether enough new opportunity is being created to cover the target. It is aggregate first and deal-specific second, so the deals that get airtime are chosen by the numbers rather than volunteered.

Pipeline Review, Forecast Call, and Deal Inspection Are Separate Meetings

A forecast call answers one question about the current period: will the number land, and what is the risk against it. That conversation centers on commit and best case deals, and it tends to get sharper in the final weeks of a quarter. A deal inspection goes the other direction and spends 20 or 30 minutes on a single opportunity, usually a large one, walking through the buying committee, the compelling event, the competitive position, and the close plan. Neither replaces the weekly review.

When the three collapse into one meeting, the symptoms are predictable. Early-stage pipeline gets ignored because the current quarter dominates the discussion, small deals never get inspected at all, and coaching happens in front of peers where reps are least willing to admit a deal is soft. Splitting them also fixes the calendar math: a 45 minute weekly review for a team of six, a separate 30 minute forecast call, and deal inspections scheduled only when one opportunity warrants them.

Cadence, Attendance, and Timing in the Week

Weekly is the default for teams where reps carry 10 to 25 active deals and cycles run one to three months. Longer enterprise cycles, where a deal may legitimately show no movement for three weeks, are better served by a biweekly team review plus weekly individual check-ins on named accounts. Schedule the meeting Monday or Tuesday morning. Reviews held late in the week produce action items that sit untouched over the weekend, and by Monday the buyer context has aged.

CRM Views to Open Before the Review Starts

The prep work is view design, and it is worth doing once properly rather than rebuilding filters every Monday. Most CRMs already ship the views a review needs, and the named definitions matter because they determine what lands on screen. Five saved views handle almost every weekly review.

Deals with no next activity scheduled. In HubSpot this is a preset view in the sales workspace, defined as deals with no upcoming scheduled activity. It is the highest-yield list in a pipeline review because a deal without a next buyer interaction on the calendar has no mechanism to advance. Start the deal-by-deal portion here.

Stalled or aging deals. HubSpot’s Stalled Deals view flags deals that have sat in a stage at least 20% longer than that owner’s average time in the same stage, which is a relative threshold rather than a fixed day count. Salesforce Pipeline Inspection covers similar ground by putting a red clock icon on opportunities whose Next Steps field has not been updated in seven days or more.

Past-due close dates. HubSpot calls this Stale Close Date: open deals whose close date is already behind us. These are almost always hygiene failures rather than live deals, and they inflate any weighted forecast built on top of them. Fix the date in the meeting or close the deal out.

Week-over-week field changes. Pipeline Inspection highlights changes from the previous seven days to amount, close date, stage, and forecast category, using red and green arrows, with hover detail showing what changed, when, and who changed it. Salesforce documents the full set of metric groups and filter behavior in their Pipeline Inspection reference .

Coverage by close month. A grouped view of open pipeline value by expected close month, filtered to qualified stages only, shows whether the shortfall is this month or two months out. Exclude unqualified early-stage deals from this one, otherwise coverage looks comfortable while the closable pipeline is thin.

Reps should have access to the same views. A review where the manager sees numbers the rep has not seen turns into a defensive exchange about data rather than a discussion about deals.

Rep Pre-Work: The Fields That Must Be Current Before the Meeting

Pipeline reviews fail in advance, in the 20 minutes of CRM updating that reps skip. Set a hard cutoff, for example 5 p.m. the day before, and require five fields on every deal that will be discussed:

• Stage , matching the documented exit criteria rather than where the rep hopes the deal is
• Close date , based on the buyer’s stated decision timeline
• Next step , written as a specific action with an owner and a date
• Amount , reflecting the current scope of the proposal rather than the original estimate
• Last buyer interaction , logged with what the buyer actually said or did

Reps push back on this, and some of the objection is fair. Salesforce’s State of Sales research has repeatedly found that reps spend well under half their week on direct selling, with manual data entry taking a visible share of the rest. The answer is to shrink the required field set rather than to relax the cutoff. Five fields on active deals is defensible. Twenty custom fields on every record is how CRM hygiene dies, and once the pre-work is unenforceable the review reverts to storytelling.

Pipeline Review Questions by Deal Stage

Generic questions produce generic answers, so the useful approach is two or three questions per stage tied to that stage’s exit criteria. Salesforce’s pipeline review guidance recommends exactly that: craft two to three questions for each stage, where the answers make it obvious whether the deal belongs where it sits.

Qualification and Discovery Stage Questions

Has the buyer described the problem in their own words, and is there a reason to solve it now rather than in two quarters? Does the account match the profile of your last 10 wins, and what specifically supports that? Who else has been in the room besides your initial contact? The answer you are listening for is buyer behavior rather than rep opinion. “They said budget is approved” is weaker than “the CFO joined the second call and asked about implementation timing,” and the second version can be checked against the activity record.

Proposal and Negotiation Stage Questions

Here the questions get narrower. Has the economic buyer, the person who controls the budget line, been in a conversation with you directly? What is the procurement, legal, or security process between verbal agreement and signature, and how long has that taken at similar accounts? Which competitor or internal alternative is still live, and on what basis are you being compared? If the deal slips a month, what is the reason it slips?

That last question is the most productive one in a review. A rep who can name the slip risk precisely, for instance a security questionnaire that has not been returned, is managing a real deal. A rep who cannot name any risk is usually describing a deal they have not tested.

Commit-Stage Questions Before You Bank the Forecast

Commit means the rep is on record that the deal closes this period. Three checks are enough: is there a documented, dated close plan agreed with the buyer, has every required approval been identified by name, and has the buyer confirmed the timeline in writing rather than verbally in a call. Deals that fail any of these belong in best case, and downgrading them during the review is a normal outcome rather than a failure. Forecast accuracy improves faster from honest recategorization than from pressure applied at quarter end.

Finding Stale Deals and Deciding Which Ones to Close Out

Every pipeline accumulates deals that are technically open and practically dead, and the weekly review is where they get resolved. The test worth applying is buyer-side activity rather than seller-side activity. A rep who has sent four unanswered follow-up emails has generated activity records without generating any evidence that the deal is alive, so filters built on “last activity date” alone will keep dead deals looking fresh.

Set stage-sensitive thresholds. Two weeks of buyer silence in negotiation is a serious signal, while the same gap during a procurement review at an enterprise account may be routine. Once a deal crosses its threshold, the review gives it one of three outcomes: a specific revival action with a date, a stage and close date correction, or closed lost with a reason code. Leaving it open with a vague “keep nurturing” note is not a fourth option.

Consider a mid-market team carrying $1.8M in open pipeline against a $500K quarterly target. On paper that is healthy coverage. Filter out deals with no scheduled next activity, deals whose close date has already passed, and deals with no buyer-initiated contact in 21 days, and $700K of that pipeline disappears. Real coverage is closer to 2.2x, which changes the conversation from deal coaching to prospecting volume. That recalculation takes four minutes with prepared views, and it is the most valuable four minutes in the meeting. Teams that never run it spend the quarter managing a pipeline number that was never real, then explain the miss afterward as a series of individual deal losses.

Deal hygiene rules and stage discipline are covered in more depth in our guide to managing a sales pipeline .

Pipeline Numbers to Read at the Top of Every Review

Open the meeting with four or five aggregate numbers, read in the same order every week, before any individual deal comes up. Coverage against target is the first. The common 3x benchmark assumes roughly a one-in-three win rate on qualified pipeline, so a team winning 20% of qualified deals needs closer to 5x, and using the generic ratio will hide a shortfall until it is too late to build pipeline for the period. Calculate the required ratio from your own segment-level win rate, split by segment rather than blended.

New qualified pipeline created last week is the second, because it is the only number in the review that is fully within the team’s control. Stage progression count is the third: how many deals advanced, how many moved backward, and how many did not move at all. Closed won and closed lost for the week is the fourth, with loss reasons read aloud.

Slippage is worth tracking as an explicit event rather than a state. When a close date moves, the old date is overwritten in most CRMs and the slip becomes invisible by the following week. Logging pushes with a reason code turns a fuzzy complaint about sandbagging into a pattern you can read: slips clustered at quarter end suggest optimistic dating, while slips concentrated in one stage point at a process gap. A deal whose close date has moved twice with no new stakeholder engaged and no new milestone reached is not slipping, it is stalled. Naming that difference in the review saves a quarter of false hope. For teams building forecasts from these inputs, the mechanics of weighted and category-based forecasting are worth reviewing separately in this walkthrough of CRM sales forecasting .

Logging Review Decisions Back Into the CRM

A review produces decisions, and decisions that live only in someone’s notebook have no effect on next week’s numbers. Work through the write-back in a fixed sequence, during the meeting rather than afterward.

• During the meeting, edit the deal record live as each decision is made. Stage corrections, close date changes, and forecast category moves take seconds inline, and doing it live removes any ambiguity about what was agreed.
• Create a CRM task for every action item, with a named owner and a due date before the next review. “Rep will follow up” is not a task. “Send security questionnaire to Priya by Thursday” is.
• Record the reason for any downgrade or close-out in a structured field rather than free text, so the reasons aggregate into something readable across a quarter.
• Open the next review by reading last week’s commitments back before anything else. This single habit does more for follow-through than any dashboard.

Managers running reviews inside Jira, where delivery work already lives, face an extra wrinkle: deal records and implementation tasks often sit in different systems, so review actions get logged twice or not at all. Jira-native tools such as Mria CRM keep deal, contact, and pipeline records in the same project structure as the delivery tickets, and the lighter Mria Contacts app covers teams that need structured customer records without a full pipeline. The prioritization signals used to decide which deals earn review time are covered in this piece on prioritizing deals in CRM .

Common Pipeline Review Failures and How Managers Fix Them

Most broken reviews share a small number of root causes, and each has a structural fix rather than a motivational one.

Reviews That Recap the Past Week Instead of Planning the Next One

Status recaps feel productive and change nothing. If the first 20 minutes go to describing what happened, the CRM is not doing its job, because that information should already sit in the views everyone can see before the meeting. The practical cap is two minutes of history per deal, with the remaining time spent on what will happen before the next review. One approach that works: ban retrospective openers for a month and require every deal comment to start with a date in the future. Review length tends to drop by a third while recorded action items roughly double.

Deals Chosen by the Rep Rather Than by the Data

When reps pick which deals to present, they present the healthy ones. Selection has to come from filters: largest commit deals, deals with no next step, deals aging past their stage threshold. The manager announces the list, not the rep.

Every Deal Getting Equal Airtime

A 12-deal review at three minutes each produces 12 shallow conversations. Rank by value at risk, cap the list at five or six deals, and accept that some opportunities will not be discussed this week. Nothing bad happens to a healthy deal that gets skipped.

No Consequence for Missing Pre-Work

If a rep arrives with stale fields and the review proceeds anyway, the cutoff is decorative. The workable rule is narrow: deals without current fields are not reviewed. When that leaves nothing on the agenda, the meeting becomes a one-on-one about CRM discipline, and it rarely needs to happen twice.

Coaching Mixed Into Group Inspection

Correcting a rep’s discovery technique in front of the team creates defensiveness and teaches everyone to under-share. Note the coaching point during the review and handle it in the one-on-one. Group time is for deal decisions, individual time is for skill development.

Weekly Pipeline Review FAQ for Sales Managers

A few questions come up consistently when teams redesign this cadence.

How long should a weekly pipeline review take?

Thirty minutes for a one-on-one review between a manager and a single rep, and 45 to 60 minutes for a team of six to eight. Salesforce’s guidance puts the one-on-one ceiling at 30 minutes with roughly three problem deals inspected. If your meeting consistently runs longer, the deal selection is too broad or the pre-work is not being done.

Should the whole team attend, or just the manager and rep?

Both formats work for different purposes. Team reviews build shared pattern recognition and peer accountability. One-on-one reviews get more honest answers about deal risk. Many teams run a short team scorecard segment together, then split into individual inspections.

Can a pipeline review be run asynchronously?

Partly. The aggregate numbers, stage changes, and stalled deal lists can circulate as a written update before the meeting, and that alone shortens the live session considerably. Deal-by-deal inspection is harder to do well in writing, because the useful part is the follow-up question after an incomplete answer. Distributed teams tend to land on a written pre-read plus a shorter live inspection of four or five deals.

What is the minimum CRM setup needed to run this well?

Documented stage exit criteria, a next step field with a date, a close date that reps are expected to maintain, a loss reason picklist, and saved views for stalled deals and missing next steps. Deal scoring, AI summaries, and slip tracking all help, but none compensate for a missing next step field. Enforce the five basics first, then add instrumentation.