Deal Review Template: What to Cover in Every Pipeline Review and How to Document It

The most common failure in pipeline management is running deal reviews as status conversations. The manager asks what is happening, the rep gives a narrative update, and the deal moves forward unchanged with no documented risk assessment and no confirmed next step. Two weeks later, the deal slips. This template gives managers a structured scorecard to run every deal review consistently and produce a documented output that can be tracked over time.

Step 1: Establish the Deal Basics Before the Conversation

Before the review call, the manager should pull the deal record and confirm the basics. If any of these fields are missing or stale, that is the first finding.

Deal Basics Block

Field	Expected Value
Account name
Current stage
Close date
ARR / ACV
Days in current stage
Original close date
Close date changes in last 60 days
Forecast category (commit / best case / pipeline)

Days in current stage and the history of close date changes are the two leading indicators of deal health that most CRM views hide. A deal that has been in the same stage for 45 days and has moved its close date three times in a quarter is a different conversation than a deal that is progressing on schedule.

Step 2: Run the Stage-Exit Criteria Check

Pipeline inspection is only valuable if the stages mean something consistent. For each stage, define what must be true for a deal to be there and what must happen for it to advance. Stage-Exit Criteria Table

Stage	Required Evidence to Be Here	Required Action to Exit
Discovery	Pain confirmed, stakeholders mapped	Economic buyer identified and contacted
Evaluation	Demo complete, technical requirements defined	Champion can articulate business case
Validation	POC / Business case approved	Legal and procurement engaged
Commit	Contract in legal review, verbal from economic buyer	Signed

During the deal review, confirm whether the evidence required for the current stage actually exists in the CRM. If the rep says the deal is in Validation but there is no record of procurement being engaged, that is a stage integrity problem and a risk flag.

Step 3: Score Deal Risk

Every deal in the forecast should be scored against the same risk criteria. This makes inspection consistent and gives managers a shared language for discussing deal health.

Deal Risk Scorecard

Risk Factor	Green	Yellow	Red
Economic buyer access	Confirmed meeting with EB	Champion claims EB access, unverified	No contact with EB
Champion strength	Champion articulates business case independently	Champion engaged but not self-sufficient	Champion is passive or single point of contact
Competition	Uncontested or clear preference	Competitive but vendor not identified	Losing to named competitor
Procurement / legal status	In progress, dates confirmed	Not started, champion says it's fine	Unresponsive or unknown
Timeline justification	Hard external deadline or event	Soft preference	No forcing function stated
Stage integrity	All exit criteria met	Partial evidence	No documented criteria met

A deal with multiple Red flags does not belong in commit. A deal with mostly Yellow flags needs a specific action plan. Deal risk scoring removes the subjectivity from the conversation. Instead of the manager saying the deal "feels risky," the scorecard makes the specific risk explicit.

Step 4: Confirm the Next Step

A deal without a confirmed next step is not progressing. The next step must be specific, dated, and owned by both sides.

Next Step Qualification Check

Question	Answer
What is the specific next step?
Who owns it on the buyer side?
Is it calendared?	Yes / No
Date?
What happens if this step doesn't happen?

If the next step is not calendared, the deal is not as advanced as the stage suggests. "We'll connect next week" is not a next step. "Procurement kick-off call with Maria scheduled for Thursday at 2pm" is a next step.

Step 5: Document and Tag the Output

The deal review produces three outputs: the updated risk score, the confirmed next step, and any actions the manager is taking to help. Document all three before ending the call.

Deal Review Output Block

Field	Content
Risk score (R/Y/G per factor above)
Overall deal confidence	Commit / Best Case / Pipeline / At Risk
Confirmed next step
Next step owner
Next step date
Manager action required	None / Introduction to sponsor / Resource / Escalation
Follow-up review date

This output belongs in the CRM, not in a spreadsheet that only the manager sees. The forecast call depends on the manager being able to pull a current view of every deal's health without recreating it from memory each week.

Common Mistakes

Letting the rep narrate without checking the record. The CRM is the evidence. If the rep says the economic buyer is engaged but there is no activity logged, the evidence is absent, not present. Skipping the stage-exit criteria check. If you do not have documented criteria, every stage is an opinion. The review becomes a conversation about feelings rather than facts. Not documenting the output. A deal review that produces no written output has no continuity. The next manager who reviews the deal starts from scratch. Conflating a pipeline review with a deal review. The aggregate pipeline view tells you what the coverage number is. The deal review tells you whether the denominator is real. Both are necessary and neither substitutes for the other.

Frequently Asked Questions

What is a deal review in sales?

A deal review is a structured inspection of an active opportunity by a sales manager and the AE responsible for it. The goal is to assess deal health, identify risks, confirm the next step is credible, and decide whether the deal belongs in the current forecast. It produces documented output. A status update does not.

How often should deal reviews happen?

For deals in your commit or best-case forecast, deal reviews should happen at least weekly in the final third of a quarter. For deals earlier in the cycle, bi-weekly is sufficient. The frequency should increase as deals get closer to close and as quarter-end pressure builds. Ad hoc check-ins do not substitute for a scheduled review with a consistent format.

What makes a deal review different from a pipeline review?

A pipeline review covers the aggregate shape of the pipeline: total pipeline, coverage, stage distribution, and creation trends. A deal review goes one level deeper and inspects individual deals. Both are necessary. The pipeline review tells you where the gaps are. The deal review tells you whether the deals you are counting on are real.