How-to guide

How to run a weekly pipeline review meeting

A weekly pipeline review is a working session, not a status update. The goal is to inspect deals, pressure-test next steps, surface risk, and leave with a tighter forecast than you walked in with. This guide gives you a repeatable 45-60 minute agenda, the pre-reads to send ahead, and the recap to send after.

Before you start

What you need.

Time: 45-60 minutes weekly

  • Clean pipeline data: every open deal has a close date, amount, stage, and documented next step from the past 14 days.
  • Consistent stage definitions: every rep agrees on the entry and exit criteria for each stage, with no "custom" interpretations.
  • Rep attendance expectation set: reps show up on time, with their own deals inspected, and ready to defend or demote them.
Run a weekly pipeline review meeting

Step by step.

  1. 1

    Send a deal inspection pre-read 24 hours ahead

    Pipeline review runtime is wasted when reps are reading their own deals for the first time. Send a pre-read 24 hours before the meeting that lists every open deal above a materiality threshold, the current close date, amount, stage, days in stage, and the last logged next step. Reps update their own records before the meeting, not during it. The pre-read also tells reps which deals they will be asked to defend on camera, so there are no surprises. Treat the pre-read as homework: a rep who shows up with stale next steps or missing close dates has already failed the meeting.

    • Export open deals above $10K (or your materiality threshold) grouped by rep.
    • Flag deals with no activity in the last 14 days or a close date in the past.
    • Share the top 5 deals per rep that will be inspected live.
    • Require reps to update close dates, amounts, and next steps before start time.
    Tip: If reps are updating deals during the review, the review has become a data-entry session. Push the hygiene work upstream.
  2. 2

    Open with coverage and movement metrics

    Spend the first 5 minutes on the numbers, not on individual deals. Pull three figures: pipeline coverage against quota for the current quarter, net new pipeline created in the past week, and total value that slipped or was lost since the last review. Coverage below 3x for the current quarter is a yellow flag; below 2x is red. If net new pipeline is below the weekly target, the problem is top-of-funnel, not deal execution. If slippage dominates, the problem is qualification and next-step discipline. Name the pattern out loud so the rest of the hour is spent on the right failure mode.

    Tip: Pipeline coverage is a diagnostic, not a verdict. Use it to decide what to inspect next, not to pre-judge the forecast.
  3. 3

    Review slipped and stalled deals first

    Walk the list of deals that slipped out of the current period or have sat in the same stage for more than 1.5x the average stage duration. For each one, ask three questions: what changed since the last close date commitment, what is the real next step with a date, and does the deal still belong in the forecast. A slipped deal with no new next step inside 7 days is a lost deal in waiting. Push reps to either reset the deal with a concrete event (champion meeting booked, procurement intro confirmed) or demote it out of the current period. Avoid letting slipped deals quietly re-slip a second time without a decision.

    • Pull every deal where close date moved right in the last 14 days.
    • Pull every deal that has been in the same stage longer than 1.5x the stage average.
    • For each: confirm a dated next step or demote the deal.
    • Log the decision in the deal record so the audit trail survives the meeting.
  4. 4

    Inspect the top 5 deals by stage

    Pick the five highest-value deals in late stage (proposal, negotiation, verbal) and inspect each for 3-4 minutes. For every deal, confirm the economic buyer is identified and has met with the rep, the business pain is documented in the deal record, the decision process and timeline are agreed with the champion, and a mutual close plan or paper process is in motion. If a late-stage deal fails any of these checks, it does not belong in late stage. Move it back and let the rep rebuild the qualification. Inspecting the top 5 by stage keeps the review focused on deals that actually move the forecast rather than everyone talking about their favorite deal.

    • Confirm the economic buyer by name, title, and last meeting date.
    • Read the documented business pain back to the rep.
    • Walk the decision process and timeline step by step.
    • Verify a mutual close plan or paper process has been shared.
    Tip: A rep who cannot answer "who signs the contract and when do they see it" does not have a late-stage deal.
  5. 5

    Call out risk signals across the board

    After deal-by-deal inspection, zoom back out and name the risk signals showing up across the pipeline. Common signals: single-threaded deals with only one contact, deals where the champion has gone dark for 10+ days, deals with no multi-threaded executive sponsor, deals pushed twice already, and deals where the amount has dropped more than 20% without a documented reason. Call out the pattern, not the individual rep. If three reps are all single-threaded on their biggest deals, that is a coaching problem for the whole team, not a performance review for one person. Agree one or two risk signals to actively coach against for the next week.

    Tip: Risk signals are leading indicators. Lost deals are lagging indicators. Spend the meeting on the former.
  6. 6

    Agree next-step commitments on every live deal

    No deal leaves the review without a dated next step and an owner. The next step is not "follow up" or "send proposal." It is a specific event with a date, a counterparty, and a verifiable outcome: "demo with VP Ops confirmed for Thursday 2pm," "redline returned by legal by Friday," "procurement intake form submitted by end of week." Reps commit live, in the meeting, and the commitments are logged against the deal record. The next review opens by scoring last week's commitments: hit, missed, or renegotiated. Commitment-tracking is what turns a pipeline review from a reporting ritual into a performance system.

    • Each inspected deal gets one dated, verifiable next step before the meeting moves on.
    • The commitment is logged against the deal, not in a side doc.
    • Next week opens by scoring the previous week's commitments.
    • Missed commitments 2 weeks in a row trigger a 1:1, not another review slot.
  7. 7

    Close with the forecast delta

    In the final 5 minutes, update the forecast number live. Compare the forecast at the start of the meeting to the forecast at the end. If the number did not move, the review did not do its job. A healthy weekly review almost always ends with the forecast moving down a little as low-confidence deals get demoted and up a little as higher-confidence commits get surfaced. State the new committed, best-case, and pipeline numbers out loud so every rep leaves with the same picture. If the forecast delta is more than 15% in either direction, flag it to the VP Sales immediately rather than waiting for month-end.

    Tip: The forecast moving is a feature of the review, not a bug. Static numbers mean reps are hiding deals, not inspecting them.
  8. 8

    Send a recap within 2 hours

    The review ends in the shared inbox, not in the meeting. Send a recap within 2 hours covering: pipeline coverage and net new, the three biggest risk calls from the hour, the demoted and slipped deals with reasons, the top 5 inspected deals and their new next steps, and the updated forecast numbers. Copy every rep and the VP Sales. The recap serves two jobs: it holds commitments in writing, and it gives absent stakeholders a 2-minute read instead of a meeting replay. Over time the recap thread becomes a weekly log of pipeline health that is more useful than any dashboard.

    • Lead with coverage, net new, and forecast delta.
    • List the top 5 inspected deals and their dated next steps.
    • List demoted or slipped deals with the reason.
    • Name the one or two risk signals being coached against next week.
Avoid

Common mistakes.

  • Running the meeting as a status update where each rep narrates their deals in turn. Inspection means the manager asks questions and the rep defends, not the other way around.
  • Reviewing every open deal. A 60-minute meeting cannot inspect 80 deals. Pick the top 5 by stage and the slipped list, and skip the rest.
  • Letting the forecast stay the same week over week. If the number never moves, reps are protecting it, not inspecting it.
  • Treating next steps as "follow up" or "send proposal." A next step is a dated event with a counterparty and a verifiable outcome.
  • Skipping the recap. Verbal commitments made in a meeting evaporate within 48 hours. The written recap is what makes the review a system.
FAQ

Frequently asked questions.

How long should a weekly pipeline review be?

45 to 60 minutes for a team of 6-10 reps. If the meeting routinely runs past 60 minutes, the pre-read is doing too little work or the manager is inspecting too many deals. Push hygiene upstream and cap the inspection list at the top 5 per stage.

Who should attend the pipeline review?

The sales manager, every rep on the team, and optionally a sales ops partner to run the numbers live. VP Sales attends monthly, not weekly, to avoid turning the review into an audience performance. Marketing and CS should not sit in; schedule a separate cross-functional revenue meeting for that.

What is a healthy pipeline coverage ratio?

For most B2B SaaS teams, 3x pipeline-to-quota for the current quarter is the working baseline. Longer sales cycles and lower win rates need higher coverage; shorter cycles with 30%+ win rates can run on 2.5x. Coverage below 2x for the current quarter means the quarter is already in trouble and the review should pivot to pipeline generation, not deal inspection.

How do you handle a rep who is unprepared for the review?

Call it out in the moment and move on. Do not spend group time cleaning one rep's data. Book a 1:1 with the rep inside 48 hours and reset expectations. Two unprepared reviews in a row is a coaching conversation, not a scheduling problem.

Should pipeline review and forecast call be the same meeting?

No. Pipeline review inspects deals and surfaces risk. The forecast call commits to a number. Running them together produces either a shallow forecast or a shallow review. Keep the pipeline review weekly and the formal forecast call bi-weekly or monthly, with the review feeding the forecast.

How do you keep reps from gaming the pipeline before the review?

Lock scoring on last week's commitments and track them week over week. Deals that keep slipping with no new events, close dates that only ever move right, and amounts that quietly rise before the review all show up in the audit trail. Reps game pipelines when the review has no memory. Track commitments and the gaming stops.

See it in Strkr

Related product surfaces.

Forecasting in Strkr Strkr CRM All Strkr features

Run tighter pipeline reviews in Strkr

Strkr gives sales managers pre-built pipeline inspection views, stage-aging flags, next-step tracking, and a forecast that moves with every commitment logged.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.