Pipeline Review Cadence: How Often to Review at Each Level

Teams argue about pipeline review frequency when the real problem is that one meeting is trying to do four jobs. A weekly call gets asked to inspect deals, coach reps, check coverage, and validate the forecast. It does the first badly and the other three not at all.

Separating the cadence by level fixes it. Different questions, different attendees, different data, different decisions.

How often should you review pipeline?

Weekly for deals, monthly for segment health, quarterly for assumptions, with off-cycle reviews triggered by specific signals rather than by anxiety. The exception review is the one most teams skip, and it is the one that catches problems while they are still fixable.

What belongs in the weekly rep review?

Individual deals where a decision is required, drawn from a list built before the meeting.

Not the whole pipeline. The filtered set: deals in commit, deals whose close date moved this week, deals past the typical close window for their group, and deals with no change to stage, close date, or amount in 30 days.

That last filter deserves its own rule. ORM treats a change in stage, close date, or amount as meaningful activity on an opportunity. Logged calls and notes do not qualify. The earliest sign a deal is dying is the absence of signal entirely: no activity, no data changing, no notes. From the seller's side, the same pattern shows up as a buyer who has stopped returning email and stopped picking up the phone.

Each deal on the list exits the meeting with one of three outcomes and a date. Deals that produce a status update instead of a decision were on the list by mistake.

What belongs in the monthly segment review?

Composition, not individual deals.

The monthly view asks whether the pipeline can produce the number given how it is distributed. Coverage in total is close to useless here. ORM's customers sit anywhere from 1.4x to 5x coverage, most near 3.5x, and the ratio alone says nothing about whether the quarter works.

What to inspect instead:

- Coverage by segment, since one segment at 6x can mask another at 1.8x. - Age distribution, because across ORM's customer base more than 10 percent of pipeline has gone untouched for twelve months. - Concentration, meaning the share of the number sitting in the top five deals. - Source mix, tracked as closed-won rate by source rather than volume by source. - Value gap, comparing average open opportunity value against average closed-won value.

That last item catches an error that survives most reviews. A pipeline averaging $80,000 per deal against closed-won deals averaging $40,000 is reporting twice the revenue it can deliver, and no amount of deal-level inspection surfaces it. This is the specific failure mode behind why coverage multiples mislead.

What belongs in the quarterly executive review?

The assumptions underneath the model, because that is where forecasts actually break.

The most common reason a SaaS forecast misses is that something in the business or the market changed and the forecast is still running on old assumptions. Four examples that recur:

1. A new competitor enters and creates pricing pressure, so average deal size falls. 2. Capital gets more expensive, buyers cut cost to protect earnings, and win rates drop. 3. Market uncertainty slows decisions, so the time from qualified to closed stretches. 4. Territories change and execution dips while coverage still looks healthy.

None of these appear in a deal review. They appear when you compare this quarter's win rate, cycle length, and deal size against the assumptions the plan was built on. Run that comparison every quarter and revise the coverage target rather than defending last year's multiple.

How does the review change through the quarter?

The frequency holds and the content shifts, because a quarter does not deliver revenue evenly.

Month one belongs to creation and qualification. The deals that close in month three of this quarter are largely being qualified now, and a creation shortfall in weeks one through four is still recoverable.

Month two belongs to stage progression. Deals that entered in the prior period should be clearing mid-funnel gates. This is where stalls become visible and where a close plan can still be rebuilt.

Month three belongs to close-plan execution. It is also the strongest month of most quarters, and Q2 and Q4 typically outperform Q1 and Q3. Knowing that pattern stops teams from over-reacting to a slow month one and from over-crediting a strong month three.

What triggers an off-cycle review?

Close-date movement, because it is the strongest slippage signal available.

When a rep changes a close date, the deal becomes less likely to close, and a deal that slips from one quarter into the next carries that reduced likelihood even when it stays in commit. A single change is routine. Three changes on the same deal, or a cluster of changes across a segment in the same week, is a pattern that will not wait for the monthly review.

Two other triggers earn an off-cycle conversation: a top-five deal leaving commit, and creation from a single source dropping by half against plan. Both change the shape of the quarter fast enough that waiting a month costs you the ability to respond. Treat every one of these as a deal slippage event with a documented cause.

What should never be on a review agenda?

Facts that are already in the CRM.

If the first ten minutes are spent establishing where a deal stands, the meeting has become a status report and the data standard has slipped. The rule that prevents it: a deal missing a current close date, a documented next step, and an owner does not get reviewed. It gets flagged for cleanup and returns next cycle.

Enforce that twice and reps update records before the call. Skip enforcement and the meeting quietly reverts to recitation.

How do you tell if your cadence is too heavy?

Count the decisions produced per hour of meeting time.

If most reps leave without a decision on a deal, you are reviewing too many deals or reviewing the wrong ones. Tighten the filters rather than extending the meeting. A review that covers forty opportunities and resolves four is a recitation with a calendar invite.

The other test is forecast accuracy. More review time does not improve accuracy by itself. Producing a reliable read on the shape of the quarter on day one, early enough to change the outcome, is what the cadence is for. Getting the forecast right in the last week of the quarter helps nobody, because by then the quarter has already happened.

For the short definition, see the glossary entry.