How to Prepare for a Pipeline Review

What does it mean to prepare for a pipeline review?

Preparation means the CRM already matches reality before anyone joins the call. The review is for judgment about deals. It is not for finding out that a close date is four months old.

Most pipeline reviews fail on inputs rather than on facilitation. The manager opens the report, the first deal shows a close date from last quarter, and the next fifteen minutes go to reconstructing what happened. Multiply that across a team and the meeting produces a corrected pipeline instead of a decision about the quarter.

Preparation splits across three roles. Reps own the accuracy of their own records. Managers own the exception list. RevOps owns the snapshot everyone argues against.

What should a rep do before the meeting?

Update stage, close date, and amount on every open deal, then write one next step with a date on it.

Those three fields carry the signal. Meaningful movement on an opportunity is a change in stage, close date, or amount, and logged calls or emails are easy to generate without a deal advancing. A rep who has updated activity counts but left the close date untouched since March has not prepared anything.

The close date deserves the most attention. When a rep moves a close date out, that single edit is the strongest available signal that the deal is in trouble, which is exactly why it needs to happen before the review and not be quietly corrected during it. See deal slippage for how those movements compound across a quarter.

What should the manager prepare?

Pull an exception list, not the full pipeline.

Reading every open deal aloud is how a sixty-minute review covers eleven opportunities and misses the ones that matter. Build the list from rules that run before the meeting.

Four filters cover most of it. Deals with no stage, close date, or amount change in 30 days. Deals whose close date has moved more than once. Deals large enough that losing one changes the quarter. Deals sitting in a late stage with a close date more than one quarter out.

The absence of any signal is its own signal. A deal with no data changing, no notes, and no buyer response is usually further gone than a deal with a documented objection.

Which numbers should be locked before the review starts?

Freeze the pipeline snapshot the night before and run the meeting against that version.

Without a frozen snapshot, the pipeline moves under the conversation. A rep updates two close dates at 8:55am, coverage shifts, and nobody can tell whether the quarter got better or the records did.

The snapshot should carry total open pipeline for the period, coverage against the number, count and value of deals with in-quarter close dates, and the aged share. Standard coverage sits between 3x and 5x, and most of ORM's customers land near 3.5x, but the ratio alone settles nothing about whether the quarter closes. Pipeline coverage hides composition, which is the argument in why the 3x pipeline coverage rule is wrong.

Include one number that most snapshots leave out. On the first day of a quarter, roughly 20 percent of the pipeline carrying in-quarter close dates actually closes in that quarter. The other 80 percent of that value does not land. A review that treats the in-quarter pipeline as mostly real is preparing for a quarter that will not happen.

How far in advance should preparation happen?

Reps finish 24 hours out. Managers and RevOps finish 12 hours out. The gap between the rep deadline and the snapshot is deliberate. It gives RevOps a clean window to calculate against records that are not moving.

What should you stop preparing?

Stop building a deck. Exported slides create a second set of numbers that disagrees with the CRM within a day, and the reconciliation costs more than the review saves.

Stop preparing commentary on deals that are progressing normally. A deal that moved a stage, has a dated next step, and has a close date the rep has never touched needs no airtime. Every minute spent confirming healthy deals is a minute not spent on the ones about to slip.

Stop asking reps to forecast confidence percentages by hand. Rep-assigned probability is a restatement of optimism, and it competes with the historical conversion data that already sits in the CRM.

How do you tell whether preparation is working?

Measure the share of review minutes spent correcting data.

Time the meeting once. If more than a fifth of it goes to establishing what a deal's current state is, prep failed and the agenda is irrelevant. Track two more signals over a quarter: the number of exception deals that arrive with no rep response, and the count of close dates edited within an hour of the meeting starting.

Both trend down when preparation becomes routine. When they do, the review stops describing the pipeline and starts changing it, which is the only reason to hold one. For the wider operating rhythm this review sits inside, see sales forecasting best practices.