How to Write a Deal Review Your VP Will Actually Read

The VP's perspective (which most AEs never consider)

When you walk into a deal review, you're thinking about your deal. One deal. The nuances, the context, the champion relationship, the history. You've been in this deal for four months. You know it cold.

Your VP is thinking about 30 deals. They have a two-hour block on their calendar, six AEs scheduled back-to-back, and a forecast call with the CRO on Friday. They are not here to understand the nuances of your Acme deal. They are here to answer one question: can I put this number in my commit?

That context changes everything about how you should write a deal review. The goal isn't completeness. The goal is giving them the answer to that question in 90 seconds, with enough evidence behind it that they don't need to follow up.

The 5 questions every VP asks (and how to answer them in writing first)

VPs don't have a secret rubric. They ask the same five questions on every deal, in every review, at every company. The AEs who know this prepare answers in advance. The ones who don't answer in real time — which means they're assembling a story instead of presenting facts.

1. Why this deal, why now?

Not "why did we start this deal nine months ago." Why is this deal closing this quarter? What changed on the buyer's side that makes now the right moment? If your answer is "end of quarter pricing" — that's a you-reason, not a them-reason. VPs know the difference. The answer they want: a specific business event on the buyer's calendar that creates urgency. Board presentation, compliance deadline, headcount freeze lifting, new budget cycle. Something real.

2. What's the customer's measurable pain?

Not the category of pain. The number. "They're losing 6 hours per week per rep to manual forecast prep, across 14 reps — that's 84 hours of selling time gone every week." That's a measurable pain. "They need better forecast visibility" is a category. VPs can't build a business case around a category. If you can't name the number, you don't actually know the pain — you know the symptom.

3. Who signs and what's their stated process?

Not who you think signs. Who has told you they sign, and what have they told you the process looks like? Legal, procurement, IT security, executive sign-off — every step that has to happen before a signature. If your VP asks "has procurement seen this?" and you say "not yet," that's a slip risk they just identified before you did. Get there first.

4. What's the most likely reason this slips?

This is the question most AEs dodge. They either say "nothing, it's solid" — which is a red flag, not a reassurance — or they pick a risk so small it's obviously cover. VPs want the real one. The CFO who hasn't been engaged directly. The legal review that takes four weeks and was just submitted. The champion who's internally blocked on budget until next month. Name it. Own it. Say what you're doing about it.

5. What's the next proof point and when?

This is where a deal review becomes a commitment, not a report. The next proof point is a specific buyer action that confirms the deal is real: legal returning redlines, CFO agreeing to a call, procurement issuing a PO number, champion sending a signed mutual close plan. You name the action, the person, and the date. If your VP hears "I'm following up with them" — that's not a proof point. That's a prayer.

The one-page deal review format

You can write a complete deal review on one page. If it's longer, you're narrating instead of reporting. Here's the format — copy it directly:

That's it. Eight fields. Every one of them forces a specific answer — no room for vague language, no space for optimism without evidence. When you hand this to your VP, they have everything they need to put your number in their forecast without a follow-up question.

The CONFIRMED / ASSUMED / AT RISK evidence tagging comes from the Enterprise Deal Review Template framework we've written about before. It's the fastest way to show a VP exactly how much of your deal is fact versus belief.

Three things to cut from your deal review immediately

Most deal reviews fail not because they're missing information, but because they're full of the wrong kind. Three categories of content that get AEs in trouble:

Cut This	Why It Fails	Replace With
Vague language "Strong interest," "great relationship," "positive momentum"	Zero signal. Every AE says this about every deal. It tells your VP nothing about whether the deal is real.	Specific buyer behaviors. "Champion attended our executive briefing on May 6 and introduced us to their CFO on the same call."
Internal acronyms "Went through MEDDIC on Acme, POC complete, MBO tied"	Your methodology is your sales process. Your VP doesn't need to hear the framework — they need the output.	Plain language facts. "Budget is confirmed at $180K. Economic buyer is the CFO, confirmed verbally on May 3rd call."
Optimism without evidence "I think this is going to close." "I feel good about this one."	The most dangerous sentence in a deal review. High confidence + low evidence is how deals get committed and then slip in week 11.	Evidence-backed conviction. "Champion has a signed mutual close plan. Legal received contract Friday. I'm committing this at $180K."

How forecast accuracy compounds when deal reviews are written this way

The one-page format isn't just a communication tool. It's a forcing function on your own thinking. The act of filling it out — before you walk into the review — surfaces the gaps you'd otherwise discover mid-conversation with your VP watching.

AEs who prepare structured deal reviews before forecast calls — not summaries, not CRM printouts, but evidence-audited one-pagers — consistently call their numbers within 10% of actual. AEs who wing it with a narrative in their head miss by 20–40%. Not because they're worse at selling. Because they never forced themselves to distinguish confirmed from assumed.

Forecast accuracy isn't a math problem. It's an evidence problem. The AEs with the best forecast accuracy aren't better at predicting the future — they're better at knowing what they actually know versus what they're guessing.

If you want to see how the evidence tagging works in practice, the Acme Q3 Deal Review Pack is the live example — a $180K deal with every item tagged CONFIRMED, ASSUMED, or AT RISK, with the risk section and commit narrative CommitTrack generates automatically.

Related: What Your VP Actually Wants to Hear on Forecast Calls breaks down the four-criteria scorecard your VP is running on every deal review — specificity, commitments, risks, follow-through. The format above is designed to address all four.