How to Run a Pipeline Review That Produces Decisions, not Status Updates.
You are about to join a weekly pipeline review - either as a rep preparing for it or a manager running it
Most pipeline reviews are a slow read-through of deal names and close dates, with everyone nodding along. They feel productive but change nothing. A review that works is structured around decisions: which deals move forward, which get downgraded, which get killed, and what one action will happen before next week. That structure only works if the data is clean before the meeting starts - which means the review itself becomes the forcing function for good CRM habits.
Where it goes wrong
Reviews drag on because reps are updating records live in the meeting. Managers leave without a clear picture of the real forecast. The same deals appear week after week with no resolution. Reps learn that stale data has no consequence, so nothing changes.
What you'll be able to do
You can run or participate in a pipeline review that ends with a clear forecast, a short list of decisions made, and every discussed deal having one specific next action and owner logged in Salesforce before the meeting ends.
How to do it
Make pre-work non-negotiable
Make pre-work non-negotiable: every rep updates stages, close dates, and next steps in Salesforce before the meeting. If a rep arrives with stale data, pause and give them five minutes to update it before continuing.
Start with the deals most likely to slip or
Start with the deals most likely to slip or die - not the ones most likely to close. Spend 30 seconds per deal: keep it as is, downgrade the stage, or close it as lost. Move fast.
For every deal you discuss, the meeting ends with
For every deal you discuss, the meeting ends with one specific next action, one owner, and a date - logged as a task in Salesforce before you move to the next deal.
End with the math
End with the math: check pipeline coverage for the current quarter and next quarter, flag any deal that has been in the same stage longer than your average sales cycle, and agree on one process change for next week based on what you saw.
See the difference
A manager runs a 60-minute pipeline review. Reps talk through 15 deals. The manager takes notes in a separate doc. Three deals are flagged as at risk but no one agrees on what happens next. The meeting ends. Nothing is updated in Salesforce. The same three deals appear again next week.
A manager sends a Salesforce report link on Sunday evening and asks reps to update all open deals before Monday's review. The meeting starts with the five deals most likely to slip. Each gets a 30-second verdict. Two are downgraded, one is closed as lost, and the other two get a specific next action logged in Salesforce during the meeting. The review ends in 35 minutes. The forecast number changes. Everyone knows what they are doing this week.
You can run or participate in a pipeline review that ends with a clear forecast, a short list of decisions made, and every discussed deal having one specific ne
How you'll know it's working
You have got it when your pipeline review consistently ends in under 45 minutes and every discussed deal has a logged task with an owner and a date before the meeting closes.
Questions people ask
How do you run a pipeline review that produces decisions, not status updates?
Most pipeline reviews are a slow read-through of deal names and close dates, with everyone nodding along. They feel productive but change nothing. You can run or participate in a pipeline review that ends with a clear forecast, a short list of decisions made, and every discussed deal having one specific next action and owner
What is the most common mistake to avoid?
Reviews drag on because reps are updating records live in the meeting. Managers leave without a clear picture of the real forecast.
Hire with Assessment.
£7-10k flat fee. The methodology, delivered.
See Hire with Assessment