Pipeline Review Template: The Agenda and Deal Grid for a 30-Minute Review

What is a pipeline review supposed to produce?

A list of deals with owners, actions, and dates attached, plus a decision about where new pipeline has to come from. Most reviews produce neither. They produce a tour of the pipeline in reverse close-date order until time runs out, and then everyone leaves with the same information they arrived with.

The structure below fixes that by deciding in advance which deals get discussed and how long each portion of the meeting lasts. Every column and every agenda block exists to force a decision.

What does the agenda look like?

Four blocks, thirty minutes, with the largest share going to deals flagged by rule rather than by preference. The gap check goes first for a reason. If the period is short on pipeline, the rest of the meeting should be weighted toward creation rather than toward polishing deals that already exist.

What columns belong in the deal grid?

Nine, and none of them is a probability percentage. Two of those columns do the heavy lifting. Close date changes to date exposes the deals that keep sliding while staying in commit. At ORM the close-date change is the strongest single slippage signal in a record, and a deal that slips from one period into the next is less likely to close even when the rep still calls it committed.

The other is last meaningful change. ORM treats a change in stage, close date, or amount as meaningful activity. When none of those has moved, the deal is decaying whether or not the rep has logged calls against it.

Which deals should get pulled into the review?

Select by rule so the list is defensible and the same rules apply to every rep. Four rules cover most of what matters:

- The close date moved at any point this period. - No stage, amount, or close-date change in the last three weeks. - The deal has aged past the point where deals in its group normally close. - It sits in the top five by value for the period.

The aging rule needs a number behind it. ORM applies a twelve-month rule for most customers, and groups opportunities with a machine learning model that predicts a close curve for each group. Those curves run from one to eighty weeks, with most of the expectation landing before week twelve and very few groups carrying expectation past fifty-two weeks. Set your own threshold from your own close-time distribution rather than from a round number that feels right.

Expect the stale list to be longer than anyone wants. Across ORM customers, more than 10% of pipeline has not been touched in twelve months.

How do you keep the review from turning into a forecast call?

Ban current-period commit deals from the flagged list unless they were flagged by a rule. The gravitational pull of the current number is strong enough that without a rule, every review becomes a negotiation about this period and future pipeline never gets worked.

The two meetings answer different questions. A forecast call asks what will close. A pipeline review asks whether enough exists to close later and whether it is moving. Teams that merge them tend to run out of pipeline two periods later, having spent every meeting defending the current one.

The gap check is where the two connect. If pipeline coverage is thin for the following period, the review should end with a creation target per rep rather than with more inspection of deals that already exist. Coverage alone is a weak input, which is why the 3x coverage rule fails so often. Across ORM's customer base coverage ranges from about 1.4x to 5x, and most customers sit near 3.5x, so the ratio by itself says almost nothing about whether a specific quarter is safe.

What happens after the review?

Every flagged deal leaves with a named owner, a written action, and a date, and those get read back at the start of the next review.

That read-back is the entire enforcement mechanism. Reps quickly learn whether last week's commitments are checked. When they are, the grid gets cleaner before the meeting instead of during it. When they are not, the review becomes theater and the same deals appear on the flagged list for six weeks running.

One additional output belongs in the log: any deal the group agrees should be removed or re-dated. Cleaning those out on the spot is what keeps deal slippage from accumulating silently inside the coverage number.