Forecast review meeting template: how to run a forecast call that builds confidence

The forecast review is where your number gets tested. Unlike the pipeline review, which focuses on deal health and coaching, the forecast review is about one question: are we going to hit the number this period?

If you are running forecast reviews that feel like a repeat of the pipeline review — or worse, a guessing game — this template will help you build a process that produces a confident, defensible number.

The difference between a pipeline review and a forecast review

This distinction matters because most managers blend them together and end up doing neither well.

A pipeline review inspects deal health, coaches reps, and ensures pipeline quality. It covers the full pipeline. Read more about running effective pipeline reviews.

A forecast review tests commit confidence, identifies upside and risk to the number, and produces a call you can stand behind. It focuses on deals in commit and best-case categories.

Run them as separate meetings. A weekly pipeline review with your reps. A weekly or bi-weekly forecast review with your manager or leadership.

Prep work: what to do before the forecast review

Your forecast is only as good as your preparation. Before the meeting, complete this checklist:

Data to pull

1. Current commit number vs. target — where do you stand right now?
2. Commit deal list — every deal your reps have committed to closing this period
3. Best-case deal list — deals that could close but are not yet committed
4. Closed-won so far this period — what is already in the bank
5. Deals that moved out of commit since last review — what slipped and why
6. Weighted pipeline by stage — for context on what is behind the commit
7. Historical conversion rates — what percentage of commit actually closes for each rep

Analysis to complete

• Compare each rep's commit to their historical close rate. If a rep commits 500K but historically closes sixty percent of commit, your realistic expectation is 300K.
• Identify which committed deals have the weakest evidence — low activity, vague next steps, single-threaded, or close dates that have already slipped.
• Flag any deals where the commit amount changed since last review without a clear reason.

A revenue intelligence workspace can pull most of this data automatically, giving you a pre-built view of commit health before you walk into the meeting.

The forecast review meeting agenda

This template is designed for a thirty to forty-five minute meeting between you and your manager or leadership team.

Minutes 0–5: Current position

Start with the facts. State the target, closed-won to date, current commit total, and the gap. No commentary yet — just the numbers.

Example: "Target is 1.2M. We have 340K closed. Current commit is 780K. Best-case adds another 210K. If commit holds, we land at 1.12M, which is 80K short."

Minutes 5–15: Commit inspection

Walk through the committed deals, but not all of them equally. Focus on:

• Deals that are new to commit this week — why did they move in?
• Deals with the largest dollar amounts — are they solid?
• Deals closing in the next seven days — is the close date real?
• Deals you are least confident in — be honest about which ones are shaky

For each deal you inspect, apply the deal inspection checklist. Is there recent activity? Is the next step concrete? Is the timeline tied to a customer event?

Minutes 15–22: Risk and upside

Identify the risk to the number and the upside that could cover it.

Risk deals — committed deals that could slip:

• What is the specific risk?
• What needs to happen this week to de-risk it?
• What is the fallback if it slips?

Upside deals — best-case deals that could pull in:

• What would it take to move this into commit?
• Is the customer's timeline real?
• Is the rep being conservative or is the deal genuinely uncertain?

Minutes 22–30: The call

Make the call. State your number and your confidence level. A useful format:

• Worst case: The number if your weakest commits slip
• Most likely: Your best estimate based on current evidence
• Best case: The number if upside deals pull in

Example: "I'm calling 1.05M most likely. Worst case is 960K if the two late-stage deals slip. Best case is 1.2M if we pull in the Acme and Globex deals from best-case."

Minutes 30–35: Actions and next review

Close with specific actions:

• Which deals need intervention this week?
• Which reps need support on specific deals?
• What changes, if any, to the commit list?

How to challenge commits without damaging trust

This is the hardest part of the forecast review. You need to pressure-test commits without making reps feel attacked. Here is how:

Lead with evidence, not suspicion. Instead of "I don't think this deal is real," try "The last customer interaction was twelve days ago and the close date is next week — help me understand what's happening."

Ask for the customer's perspective. "If I talked to the champion today, would they say this deal is closing this month?" This question reframes the conversation from what the rep thinks to what the customer has shown.

Normalize movement. Make it safe for reps to move deals out of commit. If pulling a deal out of commit is punished, reps will sandbar and your forecast will be unreliable. Say: "I would rather know now than be surprised later."

How to spot sandbagging vs. happy ears

Two patterns destroy forecast accuracy in opposite directions:

Sandbagging

The rep has a deal that is clearly going to close but keeps it in best-case instead of commit. Signs:

• The customer has verbally committed but the rep "wants to be safe"
• All the evidence supports the deal but the rep refuses to commit it
• The rep has a history of beating their commit by a wide margin

How to address it: Point to the evidence. "You have a signed proposal, a confirmed implementation date, and the champion said they are moving forward. What specifically would need to happen for you to commit this?"

Happy ears

The rep hears what they want to hear and commits deals that are not ready. Signs:

• The deal moved to commit after a single positive conversation
• There is no evidence of a buying process or economic buyer engagement
• The rep's close rationale is based on what the customer said in one meeting, not a pattern of behavior

How to address it: Apply the deal inspection framework. Walk through the evidence together. If the deal fails more than three inspection checks, it is not ready for commit.

Forecast review cadence

Weekly during the last month of the quarter. This is when deals move fastest and the number changes most.

Bi-weekly in the first two months of the quarter. The commit list is smaller and less volatile.

Daily stand-up in the final week of the quarter. Five minutes, commit changes only.

Common mistakes in forecast reviews

Mistake 1: Treating the forecast review as a pipeline review. Do not inspect every deal in the pipeline. Focus on commit, best-case, and the gap to target.

Mistake 2: Accepting round numbers without evidence. When a rep says "I'll do 400K this month," ask which specific deals make up that number.

Mistake 3: Ignoring historical patterns. If a rep has committed and missed three quarters in a row, the pattern matters more than the words.

Mistake 4: Only reviewing the forecast with leadership. Your reps should understand the forecast process. Include them in the logic, not just the data entry.

Mistake 5: Not adjusting the call as data changes. Your forecast should update weekly. A number you called three weeks ago is stale if the pipeline has changed.

Building a repeatable forecast process

The goal is not a perfect forecast. It is a forecast that improves over time because it is based on evidence, tested weekly, and adjusted when reality changes.

Start with this template. Run it consistently for a quarter. Track your accuracy. Adjust the process based on where you miss.

If you want to automate the prep work — pulling commit lists, flagging at-risk deals, comparing rep commit patterns to historical close rates — RepUp builds that layer for you. It gives you the evidence base you need to walk into the forecast review with confidence instead of hope. Book a demo to see it in action.