Pipeline Review Deck Template: The Six Slides Worth Presenting

What belongs in a pipeline review deck?

Six slides, each of which forces a decision that changes what someone does this week. Most pipeline decks fail by being complete rather than useful. They show every open opportunity in close-date order, the meeting becomes a narration exercise, and the room runs out of time before reaching the deals that need help.

The structure below inverts that. Every slide answers one question, and any content that does not change a decision gets cut. Build it once as a saved report set so it regenerates weekly without a manager spending an afternoon in slides.

What goes on the coverage slide?

Coverage by segment and by rep, with the dollar gap stated in dollars rather than as a ratio. A single company-level ratio is the least useful number in the deck because it averages away the part that is broken.

Three to five times the target is the standard range, and across ORM's customer base most companies sit around three and a half. Individual teams range far wider than that. The slide should show the ratio and the absolute gap side by side, because a team at 2.8x with a 200K gap and a team at 2.8x with a 40K gap need different conversations.

Do not let the ratio become the conclusion of the meeting. A team can carry 4x and still miss badly if the pipeline is concentrated in a few large deals, aged past its normal close window, or built on close dates that keep moving. That failure mode is covered in why the 3x pipeline coverage rule is wrong, and the mechanics of the calculation sit in the pipeline coverage definition.

What does the movement slide show?

Every deal that changed stage, amount, or close date since the last review, with the direction of the change. Those three fields are what meaningful activity means. A deal with logged calls and emails but no change to stage, date, or value has not moved. Close date pushes deserve a running count per deal rather than only the current date. At ORM the rep changing a close date is the best single signal that a deal is slipping, and a deal that moves from one period into the next is less likely to close even when the rep still calls it committed. A deal on its third push belongs on the flagged slide automatically. The deal slippage definition covers how to measure the rate across a team.

Which deals belong on the flagged slide?

Deals selected by rule, capped at six, so the list is defensible and identical across reps. Manager intuition produces a list nobody can argue with and nobody can reproduce.

Four rules cover most of what matters. Any deal whose close date moved this period. Any deal with no change to stage, date, or amount in three weeks. Any deal aged past the normal close window for its type. Any deal above a value threshold you set by segment.

Give each flagged deal ninety seconds and one output: owner, specific next action, and a date. The slide should have a blank action column that gets filled in live during the meeting, because an action captured after the fact usually never gets captured.

What does the creation slide need?

New opportunities created since the last review, split by source, against the target for the period. Coverage problems are almost always creation problems that were visible weeks earlier.

Show created count and created value separately. A month can hit its creation count while missing on value because the deals coming in are smaller, which is an early warning about average deal size. Watch for the gap between pipeline value and closed-won value. A pipeline carrying an average deal size of 80K that produces closed-won deals averaging 40K is not a coverage problem, it is a valuation problem, and no amount of extra pipeline fixes it.

What goes on the aging slide?

A count and dollar value of pipeline with no meaningful change in the last twelve months, plus everything approaching that line. Stale pipeline inflates coverage and makes every ratio on slide one look better than the business is.

Across ORM's customer base, 10 percent or more of open pipeline has gone untouched for twelve months. There is a second number worth putting on this slide: of the pipeline carrying close dates inside the quarter on day one, roughly 20 percent typically closes in that quarter. Eighty percent of the value sitting in the period on day one does not land in the period. A review that treats day-one pipeline as the quarter's revenue is starting from the wrong base.

Set a twelve-month rule and enforce it. Deals past that line get worked this week or closed out.

What should be cut from the deck?

Weighted pipeline totals, probability percentages by stage, and any slide that lists deals without a reason for listing them. A stage probability applied to a deal value produces a number that matches no real outcome, and putting it on a slide gives it authority it has not earned. The reasoning is set out in the weighted pipeline breakdown.

Also cut activity leaderboards. Call counts and email volume belong in a coaching conversation, not in a review whose purpose is deciding which deals get worked. Every slide that survives should end with someone writing something down.