How to Run a Pipeline Review Meeting (Agenda and Template)

Most pipeline reviews sound like this:

“Did you send the email?” “Did you call them?” “Did you follow up?”

This trains reps to show activity, not judgment.

It also trains them to hide risk.

Then the leader goes deal by deal, letter by letter, live directing, while the seller defends. An hour later, the CRM looks the same, the pipeline is just as inflated, and the forecast is still a guess.

Deal Management doesn’t become productive by running harder pipeline reviews. It becomes productive when truth is safe, assumptions become facts, and sellers build plans instead of telling stories.

Here’s how to run a pipeline review that does that.

What a Pipeline Review Is For

A pipeline review has one job: keep the pipeline honest.

• What’s real?
• What’s at risk, and what are we doing about it?
• What should be killed?

That makes it different from the meetings it usually gets confused with:

Meeting	Its one job	Where it goes wrong
Pipeline review	Keep the pipeline honest: real, at risk, or dead	Activity interrogation
Deal review	Swarm one high-value deal with a cross-functional team	Reviewing five deals and solving none
Forecast call	Leave the room with a number you can stand behind	Turning into a fast deal review
1:1	Build trust, inspect and coach one seller, develop the person	Becoming a pipeline interrogation
Team meeting	Energy, alignment, learning, removing friction	Public inspection of individual deals

Keep the purposes clean. When one meeting tries to do everything, you get the worst of everything, not the best of anything.

Step 1: Define What “Pipeline” Means

Most pipeline reviews fail before they start, because nobody agrees on what counts.

Pipeline isn’t “anything in my CRM.” Set the standard:

Qualified pipeline:

• Current state is understood, and you can help.
• Desired future state is agreed upon.
• A buying or strong influencing stakeholder is engaged.

If you don’t have those three, it’s not qualified pipeline.

Upside: “We likely have a deal, but it could close this month or next quarter. We just don’t know yet.”

• You’re in Business Alignment.
• You’re green on Current State, Desired Future State and Competition, and green on Stakeholders except the economic buyer’s sign-off, which usually comes at Go / No Go.
• You’re working through the final business justification and the buying process.

This is where “we’re ready” usually belongs.

Commit: Commit is earned.

• The deal is green across all criteria.
• The timeline is nailed down.
• Milestones are tracked in a mutual action plan with mutual owners and dates, and paperwork is moving.

Commit is not “I feel good.” Commit is “the buyer is executing a shared plan with us.”

One rule governs the system: downgrade fast. The moment an agreed milestone is missed and there’s no plan to get it back on track, commit drops to upside. Missed milestones aren’t neutral. They’re data.

Step 2: Grade Every Deal on Evidence

A field in the CRM doesn’t tell you the deal is healthy. A number in the Metrics box doesn’t mean you know Metrics.

Grade the depth of what you actually know:

• Red: we don’t know.
• Yellow: we think. Assumed, not validated.
• Green: we know. Evidence, facts, client validated.

Do it for each of the six criteria: Current State, Desired Future State, Change Justification, Stakeholders, Buying Process and Competition. (If you run MEDDPICC, color each letter instead. It works the same way.)

Now the pipeline review isn’t a debate about how the seller feels. You’re looking at the same colors, and the gaps are obvious.

Remember that stage matters. A red Buying Process after the first call is completely appropriate. A red Buying Process in commit is a problem.

Step 3: Run the Weekly Keep-or-Kill Scrub

Once a week, scrub the pipeline.

Any deal without a buyer-owned next step, a dated milestone and a clear sign of momentum gets re-staged or killed.

I can’t tell you how many “keep or kill” reviews I’ve run where I gave a seller simple criteria, asked one question, keep or kill, and half the pipeline died.

Now, be careful. This isn’t about qualifying out too early. Use Deal Management to navigate in. Qualify out when there’s:

• Too much misalignment
• No compelling event
• No credible path to decision makers
• No reason the buyer journey and seller journey should continue together

Before you kill a deal, ask:

• Do you need to run another loop of discovery to gather more intel and build a stronger narrative?
• Have you made the narrative portable and shared it for feedback?
• Are you working the right power centers, or are you stuck too low?
• Is there a play you haven’t run yet that could create momentum or clarity?

And when you feel drift but aren’t sure, ask the buyer:

“Hey, I know we were both excited about this. And I also respect that priorities shift and there may be things happening internally that I don’t see. Can you level with me, should we keep working on this project right now, or should we pause and revisit when the timing’s better?”

Sometimes you get an honest “let’s pause for six months.” Sometimes you get “I’m sorry, X happened, but yes, let’s regroup next week.” Both outcomes are wins, because you get the truth.

(Please don’t use the “I’m going to close your file” line. Be human.)

A healthy pipeline protects your time and attention. It’s better to remove a deal than to leave a zombie sitting there, consuming time, attention and forecast credibility. For the full disqualification rules, read When to Disqualify a Deal.

Step 4: Run It With the Seller, Not at the Seller

Here’s the standard for every pipeline conversation. The seller comes prepared:

• Deals are pre-color-coded.
• Gaps are explicit.
• Risks are named.
• A plan exists.
• Asks are clear.

Then the leader does three things:

1. Validate the color. Hold people to the definitions. Most sellers mark things green that are really yellow, so pressure-test every green: What did we see, hear and validate that makes this green? Who confirmed it, and when? What would make it yellow again?

2. Stage-check the deal. In each stage, certain things must be true. If something was missed, name it. Decide whether it can be fixed, or whether it’s a risk you accept out loud, not as a surprise at the end of the quarter.

3. Choose one to two actions that move the deal the most. Not a to-do list. A leverage list. Then form agreements and follow up next week.

And watch your stance:

• Normalize “I don’t know.” Don’t punish it. Turn it into a plan: how will you find out, and by when?
• Challenge “I think” into evidence. “I think” isn’t wrong. It’s a flag. What makes you think that? How do we confirm it?
• Don’t criticize red. Require a plan to move it to yellow. Red isn’t a moral failure. It’s a signal.
• Ask for their plan before giving yours.
• Coach to patterns. If three deals have no executive sponsor, that’s not three deal problems. It’s one seller habit.

Why not run it as a team meeting?

Because the moment you inspect individual deals in front of peers, the dynamic changes. Sellers stop listening and start preparing to defend. The person in the hot seat learns one lesson: don’t share anything that can be used against me later.

Deal inspection belongs in 1:1s. The number belongs in the forecast call. Team meetings are for learning and alignment. Protect that.

The Pipeline Review Agenda

You don’t need another meeting on the calendar. A good pipeline review has two parts, and both fit into the rhythm you should already have.

Part 1: The seller’s weekly scrub (before the 1:1). The seller runs keep-or-kill on their own pipeline, updates the colors honestly, and comes in with the deals they want to keep, kill or get help on.

Part 2: The inspection block in the weekly 1:1 (15 minutes). A 1:1 should run 45 minutes: 10 human first, 10 on the seller’s priorities, 15 on Deal Management inspection and coaching, 5 on development, 5 on agreements. The pipeline review is that 15-minute block:

Time	Focus	Questions
3 min	What changed	What moved since last week? Did any colors change? If so, why? If not, why not?
4 min	Keep or kill	What came out of the scrub? Which deals get re-staged, killed, or a play?
5 min	Upside and commit check	Does each deal meet the definition? Is there a mutual action plan? Any missed milestones that mean downgrade?
3 min	Actions	The one or two highest-leverage actions. Who owns them, by when? Write it down, and follow up next week.

What you should see on the screen:

• The seller’s pipeline by category: qualified pipeline, upside, commit
• Each deal’s stage and color code
• Close dates and what changed since last week

Free Pipeline Review Template

Have each seller fill this in during their weekly scrub, before the 1:1:

Pipeline review: [Seller], week of [date]

• What changed since last week:
• Keep-or-kill candidates:
• Where I need help:

Deal	Stage	Category	Value	Close date	Colors (CS / DFS / CJ / SH / BP / C)	Buyer-owned next step and date	Biggest risk and my plan

Agreed actions (filled in at the end)

Action	Owner	Date

Category = Pipeline, Upside or Commit. CS = Current State, DFS = Desired Future State, CJ = Change Justification, SH = Stakeholders, BP = Buying Process, C = Competition.

For the grading definitions, grab the free Color Coding Cheat Sheet, and use the Forecast Commit Checklist for the upside and commit check.

What Changes When You Run It This Way

Pipeline quality improves because bad deals get disqualified faster and the definitions are clear. Forecast accuracy improves because truth shows up earlier. Sellers stop hiding risk and start solving it early.

And the pipeline review stops being the meeting everyone dreads.

When a single deal needs the whole team, take it to a deal review. When it’s time to call the number, that’s the forecast call. Every operating rhythm, for sellers and leaders, is in Section 3 of the book.