13/13 Gate✓ IQ Certified10/10?

The Forecast Call Reset — 60-Min Training

📖 3,550 words🗓️ Published Jul 31, 2026

Direct Answer

The Forecast Call Reset is a 60-minute training that converts the weekly forecast meeting from a status roll-call into a deal-inspection ritual. Managers learn a five-stage loop — categorize, inspect, challenge, reforecast, commit — pressure-test every Commit deal against MEDDPICC and buyer-side activity, and surface shortfalls six to nine weeks early instead of in the final week.

Why the weekly forecast call misses

A weekly forecast call rarely misses because reps lie. It misses because the meeting is run as a status ritual: each rep reads three numbers — Commit, Best Case, Pipeline — the manager adds them up, nobody is challenged, and the gap between the roll-up and reality stays hidden until the final 72 hours, when nothing can be done about it. The forecast looks healthy for eleven weeks and then four "Commit" deals slip in the last fortnight.

The Forecast Call Reset — 60-Min Training — figure 1

The damage is not the missed points of revenue alone; it is the *blind* miss. A number that says "we will hit 100%" and lands at 81% costs the nineteen points, plus the CRO's credibility with the board, plus next quarter's target (which gets set off the inflated figure), plus the headcount and marketing spend approved against revenue that never arrived. Worse, a board that gets blindsided discounts *every future forecast* that leader presents, so the leader over-corrects and targets get set defensively. The forecast call is the cheapest place to break that cycle because it is the only recurring meeting where the *inputs* to the number are still small enough to change.

The mechanism of most misses is mundane. A deal single-threaded to a champion who goes on leave; a deal that has sat in Commit for six weeks with the same next step ("circling back with Legal") while nobody asks why Legal produced no redlines in 40 days; a renewal-plus-expansion counted at full value where the expansion was never scoped with the buyer; a deal that would close three weeks into the *next* quarter because the close date was never checked against the buyer's fiscal calendar. Every one is catchable with a single inspection question in week three. None is a rep lying. All are a rep going un-inspected. That is the entire thesis of the reset: inspection is not measurement, it is intervention — the call exists to change the outcome of deals, not to recite a number.

The five stages of an inspection-first call

A real forecast call moves every deal through five stages of scrutiny. Most calls only do the first — they categorize, sum, and end — but the accuracy lives in stages two through five. Run weekly, the five stages form a loop where stage five's committed actions become stage two's inspection material the following week.

Categorize. Every deal sits in exactly one forecast category, and categories are definitions, not feelings. A workable standard, popularized in modern revenue operations by Clari, keeps forecast category deliberately distinct from CRM sales stage. Commit means the rep will personally be held to this deal closing this quarter: it has a confirmed close date the buyer agreed to, an identified and *engaged* economic buyer, a known paper process, and a scheduled next step on a shared calendar. Best Case is a real, winnable deal missing at least one of those four. Pipeline is an active opportunity that is not realistically closing this quarter. A deal can be in "Negotiation" in the CRM and still only be a Best Case deal if the economic buyer has never been in a room — stage measures where the deal is in your process, category measures how confident you are it closes this quarter, and the two should never auto-update each other.

The Forecast Call Reset — 60-Min Training — figure 3

Inspect. For each Commit deal, the manager runs an evidence check anchored to MEDDPICC — Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition. The discipline is the word *show*. "I'm confident in the buyer" is not evidence; "the CFO joined our call on the 12th and emailed me on the 14th" is. The most useful lens is seller-side versus buyer-side activity: seller-side (emails sent, calls dialed) predicts almost nothing because a rep can generate it on a dead deal forever; buyer-side (replies, accepted meetings, a contract the buyer opened) is what actually predicts an on-time close. Done right, inspection is a buyer-side-activity audit over a tight ten-day window.

Challenge. When the inspection surfaces a gap, the manager challenges the category calmly, aiming at the deal and never the rep. The grammar has three moves: name the evidence, not the verdict ("you have not met the EB and the next step is undated," not "you're sandbagging"); apply the written definition out loud so the *standard* is the authority; and convert the gap to a dated action so the rep leaves with a path, not a demotion. The burden of proof sits with the higher category — Commit is a claim the team will be held to, so absent evidence a deal defaults to Best Case.

The Forecast Call Reset — 60-Min Training — figure 4

Reforecast. After every deal is inspected and challenged, the manager re-rolls the number and looks at the *gap to plan*. A gap in week three is the most valuable output of the call, not bad news — it means there is time to act. The correct response is time-aware: in weeks one to four a gap means open new pipeline and multi-thread, no panic; in weeks five to nine, pull credible Best Case deals forward and accelerate paper; in weeks ten to thirteen, new pipeline cannot land, so escalate honestly and protect board credibility. The expensive mistake is treating a week-three gap as a crisis and a week-twelve gap as something to wait out — exactly backwards.

Commit. The call ends with each rep committing to their inspected number and a small number of specific deal actions. Commitment is to actions, not adjectives: "I'll work hard on Cascade" is an adjective; "I will email the CFO and book a 30-minute call by Thursday" is a verifiable action. Every committed action is written down, and next week's call *opens* by reading them back and marking each done or not-done. That verification loop — inspect, act, verify — is what converts the forecast call from a meeting into a system.

The Forecast Call Reset — 60-Min Training — figure 5

The three forecast pathologies every manager tolerates

Three predictable distortions explain most of the gap between a reported forecast and reality. A manager who can name them in the room can correct them, and none is a character flaw — all three are rational rep behavior in response to how the call is run.

Sandbagging is deliberate *under*-categorization: parking a real Commit in Best Case to stay safe or to bank a beat. It feels harmless because it produces a pleasant surprise, but it quietly destroys planning — the org under-hires, under-spends on demand generation, and mis-allocates territory against a number that is too low, and it trains your best reps to hide pipeline. Detection: a rep whose actuals chronically exceed their forecast, and complete-MEDDPICC deals that close out of Best Case because the rep "didn't want to jinx it." Coach it by rewarding honest Commits and refusing to punish the beat: "I love that you beat, and I need your forecast to be a forecast."

Happy-ears is *over*-categorization: calling a single-threaded, no-next-step deal a Commit because the buyer was friendly or the rep is behind quota. It is rarely dishonesty — it is a cognitive bias under pressure. The tell is that happy-ears reps describe deals in *sentiment* ("they love us," "great relationship") rather than *process* ("the EB approved budget," "next step booked for the 14th"). Detection: Commit deals with one contact, no economic-buyer access, no scheduled next step, and no buyer-side activity in the last two weeks. The cure is not to argue but to ask the process questions and let the absence of answers do the work — happy-ears collapses on "show me the calendar invite."

The Forecast Call Reset — 60-Min Training — figure 6

The silent slip is the most dangerous because nobody mis-categorizes anything: a deal was a genuine Commit three weeks ago, then went quiet and rode the forecast un-inspected. The champion got reorganized, budget froze, priorities shifted — and because the rep is still doing seller-side activity, the deal *looks* alive on the CRM surface. A status call asks "what category is this in?" and the deal answers honestly, "Commit." Only a question about buyer-side activity in a tight recent window surfaces it. That is exactly why the inspection set is built around buyer-side artifacts and a roughly ten-day silence threshold — it is the only mechanism that catches a deal that has died but not yet been buried.

The common trap is treating sandbagging as harmless ("at least we'll beat") and happy-ears as the only real problem. Both are forecast errors and both must be inspected in *both* directions, because minimum variance — not maximum optimism — is the goal. A rep who is consistently accurate is more valuable to the forecast than one who beats erratically, and that should be named out loud as the calibration benchmark for the team.

The Forecast Call Reset — 60-Min Training — figure 7

Running the 60-minute session end to end

The training installs the ritual in a single tightly-timed hour, best run before quarter start, after any missed quarter (the miss is the curriculum), and whenever a new front-line manager inherits a forecast call. The manager brings the live roll-up, last quarter's forecast-vs-actual by rep, and a one-page Forecast Call Card with the category definitions, the seven-question inspection script, and a slip-signal checklist.

Time	Block	Outcome
0:00–0:08	Intro + cold open — the status-call manager who missed at 81% blind, versus the inspection-call manager who caught three soft deals in week three and landed at 103%	A forecast call is an inspection ritual, not a status meeting
0:08–0:30	Teach — the five stages, the three pathologies, and a forecast-accuracy self-diagnosis	Recite five stages, three pathologies, and category definitions without notes
0:30–0:40	Discussion — category discipline, single-threaded Commits, dark deals, sandbagging detection, the slip conversation, board-credibility math	An honest audit of last quarter's forecast-vs-actual by rep
0:40–0:55	Role-play ×2 — a sandbagged Commit-grade deal, and a happy-ears single-threaded Commit; run the five stages live	Practice categorize → inspect → challenge → reforecast → commit
0:55–1:00	Debrief + written commitments — one deal to re-inspect, one inspection question to adopt, one definition to put in writing	Inspection-first habit installed in the weekly call

The Forecast Call Reset — 60-Min Training — figure 8

The two role-plays carry the training. In round one, a rep who has beaten three quarters running carries a deal with a complete MEDDPICC in Best Case "so I don't jinx it"; the manager must surface the sandbag without shaming, apply the written definition, and — critically — win agreement to the *rule*, not just move the one deal. A manager who "wins" by asserting authority ("I'm moving it") has fixed nothing. In round two, a rep behind quota carries a single-threaded, no-EB, sixteen-days-silent deal in Commit "because I have a good feeling"; the manager runs the "show me" set and lets the missing answers do the work, then separates two numbers the rep has conflated — the forecast is not a verdict on the rep, and an honest 70% with a real multi-threading plan beats a happy-ears 100% that misses.

Adoption is deliberately incremental so the ritual survives the next four calls: week one, send the written definitions; week two, run the seven-question inspection on each rep's top three Commits; week three, open the call by reading last week's committed actions; week four, run a full reforecast and present the honest gap-to-plan. Common adoption failures each have a structural fix — inspection drifting back to roll-call ("show me" every call, no exceptions), committed actions never checked (make the action board the first agenda item), and challenges turning personal (move the hardest ones to a 1:1, and never let a forecast number double as a performance verdict).

The Forecast Call Reset — 60-Min Training — figure 9

The seven inspection questions and the evidence standard

The engine of the whole reset is a short, repeatable question set the manager runs on every Commit. Each question tests one specific risk, and each has a recognizable weak answer.

*Who is the economic buyer and when did you last speak with them directly?* Tests EB engagement. Weak: "I know who it is, haven't met them yet."
*What is the paper process and who signs?* Tests procurement and legal risk. Weak: "It should be straightforward."
*What is the buyer's decision process between now and close?* Tests a real path to signature. Weak: "They said end of month."
*Show me buyer-side activity in the last ten days.* Tests momentum. Weak: "I emailed them Tuesday" (that is seller-side).
*What is the next step and what date is it on?* Tests a scheduled, mutual commitment. Weak: "I'm going to follow up."
*Is the deal multi-threaded?* Tests single-point-of-failure risk — single-threaded deals close at roughly half the rate of multi-threaded ones. Weak: "My champion has it handled."
*What would have to be true for this to slip?* Tests honest pre-mortem thinking, and is the highest-yield question in the set because it asks the rep to argue *against* their own deal. Weak: "Nothing, it's solid."

The four-part Commit test is the spine underneath every question: a confirmed close date, an identified and engaged economic buyer, a known paper process, and a scheduled next step. A deal that fails any one is a Best Case deal — not a weak Commit, a Best Case deal. The two MEDDPICC elements that most often expose a happy-ears Commit are the economic buyer (named but never engaged) and the paper process (assumed but never confirmed). Because these are *definitions*, they are auditable: either the EB has joined a call or they have not, which is what makes a challenge possible at all — you cannot challenge a feeling, but you can challenge whether a calendar invite exists.

The Forecast Call Reset — 60-Min Training — figure 10

What good looks like, and when to skip the reset

Benchmarks are the evidence base for why each stage exists, not a rep scorecard. Research from The Bridge Group, Clari, Gong, and Korn Ferry/CSO Insights consistently shows that orgs without a structured weekly inspection cadence run a wide forecast-vs-actual gap (frequently in the 20–35% range), that fewer than half of forecasted deals close as forecasted in low-process-maturity organizations, and that a meaningful slice of revenue leaks away between forecast and actual — recoverable only when the gap is caught early enough to act. Use these as a *direction*, not a verdict: win rates and coverage ratios vary by segment, so a 17% win rate is healthy for an enterprise motion and alarming for an inbound mid-market one. The real scorecard is always the team's own forecast-vs-actual history.

A framework taught without its failure modes gets over-applied, so name the limits out loud. First, inspection is not interrogation — if "show me" becomes a public cross-examination, reps stop bringing weak deals forward and hide them until the last week, the exact failure the call was meant to prevent; do the hardest challenges in a 1:1 and visibly reward the rep who voluntarily moves a deal down. Second, a brand-new rep has no forecast history to inspect and often an incomplete MEDDPICC simply because they are ramping — coach the inputs, don't grade the output, for their first full quarter. Third, transactional high-velocity motions (say, a $4K deal with a 14-day cycle and hundreds of deals a quarter) forecast as a *statistical* object off conversion rates and coverage, not deal by deal; this reset is built for considered B2B deals of roughly $25K+ ACV with multi-stakeholder, 30-day-plus cycles. Fourth, over-inspection without psychological safety *manufactures* sandbagging — if a slipped Commit is punished harder than an honest Best Case is rewarded, rational reps under-categorize everything, so the only punishable error must be miscategorization. Finally, inspection makes a number accurate, not bigger: at 1.8x coverage in week two, no amount of challenge conjures revenue, and the honest output is a demand-gen and pipeline problem, not a forecast-call problem.

FAQ

How long should the training run? Sixty minutes is the standard: eight minutes of cold open, twenty-two of teaching, ten of discussion, fifteen of role-play, and five of debrief. For a quarter kickoff, extend to ninety minutes with additional role-play rounds. The manager facilitates and the reps participate.

Who should be in the room? Front-line sales managers, second-line directors, VPs of Sales, and RevOps leaders who own a weekly forecast call. The training is designed for whoever actually runs the recurring roll-up meeting, since they are the ones who install the inspection ritual with their team.

What tools do I need to run it? None specific. The mechanics work in any CRM plus whatever forecasting and call-review tooling you already use. What matters is the discipline — written category definitions, buyer-side artifacts on demand, and a written action board read back weekly — not any particular vendor.

What's the single biggest mistake to avoid? Letting the call drift back into a status meeting. Anchor a written agenda, require "show me" evidence on every Commit, run the challenge on the deal and never the rep, and open every call by verifying last week's committed actions.

How do I measure whether it's working? Watch three things over the following quarter: forecast-vs-actual gap narrowing toward single digits, at least one honest re-categorization per rep in the first month of inspections, and reps voluntarily moving deals down a category — the surest sign the safety culture took hold.

Does this replace an LMS or certification program? No. Use self-paced LMS content for theory and this live session for the working session where deals get inspected. They are complementary: the LMS teaches the vocabulary; the forecast call is where the ritual is practiced on real pipeline every week.

Sources

flowchart TD S["The Forecast Call Reset — 60-Min Train"] S --> N0["Why the weekly forecast call misses"] N0 --> N1["The five stages of an inspection-first"] N1 --> N2["The three forecast pathologies every m"] N2 --> N3["Running the 60-minute session end to e"]

flowchart LR C["The Forecast Call Reset — 60-Min Train"] C --> H0["The three forecast pathologies every m"] C --> H1["Running the 60-minute session end to e"] C --> H2["The seven inspection questions and the"] C --> H3["What good looks like, and when to skip"] ![The Forecast Call Reset — 60-Min Training — figure 2](/assets/qa/st0037-b2.jpg)

Related on PULSE

[The Discovery Call Reset — 60-Min Training](/knowledge/st0053)
[The Channel Co-Sell Pipeline Coverage Forecast on Dynamics 365 — 60-Min Training](/knowledge/st92)
[Top 10 forecast call role-play scenarios for sales teams](/knowledge/st0552)
[Top 10 forecast call training drills for B2B sales reps](/knowledge/st0551)
[Resilience Reset: A Template for Team Emotional Regulation After Big Losses](/knowledge/st0695)

Download:

## Direct Answer

The Forecast Call Reset is a 60-minute training that converts the weekly forecast meeting from a status roll-call into a deal-inspection ritual. Managers learn a five-stage loop — categorize, inspect, challenge, reforecast, commit — pressure-test every Commit deal against MEDDPICC and buyer-side activity, and surface shortfalls six to nine weeks early instead of in the final week.

## Why the weekly forecast call misses

```mermaid
flowchart TD
  S["The Forecast Call Reset — 60-Min Train"]
  S --> N0["Why the weekly forecast call misses"]
  N0 --> N1["The five stages of an inspection-first"]
  N1 --> N2["The three forecast pathologies every m"]
  N2 --> N3["Running the 60-minute session end to e"]
```


A weekly forecast call rarely misses because reps lie. It misses because the meeting is run as a status ritual: each rep reads three numbers — Commit, Best Case, Pipeline — the manager adds them up, nobody is challenged, and the gap between the roll-up and reality stays hidden until the final 72 hours, when nothing can be done about it. The forecast looks healthy for eleven weeks and then four "Commit" deals slip in the last fortnight.

![The Forecast Call Reset — 60-Min Training — figure 1](/assets/qa/st0037-b1.jpg)



The damage is not the missed points of revenue alone; it is the *blind* miss. A number that says "we will hit 100%" and lands at 81% costs the nineteen points, plus the CRO's credibility with the board, plus next quarter's target (which gets set off the inflated figure), plus the headcount and marketing spend approved against revenue that never arrived. Worse, a board that gets blindsided discounts *every future forecast* that leader presents, so the leader over-corrects and targets get set defensively. The forecast call is the cheapest place to break that cycle because it is the only recurring meeting where the *inputs* to the number are still small enough to change.

The mechanism of most misses is mundane. A deal single-threaded to a champion who goes on leave; a deal that has sat in Commit for six weeks with the same next step ("circling back with Legal") while nobody asks why Legal produced no redlines in 40 days; a renewal-plus-expansion counted at full value where the expansion was never scoped with the buyer; a deal that would close three weeks into the *next* quarter because the close date was never checked against the buyer's fiscal calendar. Every one is catchable with a single inspection question in week three. None is a rep lying. All are a rep going un-inspected. That is the entire thesis of the reset: inspection is not measurement, it is intervention — the call exists to change the outcome of deals, not to recite a number.


## The five stages of an inspection-first call

```mermaid
flowchart LR
  C["The Forecast Call Reset — 60-Min Train"]
  C --> H0["The three forecast pathologies every m"]
  C --> H1["Running the 60-minute session end to e"]
  C --> H2["The seven inspection questions and the"]
  C --> H3["What good looks like, and when to skip"]

![The Forecast Call Reset — 60-Min Training — figure 2](/assets/qa/st0037-b2.jpg)

```


A real forecast call moves every deal through five stages of scrutiny. Most calls only do the first — they categorize, sum, and end — but the accuracy lives in stages two through five. Run weekly, the five stages form a loop where stage five's committed actions become stage two's inspection material the following week.

**Categorize.** Every deal sits in exactly one forecast category, and categories are definitions, not feelings. A workable standard, popularized in modern revenue operations by Clari, keeps forecast category deliberately distinct from CRM sales stage. Commit means the rep will personally be held to this deal closing this quarter: it has a confirmed close date the buyer agreed to, an identified and *engaged* economic buyer, a known paper process, and a scheduled next step on a shared calendar. Best Case is a real, winnable deal missing at least one of those four. Pipeline is an active opportunity that is not realistically closing this quarter. A deal can be in "Negotiation" in the CRM and still only be a Best Case deal if the economic buyer has never been in a room — stage measures where the deal is in your process, category measures how confident you are it closes this quarter, and the two should never auto-update each other.

![The Forecast Call Reset — 60-Min Training — figure 3](/assets/qa/st0037-b3.jpg)


**Inspect.** For each Commit deal, the manager runs an evidence check anchored to MEDDPICC — Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition. The discipline is the word *show*. "I'm confident in the buyer" is not evidence; "the CFO joined our call on the 12th and emailed me on the 14th" is. The most useful lens is seller-side versus buyer-side activity: seller-side (emails sent, calls dialed) predicts almost nothing because a rep can generate it on a dead deal forever; buyer-side (replies, accepted meetings, a contract the buyer opened) is what actually predicts an on-time close. Done right, inspection is a buyer-side-activity audit over a tight ten-day window.


**Challenge.** When the inspection surfaces a gap, the manager challenges the category calmly, aiming at the deal and never the rep. The grammar has three moves: name the evidence, not the verdict ("you have not met the EB and the next step is undated," not "you're sandbagging"); apply the written definition out loud so the *standard* is the authority; and convert the gap to a dated action so the rep leaves with a path, not a demotion. The burden of proof sits with the higher category — Commit is a claim the team will be held to, so absent evidence a deal defaults to Best Case.

![The Forecast Call Reset — 60-Min Training — figure 4](/assets/qa/st0037-b4.jpg)


**Reforecast.** After every deal is inspected and challenged, the manager re-rolls the number and looks at the *gap to plan*. A gap in week three is the most valuable output of the call, not bad news — it means there is time to act. The correct response is time-aware: in weeks one to four a gap means open new pipeline and multi-thread, no panic; in weeks five to nine, pull credible Best Case deals forward and accelerate paper; in weeks ten to thirteen, new pipeline cannot land, so escalate honestly and protect board credibility. The expensive mistake is treating a week-three gap as a crisis and a week-twelve gap as something to wait out — exactly backwards.


**Commit.** The call ends with each rep committing to their inspected number and a small number of specific deal actions. Commitment is to actions, not adjectives: "I'll work hard on Cascade" is an adjective; "I will email the CFO and book a 30-minute call by Thursday" is a verifiable action. Every committed action is written down, and next week's call *opens* by reading them back and marking each done or not-done. That verification loop — inspect, act, verify — is what converts the forecast call from a meeting into a system.

![The Forecast Call Reset — 60-Min Training — figure 5](/assets/qa/st0037-b5.jpg)


## The three forecast pathologies every manager tolerates

Three predictable distortions explain most of the gap between a reported forecast and reality. A manager who can name them in the room can correct them, and none is a character flaw — all three are rational rep behavior in response to how the call is run.


**Sandbagging** is deliberate *under*-categorization: parking a real Commit in Best Case to stay safe or to bank a beat. It feels harmless because it produces a pleasant surprise, but it quietly destroys planning — the org under-hires, under-spends on demand generation, and mis-allocates territory against a number that is too low, and it trains your best reps to hide pipeline. Detection: a rep whose actuals chronically exceed their forecast, and complete-MEDDPICC deals that close out of Best Case because the rep "didn't want to jinx it." Coach it by rewarding honest Commits and refusing to punish the beat: "I love that you beat, and I need your forecast to be a forecast."

**Happy-ears** is *over*-categorization: calling a single-threaded, no-next-step deal a Commit because the buyer was friendly or the rep is behind quota. It is rarely dishonesty — it is a cognitive bias under pressure. The tell is that happy-ears reps describe deals in *sentiment* ("they love us," "great relationship") rather than *process* ("the EB approved budget," "next step booked for the 14th"). Detection: Commit deals with one contact, no economic-buyer access, no scheduled next step, and no buyer-side activity in the last two weeks. The cure is not to argue but to ask the process questions and let the absence of answers do the work — happy-ears collapses on "show me the calendar invite."

![The Forecast Call Reset — 60-Min Training — figure 6](/assets/qa/st0037-b6.jpg)



**The silent slip** is the most dangerous because nobody mis-categorizes anything: a deal was a genuine Commit three weeks ago, then went quiet and rode the forecast un-inspected. The champion got reorganized, budget froze, priorities shifted — and because the rep is still doing seller-side activity, the deal *looks* alive on the CRM surface. A status call asks "what category is this in?" and the deal answers honestly, "Commit." Only a question about buyer-side activity in a tight recent window surfaces it. That is exactly why the inspection set is built around buyer-side artifacts and a roughly ten-day silence threshold — it is the only mechanism that catches a deal that has died but not yet been buried.

The common trap is treating sandbagging as harmless ("at least we'll beat") and happy-ears as the only real problem. Both are forecast errors and both must be inspected in *both* directions, because minimum variance — not maximum optimism — is the goal. A rep who is consistently accurate is more valuable to the forecast than one who beats erratically, and that should be named out loud as the calibration benchmark for the team.

![The Forecast Call Reset — 60-Min Training — figure 7](/assets/qa/st0037-b7.jpg)



## Running the 60-minute session end to end

The training installs the ritual in a single tightly-timed hour, best run before quarter start, after any missed quarter (the miss is the curriculum), and whenever a new front-line manager inherits a forecast call. The manager brings the live roll-up, last quarter's forecast-vs-actual by rep, and a one-page Forecast Call Card with the category definitions, the seven-question inspection script, and a slip-signal checklist.

| Time | Block | Outcome |
|------|-------|---------|
| 0:00–0:08 | Intro + cold open — the status-call manager who missed at 81% blind, versus the inspection-call manager who caught three soft deals in week three and landed at 103% | A forecast call is an inspection ritual, not a status meeting |
| 0:08–0:30 | Teach — the five stages, the three pathologies, and a forecast-accuracy self-diagnosis | Recite five stages, three pathologies, and category definitions without notes |
| 0:30–0:40 | Discussion — category discipline, single-threaded Commits, dark deals, sandbagging detection, the slip conversation, board-credibility math | An honest audit of last quarter's forecast-vs-actual by rep |
| 0:40–0:55 | Role-play ×2 — a sandbagged Commit-grade deal, and a happy-ears single-threaded Commit; run the five stages live | Practice categorize → inspect → challenge → reforecast → commit |
| 0:55–1:00 | Debrief + written commitments — one deal to re-inspect, one inspection question to adopt, one definition to put in writing | Inspection-first habit installed in the weekly call |

![The Forecast Call Reset — 60-Min Training — figure 8](/assets/qa/st0037-b8.jpg)



The two role-plays carry the training. In round one, a rep who has beaten three quarters running carries a deal with a complete MEDDPICC in Best Case "so I don't jinx it"; the manager must surface the sandbag without shaming, apply the written definition, and — critically — win agreement to the *rule*, not just move the one deal. A manager who "wins" by asserting authority ("I'm moving it") has fixed nothing. In round two, a rep behind quota carries a single-threaded, no-EB, sixteen-days-silent deal in Commit "because I have a good feeling"; the manager runs the "show me" set and lets the missing answers do the work, then separates two numbers the rep has conflated — the forecast is not a verdict on the rep, and an honest 70% with a real multi-threading plan beats a happy-ears 100% that misses.

Adoption is deliberately incremental so the ritual survives the next four calls: week one, send the written definitions; week two, run the seven-question inspection on each rep's top three Commits; week three, open the call by reading last week's committed actions; week four, run a full reforecast and present the honest gap-to-plan. Common adoption failures each have a structural fix — inspection drifting back to roll-call ("show me" every call, no exceptions), committed actions never checked (make the action board the first agenda item), and challenges turning personal (move the hardest ones to a 1:1, and never let a forecast number double as a performance verdict).

![The Forecast Call Reset — 60-Min Training — figure 9](/assets/qa/st0037-b9.jpg)


## The seven inspection questions and the evidence standard

The engine of the whole reset is a short, repeatable question set the manager runs on every Commit. Each question tests one specific risk, and each has a recognizable weak answer.


- *Who is the economic buyer and when did you last speak with them directly?* Tests EB engagement. Weak: "I know who it is, haven't met them yet."
- *What is the paper process and who signs?* Tests procurement and legal risk. Weak: "It should be straightforward."
- *What is the buyer's decision process between now and close?* Tests a real path to signature. Weak: "They said end of month."
- *Show me buyer-side activity in the last ten days.* Tests momentum. Weak: "I emailed them Tuesday" (that is seller-side).
- *What is the next step and what date is it on?* Tests a scheduled, mutual commitment. Weak: "I'm going to follow up."
- *Is the deal multi-threaded?* Tests single-point-of-failure risk — single-threaded deals close at roughly half the rate of multi-threaded ones. Weak: "My champion has it handled."
- *What would have to be true for this to slip?* Tests honest pre-mortem thinking, and is the highest-yield question in the set because it asks the rep to argue *against* their own deal. Weak: "Nothing, it's solid."

The four-part Commit test is the spine underneath every question: a confirmed close date, an identified and engaged economic buyer, a known paper process, and a scheduled next step. A deal that fails any one is a Best Case deal — not a weak Commit, a Best Case deal. The two MEDDPICC elements that most often expose a happy-ears Commit are the economic buyer (named but never engaged) and the paper process (assumed but never confirmed). Because these are *definitions*, they are auditable: either the EB has joined a call or they have not, which is what makes a challenge possible at all — you cannot challenge a feeling, but you can challenge whether a calendar invite exists.

![The Forecast Call Reset — 60-Min Training — figure 10](/assets/qa/st0037-b10.jpg)



## What good looks like, and when to skip the reset

Benchmarks are the evidence base for why each stage exists, not a rep scorecard. Research from The Bridge Group, Clari, Gong, and Korn Ferry/CSO Insights consistently shows that orgs without a structured weekly inspection cadence run a wide forecast-vs-actual gap (frequently in the 20–35% range), that fewer than half of forecasted deals close as forecasted in low-process-maturity organizations, and that a meaningful slice of revenue leaks away between forecast and actual — recoverable only when the gap is caught early enough to act. Use these as a *direction*, not a verdict: win rates and coverage ratios vary by segment, so a 17% win rate is healthy for an enterprise motion and alarming for an inbound mid-market one. The real scorecard is always the team's own forecast-vs-actual history.

A framework taught without its failure modes gets over-applied, so name the limits out loud. First, inspection is not interrogation — if "show me" becomes a public cross-examination, reps stop bringing weak deals forward and hide them until the last week, the exact failure the call was meant to prevent; do the hardest challenges in a 1:1 and visibly reward the rep who voluntarily moves a deal down. Second, a brand-new rep has no forecast history to inspect and often an incomplete MEDDPICC simply because they are ramping — coach the inputs, don't grade the output, for their first full quarter. Third, transactional high-velocity motions (say, a $4K deal with a 14-day cycle and hundreds of deals a quarter) forecast as a *statistical* object off conversion rates and coverage, not deal by deal; this reset is built for considered B2B deals of roughly $25K+ ACV with multi-stakeholder, 30-day-plus cycles. Fourth, over-inspection without psychological safety *manufactures* sandbagging — if a slipped Commit is punished harder than an honest Best Case is rewarded, rational reps under-categorize everything, so the only punishable error must be miscategorization. Finally, inspection makes a number accurate, not bigger: at 1.8x coverage in week two, no amount of challenge conjures revenue, and the honest output is a demand-gen and pipeline problem, not a forecast-call problem.

## Related questions

### How is forecast category different from CRM sales stage?
Sales stage marks where a deal is in your process (a milestone the rep controls). Forecast category is a probability statement about *this quarter* the rep will be held to. A deal can be in a late CRM stage and still only be Best Case if the economic buyer has never engaged. The two should never auto-update each other.

### What counts as buyer-side activity?
Anything the *buyer* does: replying to an email, accepting a meeting, forwarding your proposal internally, opening the contract, looping in procurement. Seller-side activity — emails you sent, calls you dialed — predicts almost nothing because a rep can generate it on a dead deal indefinitely. Silence past roughly ten days is a strong slip signal.

### How early can a good forecast call catch a shortfall?
Six to nine weeks, if you inspect weekly. Catching three soft deals in week three of a thirteen-week quarter leaves ten weeks of runway to open pipeline and pull Best Case deals forward. Skip inspection and the same gap surfaces in the final 72 hours, when it is unfixable.

### Is sandbagging really a problem if the team beats?
Yes. Sandbagging hides real revenue, so the org under-hires, under-invests in demand generation, and mis-allocates territory against a number that is too low — and it trains your best reps to lie low. Minimum forecast variance, not a pleasant surprise, is the goal.

### How often should this training be re-run?
At the start of every quarter, after any missed quarter, when a new front-line manager inherits the call, when forecast-vs-actual drifts past 15% for two quarters running, and before a board cycle where forecast credibility matters. Rotate the role-play scenarios each time.

## FAQ

**How long should the training run?**
Sixty minutes is the standard: eight minutes of cold open, twenty-two of teaching, ten of discussion, fifteen of role-play, and five of debrief. For a quarter kickoff, extend to ninety minutes with additional role-play rounds. The manager facilitates and the reps participate.

**Who should be in the room?**
Front-line sales managers, second-line directors, VPs of Sales, and RevOps leaders who own a weekly forecast call. The training is designed for whoever actually runs the recurring roll-up meeting, since they are the ones who install the inspection ritual with their team.

**What tools do I need to run it?**
None specific. The mechanics work in any CRM plus whatever forecasting and call-review tooling you already use. What matters is the discipline — written category definitions, buyer-side artifacts on demand, and a written action board read back weekly — not any particular vendor.

**What's the single biggest mistake to avoid?**
Letting the call drift back into a status meeting. Anchor a written agenda, require "show me" evidence on every Commit, run the challenge on the deal and never the rep, and open every call by verifying last week's committed actions.

**How do I measure whether it's working?**
Watch three things over the following quarter: forecast-vs-actual gap narrowing toward single digits, at least one honest re-categorization per rep in the first month of inspections, and reps voluntarily moving deals down a category — the surest sign the safety culture took hold.

**Does this replace an LMS or certification program?**
No. Use self-paced LMS content for theory and this live session for the working session where deals get inspected. They are complementary: the LMS teaches the vocabulary; the forecast call is where the ritual is practiced on real pipeline every week.

## Sources

- https://www.clari.com/blog/sales-forecasting/
- https://www.gong.io/blog/
- https://www.bridgegroupinc.com/blog
- https://blog.hubspot.com/sales/sales-forecasting
- https://meddic.academy/what-is-meddic/
- https://www.saastr.com/category/sales/
- https://www.joinpavilion.com/blog
- https://www.salesforce.com/resources/research-reports/state-of-sales/
- https://www.forrester.com/blogs/category/b2b-sales/

## Related on PULSE

- [The Discovery Call Reset — 60-Min Training](/knowledge/st0053)
- [The Channel Co-Sell Pipeline Coverage Forecast on Dynamics 365 — 60-Min Training](/knowledge/st92)
- [Top 10 forecast call role-play scenarios for sales teams](/knowledge/st0552)
- [Top 10 forecast call training drills for B2B sales reps](/knowledge/st0551)
- [Resilience Reset: A Template for Team Emotional Regulation After Big Losses](/knowledge/st0695)

Was this helpful?

Sources cited

bridgegroupinc.comThe Bridge Group Inside Sales & SaaS AE Metrics reports (Sudbury MA, founded 1998 by Trish Bertuzzi) — the most-cited US SaaS sales-operations benchmarking firm: annual SaaS AE Metrics + SDR Metrics + Sales Compensation reports surveying 250-500+ B2B SaaS companies; pivotal forecast-relevant benchmarks median mid-market SaaS win rate 17-22% of created pipeline, ramp 4-6 months, AE annual quota attainment median ~52-58% of reps hitting plan, pipeline coverage 3-4x for a quarter typical though 3.0x is the most-defensible figure for a healthy forecast; The Bridge Group data repeatedly shows the gap between reported forecast and actuals widens to 20-35% in orgs without a structured weekly deal-inspection cadence clari.comClari Inc (Sunnyvale CA, founded 2012 by Andy Byrne, Venkat Rangan, Kurt Leafstrand) — the category-defining revenue-operations + forecasting + revenue-intelligence platform; Clari "Definitive Guide to Sales Forecasting" + Clari quarterly Revenue Leak research; pivotal forecast methodology Clari popularized the three-tier forecast call (Commit / Best Case / Pipeline) tied to deal-level roll-up, the "forecast category" discipline distinct from CRM sales stage, and the published finding that the average B2B company loses ~14-15% of revenue annually to "revenue leak" (deals that should have closed but slipped, stalled, or were lost to no-decision); Clari estimates only ~20-25% of reps forecast within a reliable margin without manager inspection meddic.academyMEDDIC / MEDDPICC qualification framework (originated at PTC / Parametric Technology Corp in the early 1990s by Dick Dunkel and Jack Napoli; codified and taught by the MEDDIC Academy founded by Darius Lahoutifard) — Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition; the dominant enterprise-SaaS deal-qualification and forecast-inspection scoring system; pivotal forecast use a MEDDPICC score converts a rep gut-feel "I feel good about this one" into an inspectable, evidence-based commit/no-commit decision — a deal missing Economic Buyer access or a confirmed Paper Process is structurally a Best Case deal, not a Commit

Kory White

The Forecast Call Reset — 60-Min Training

Why the weekly forecast call misses

The five stages of an inspection-first call

The three forecast pathologies every manager tolerates

Running the 60-minute session end to end

The seven inspection questions and the evidence standard

What good looks like, and when to skip the reset

Related questions

How is forecast category different from CRM sales stage?

What counts as buyer-side activity?

How early can a good forecast call catch a shortfall?

Is sandbagging really a problem if the team beats?

How often should this training be re-run?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ