The Forecast Call Reset: Running a Weekly Deal-Inspection Meeting That Kills Sandbagging and Happy-Ears — a 60-Minute Sales Training

Direct Answer

A weekly forecast call misses not because reps lie, but because the meeting is a status ritual — reps read Commit / Best Case / Pipeline numbers, nobody is challenged, and the gap between the roll-up and reality stays hidden until the final 72 hours. The fix is to convert the call into a deal-inspection ritual built on five stages — CATEGORIZE → INSPECT → CHALLENGE → REFORECAST → COMMIT — where every Commit deal is pressure-tested against an evidence standard (MEDDPICC plus observable buyer-side activity), every category is earned and not asserted, and the manager's job is to change the outcome of deals, not to recite a number.

This training is a fully runnable 60-minute live session that installs that ritual, names the three forecast pathologies every manager tolerates (sandbagging, happy-ears, the silent slip), and ends with each manager committing to one deal, one inspection question, and one written category definition.

Run it before quarter start, after any missed quarter, and whenever a new manager inherits a forecast call.

TL;DR

• Problem: The weekly forecast call is run as a status meeting; numbers are read, not inspected, so a shortfall surfaces only in the final week when nothing can be done about it.
• Framework: The 5-Stage Forecast Call — CATEGORIZE, INSPECT, CHALLENGE, REFORECAST, COMMIT — turns the call into an evidence-based deal-inspection ritual.
• Pathologies: Sandbagging (deal under-categorized), happy-ears (deal over-categorized), and the silent slip (deal goes quiet and rides Commit un-inspected).
• Format: A 60-minute training — Intro 0:00-0:08, Teach 0:08-0:30, Discussion 0:30-0:40, Role-Play 0:40-0:55, Debrief 0:55-1:00.
• Outcome: Managers leave able to recite the 5 stages and 3 pathologies, run a live inspection, and surface a shortfall 6-9 weeks early — early enough to fix it.

📊 The Pulse Training

Who this is for: Front-line sales managers, second-line directors, VPs of Sales, CROs, and RevOps leaders who run a weekly forecast call — the recurring meeting where reps roll up Commit / Best Case / Pipeline numbers and the team commits to a quarter. Per The Bridge Group, Clari, Gong, and CSO Insights / Korn Ferry: median B2B SaaS orgs without a structured deal-inspection cadence run a 20-35% gap between reported forecast and actuals, fewer than ~50% of forecasted deals close as forecasted in low-process-maturity orgs, and the average company loses ~14-15% of revenue to "revenue leak." Run this before quarter start, after any missed quarter, and when onboarding a new manager into the forecast call.

What teams leave with: A 5-STAGE FORECAST CALL (CATEGORIZE → INSPECT → CHALLENGE → REFORECAST → COMMIT) plus the 3 forecast pathologies every manager tolerates (sandbagging, happy-ears, and the silent slip). Plus verbatim inspection questions, two role-plays (a rep sandbagging a Commit-grade deal into Best Case, and a rep happy-ears-ing a single-threaded Pipeline deal into Commit), a Commit/Best-Case/Pipeline definition card, a MEDDPICC-anchored deal-inspection script, and a forecast-accuracy self-diagnosis.

The manager brings: (1) The live roll-up — every rep's Commit, Best Case, and Pipeline for the current quarter. (2) The Forecast Call Kit — category definitions, the 7-question inspection script, MEDDPICC scorecard, and a slip-signal checklist. (3) Last quarter's forecast-vs-actual by rep, so the room can see who is chronically high (happy-ears) and who is chronically low (sandbagging).

MEETING AGENDA — 60 MINUTES

🎯 Bottom Line

Your forecast is not wrong because your reps are dishonest. It is wrong because the weekly call is a status meeting — reps read numbers, nobody gets challenged, and the gap between the roll-up and reality stays hidden until the final week. A real forecast call is a deal-inspection ritual: every Commit deal is pressure-tested against an evidence standard (MEDDPICC plus observable buyer activity), every category is earned not asserted, and the manager's job is to change the outcome of deals, not to recite a number.

Run the 5-stage call every week and you surface a shortfall 6-9 weeks early — early enough to fix it. Skip it and you find out in the last 72 hours, when nothing can be done.

SECTION 1 — INTRO + COLD OPEN (0:00-0:08)

🟡 Coach Note

Do not open this meeting by reading the roll-up number. Open with the two-manager story and the cost of a blind miss. Eight minutes. Hard stop at 0:08. The point of the cold open is to make the room feel the difference between a status meeting and an inspection meeting before you teach the model.

1.1 The cost, then the story

A missed forecast is not just a missed number. It is a missed number the leadership team did not see coming. Per SaaStr's long-running writing on the CRO and VP-of-Sales role [SaaStr, "Why Your VP of Sales Will Likely Fail" and related forecast posts], the single most damaging credibility event between a revenue leader and a board is a shortfall that surfaces in the final week — because by then there is no time to build pipeline, accelerate deals, or reset expectations [SaaStr, CRO board-reporting guidance].

The weekly forecast call is the one mechanism that can surface that shortfall 6-9 weeks early, while it is still fixable. Pavilion's go-to-market leadership community describes the weekly forecast call as the single highest-leverage operating cadence a revenue org runs [Pavilion, GTM leadership practice].

Make the room feel the asymmetry. A forecast that says "we will hit 100%" and lands at 100% earns nothing — that is the expected outcome. A forecast that says "we will hit 100%" and lands at 81% does not cost 19 points of revenue; it costs 19 points of revenue plus the CRO's credibility, plus the next quarter's target (which gets set off the inflated number), plus the headcount and marketing spend that were approved against revenue that never arrived.

The blind miss is the expensive event. The forecast call exists to make sure no miss is ever blind.

There is a second-order cost the room should name. When a CRO misses a number the board did not see coming, the board discounts *every future forecast that CRO presents*. Salesforce's "State of Sales" research finds forecast accuracy is one of the lowest-confidence metrics sales leaders report [Salesforce, "State of Sales"].

A blind miss costs compounding interest: the next forecast is believed less, the CRO over-corrects, targets get set defensively. The forecast call is the cheapest place to break that cycle — it is the only recurring meeting where the *inputs* to the forecast are still small enough to change.

Frame the eight minutes this way: you are not here to learn a new meeting; you are here to change what happens *inside* the hour you already spend.

1.2 Manager A — the status-update call

Manager A ran a status-update forecast call. Every Tuesday, eight reps each read three numbers — Commit, Best Case, Pipeline — and the manager added them up. Nobody asked who the economic buyer was.

Nobody asked when the last buyer-side meeting happened. The roll-up looked healthy all quarter. In the final two weeks, four "Commit" deals slipped.

The quarter closed at 81% of plan, and the CRO had told the board, three weeks earlier, that the number was safe.

The tell in Manager A's call was not laziness — it was the *shape* of the meeting. It was a roll-call. Each rep performed a number, the manager performed arithmetic, and the call ended on time feeling productive.

Nothing in the structure forced a single deal to defend itself. That is the trap: a status call can feel disciplined — it starts on time, everyone participates, a number is produced — and still produce a fiction.

Walk the room through Manager A's final two weeks, because the *mechanism* of the miss matters more than the headline. Of the four deals that slipped, none slipped from a dramatic loss. Deal one was single-threaded to a champion who went on leave; the rep had never met the economic buyer, so nobody kept the deal moving.

Deal two had been in Commit for six weeks with the same next step — "circling back with Legal" — and nobody asked why Legal had not produced redlines in 40 days. Deal three was a renewal-plus-expansion counted at full value, but the expansion had never been scoped with the buyer. Deal four would have closed — three weeks into the *next* quarter, because the rep never confirmed the close date against the buyer's fiscal calendar.

Every one is something an inspection question catches in week 3. None is a rep lying. All are a rep going un-inspected.

1.3 Manager B — the deal-inspection call

Manager B ran a deal-inspection call. Same eight reps, same 60 minutes. But every deal in Commit had to survive a question set: Who is the economic buyer and have you met them?

What is the paper process and who signs? When is the next step, and is it on a calendar? Show me buyer-side activity in the last 10 days.

In week 3, three deals failed the inspection and got moved from Commit to Best Case — a painful, honest re-categorization. Because the gap surfaced early, the team ran an outbound pipeline sprint and pulled two Best Case deals forward. The quarter closed at 103%.

Same number of reps. Same hour. The difference was entirely in what happened during it. Manager B's call did not *predict* the quarter better — it *changed* the quarter. Catching three soft deals in week 3 created nine weeks of runway. That is the thesis of this training: inspection is not measurement, it is intervention.

Be precise about *what* Manager B did differently, because "she inspected" is too vague to copy. She did four things: opened with the *gap to plan* rather than the roll-up total; required *artifacts* — every Commit deal needed a buyer-side email, an accepted invite, or a document the buyer touched in the last ten days; ran the challenge on the *deal*, never the rep; and ended every deal in a dated action on a shared board, read back at the next call.

None is difficult; together they are the difference between 81% and 103%.

The Bridge Group's benchmarking finds the orgs with the tightest forecast-vs-actual gaps are the ones with the most *consistent inspection cadence* [The Bridge Group, SaaS AE Metrics]. Consistency, not intensity, is the variable: a medium-rigor inspection every week beats a heroic deep-dive twice a quarter, because the silent slip is a *time* problem only a weekly cadence catches before it compounds.

⚠️ Common Trap

"Manager A just had a worse team." No. Manager A had an *un-inspected* team. Reps are not lying — they are optimistic, they are protecting themselves, and they mirror whatever the manager rewards.

CSO Insights / Korn Ferry sales-performance research found that organizations with a formally adopted, dynamic sales process forecast materially more accurately than those running an informal process [CSO Insights / Korn Ferry, Sales Best Practices Study lineage]. The forecast call does not measure rep honesty; it manufactures forecast accuracy through the questions asked.

1.4 What this hour buys you

Transition: "For the next 52 minutes we are going to learn the 5-stage forecast call, name the three pathologies that are quietly destroying your number, and run two role-plays. By the end you will never run a status-update forecast call again."

SECTION 2 — THE TEACH (0:08-0:30)

🟡 Coach Note

Twenty-two minutes. Split into the 5-STAGE FORECAST CALL (12 min), the 3 forecast pathologies (6 min), and the forecast-accuracy self-diagnosis (4 min). End-of-section test: every manager can recite the 5 stages, define Commit / Best Case / Pipeline without notes, and name all 3 pathologies.

Part A — The 5-STAGE FORECAST CALL (12 min)

A weekly forecast call should move every deal through five stages of scrutiny. Most calls only do the first — they categorize, add up the number, and end. The accuracy lives in stages two through five.

The five stages are not a sequence you run once; they are a loop you run every week, where stage 5's committed actions become stage 2's inspection material the following Tuesday.

2.1 Stage 1 — CATEGORIZE

Every deal in the quarter sits in exactly one forecast category, and the categories are definitions, not feelings. This three-tier model — Commit / Best Case / Pipeline — was popularized in modern revenue operations by Clari, which built its forecasting platform around forecast categories that are deliberately distinct from CRM sales stage [Clari, "Definitive Guide to Sales Forecasting"; Clari, forecast-category methodology].

A workable standard:

• Lead-in: Commit = the rep is willing to be held to this deal closing this quarter; it has a confirmed close date, an identified and engaged economic buyer, a known paper process, and a scheduled next step.
• Lead-in: Best Case = a real, winnable deal with a credible path, but missing at least one Commit requirement.
• Lead-in: Pipeline = an active opportunity that is not realistically closing this quarter.

A deal can be in "Stage 4 / Negotiation" in the CRM and still only be a Best Case deal if the economic buyer has never been in a room. Sales stage measures *where the deal is in your process*; forecast category measures *how confident you are it closes this quarter*. Conflating the two is the most common categorization error.

HubSpot's pipeline-management guidance makes the same distinction — a stage is a *milestone in the deal*, a category is a *probability statement about the quarter* — and the two should never auto-update each other [HubSpot, sales forecasting methodology].

CATEGORIZE has to be a *definition* and not a feeling because feelings are not auditable. If "Commit" means "I feel good about it," two reps with identical deals categorize differently, the manager cannot challenge a feeling, and last quarter's miss teaches nothing. A written definition makes the category falsifiable: either the EB has joined a call or they have not.

Forrester's research on B2B revenue process maturity describes this as the move from an *intuitive* to a *defined* revenue process, and finds defined-process orgs forecast materially more reliably [Forrester, B2B revenue process research].

There is a four-part Commit test the room should memorize, the spine of every later stage: (1) confirmed close date — an actual date the buyer agreed to; (2) identified and engaged economic buyer — the person who can sign, personally in a conversation; (3) known paper process — who touches the contract and in what order; (4) scheduled next step — on a calendar both sides accepted.

A deal that fails any one of the four is a Best Case deal. Not a weak Commit. A Best Case deal.

🎤 Verbatim Script — CATEGORIZE

"Before we inspect anything, I want category discipline. Commit means you are personally signing up for this deal to close by the 30th — confirmed date, economic buyer engaged, paper process known, next step on a calendar. If any one of those is missing, it is Best Case, not Commit, and that is completely fine.

Best Case is not a demotion. Miscategorized is the only failure here."

2.2 Stage 2 — INSPECT

For each Commit deal, the manager runs an evidence inspection — not "how do you feel," but "show me." The inspection is anchored to MEDDPICC: Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition — the qualification framework that originated at PTC (Parametric Technology Corp) in the early 1990s under sales leaders including Jack Napoli and Dick Dunkel [MEDDIC Academy, framework history], and is now codified by the MEDDIC Academy [MEDDIC Academy].

The manager is checking whether the rep's category is supported by facts the rep can produce on the spot.

The discipline of INSPECT is the word *show*. "I'm confident in the economic buyer" is not evidence; "the CFO joined our call on the 12th and sent this email on the 14th" is evidence. A rep who can produce buyer-side artifacts on demand has a real Commit. A rep who narrates feelings has a Best Case wearing a Commit label.

The most useful mental model for INSPECT is *seller-side* versus *buyer-side* activity. Seller-side activity is everything the rep does — emails sent, calls dialed, demos delivered — and it predicts almost nothing, because a rep can generate it on a dead deal indefinitely. Buyer-side activity is what the *buyer* does — replies, accepts a meeting, forwards the proposal, opens the contract.

Gong Labs' research on deal signals finds the trajectory of buyer-side engagement is one of the strongest predictors of on-time close, and deals where it has gone flat are dramatically more slip-prone regardless of how busy the rep looks [Gong Labs]. INSPECT, done right, is a buyer-side-activity audit.

The MEDDPICC frame gives the inspection eight checkpoints. Metrics: the quantified business outcome. Economic buyer: the budget authority — engaged, not just named.

Decision criteria: how the buyer chooses. Decision process: the steps to a signature. Paper process: the procurement, legal, and security path.

Identify pain: the reason to act now. Champion: an internal advocate who sells when the rep is absent. Competition: who else, including "do nothing," is in play.

A Commit deal needs credible, rep-producible evidence on all eight. The two that most often expose a happy-ears Commit are the economic buyer (named but never engaged) and the paper process (assumed but never confirmed).

🎤 Verbatim Script — INSPECT

"Walk me through this Commit. Who is the economic buyer, and when did you last speak with them directly? What is the paper process — who in their org has to touch this contract, and is Procurement or Legal already involved?

What does the buyer's decision process look like between now and the 30th? Show me the most recent buyer-side activity — an email they sent you, a meeting they accepted. What is the next step and what date is it on?"

The seven inspection questions, with what each one is really testing:

The last question — "what would have to be true for this to slip" — is the highest-yield in the set, because it asks the rep to argue *against* their own deal. A rep who names two credible slip risks understands their deal; a rep who says "nothing, it's solid" has not stress-tested it.

2.3 Stage 3 — CHALLENGE

When the inspection surfaces a gap, the manager challenges the category — calmly, without shaming the rep. The goal is to convert a gap into a re-categorization or an action, not to win an argument. A Commit deal with no economic-buyer access and no scheduled next step is, by definition, a Best Case deal — and the manager says so.

CHALLENGE is where the safety culture of the team is either built or destroyed: a challenge aimed at the *deal* builds trust; a challenge aimed at the *rep* teaches the room to hide deals.

The grammar of a good challenge has three moves. Move one — name the evidence, not the verdict: "you have not met the EB and the next step is undated" is an observation the rep cannot dispute; "you're sandbagging" is a verdict the rep will defend. Move two — apply the definition out loud: "by our written Commit definition, a deal with no engaged EB is a Best Case deal" puts the *standard* in the room as the authority, not the manager's opinion.

Move three — convert to an action: "what is the single thing that moves this back to Commit, and when" leaves the rep with a path, not a demotion. All three feels like coaching; skipping move three feels like a downgrade and trains the rep to argue.

The hardest CHALLENGE is when manager and rep genuinely disagree and the evidence is ambiguous. The rule: the *burden of proof sits with the higher category*. Commit is a claim the team will be held to; the rep claiming Commit produces the evidence, and absent it the deal defaults to Best Case.

The more consequential the claim, the higher the evidentiary bar.

🎤 Verbatim Script — CHALLENGE

"You have called this a Commit, but you have not met the economic buyer and the next step is 'I will follow up.' That is not a Commit, that is a Best Case with a strong champion. I would rather you carry it honestly as Best Case and we build a plan to earn the EB meeting this week.

What is the single action that would move it back to Commit, and when will you do it?"

2.4 Stage 4 — REFORECAST

After every deal is inspected and challenged, the manager re-rolls the number — and critically, looks at the gap to plan. If inspected Commit is below target, that is the most valuable output of the meeting: it means the team has time to act. The Bridge Group's SaaS AE benchmarking shows that in orgs without a structured weekly deal-inspection cadence the gap between reported forecast and actuals widens to roughly 20-35% [The Bridge Group, SaaS AE Metrics] — reforecast is where a manager catches that drift early.

The reforecast number is never "bad news" in week 3; it is the most actionable intelligence the call produces.

The REFORECAST stage has a *time-aware* response: the correct reaction to a gap depends entirely on the week of the quarter. The same 16-point gap means three different things in week 3, week 8, and week 12:

The most expensive mistake at REFORECAST is treating a week-3 gap as a crisis and a week-12 gap as something to wait out — it is exactly backwards. A week-3 gap is a *normal, fixable* operational fact; a week-12 gap is the moment to call the CRO before the board hears it second-hand.

Clari's revenue-leak research frames the point: the ~14-15% of revenue that quietly disappears between forecast and actual is recoverable *only* when the gap is visible early enough to act on [Clari, Revenue Leak research].

🎤 Verbatim Script — REFORECAST

"Inspected Commit is now 88% of plan, down from the 104% we read at the top of the call. That 16-point gap is not bad news — it is the most useful thing we learned today, because it is week 3 and not week 13. Here is the plan: two Best Case deals get a multi-threading push this week, and we open 15 new conversations by Friday."

2.5 Stage 5 — COMMIT

The call ends with each rep verbally committing to their inspected number and to a small number of specific deal actions before the next call. 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 an action.

The committed actions are written down, and the next week's call opens by checking them — that verification loop is what converts the forecast call from a meeting into a system.

A good COMMIT action passes three tests. It is specific — it names the deal, the person, and the move. It is dated — a deadline before the next call, "by Thursday EOD," not "this week." It is verifiable — next week the manager can ask one yes/no question and know whether it happened.

An action that fails any of the three is a wish, not a commitment.

The verification loop is the part most teams skip, and skipping it is what makes forecast calls feel performative. If the manager writes ten actions and never reads them back, the team learns within two weeks that actions do not matter. The fix costs ninety seconds: the *first* agenda item of every call is reading last week's committed actions and marking each done or not-done — which makes the rep's word in the room a thing that gets checked.

🎤 Verbatim Script — COMMIT

"Before we close: each of you, give me your inspected Commit number and the one action you are taking on your weakest deal before next Tuesday. I am writing them down, and we open next week's call by checking them. That is the loop — inspect, act, verify."

🗺️ The Forecast Call Flow

flowchart TD A[Weekly Forecast Call Starts] --> B{Stage 1: CATEGORIZE} B -->|Commit / Best Case / Pipeline by definition| C{Stage 2: INSPECT} C -->|MEDDPICC plus buyer activity show me| D{Stage 3: CHALLENGE} D -->|Evidence supports category| E[Category holds] D -->|Gap found| F[Re-categorize or assign action] E --> G{Stage 4: REFORECAST} F --> G G -->|Inspected Commit vs plan| H{Gap to plan} H -->|At or above plan| I[Hold and protect Commit deals] H -->|Below plan in week 1 to 9| J[Pipeline sprint plus pull Best Case forward] H -->|Below plan in week 10 to 13| K[Escalate early and protect board credibility] I --> L{Stage 5: COMMIT} J --> L K --> L L -->|Each rep inspected number plus 1 deal action| M[Actions logged and verified next call]

Part B — The 3 Forecast Pathologies Every Manager Tolerates (6 min)

Per The Bridge Group, Clari, and Gong, 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. None of the three is a character flaw; all three are rational rep behavior in response to how the call is run.

2.6 Pathology 1 — Sandbagging

Lead-in: Sandbagging is when the rep deliberately under-categorizes a strong deal — parks a real Commit in Best Case — to protect themselves from being held accountable, or to bank a "beat" later. It feels safe to the rep and quietly destroys the forecast: the org under-invests because the number looks low.

Detection: a rep whose actuals chronically exceed their forecast, and deals that close from Best Case with a complete MEDDPICC the rep "didn't want to jinx." Sandbagging is not harmless conservatism — it causes the org to under-hire, under-spend on demand-gen, and mis-allocate territory, and it trains your best reps to lie low.

Managers tolerate sandbagging because it produces a *pleasant surprise* — the rep beats, the manager looks good. But the org pays elsewhere: if the true number were visible, the CRO would set a higher target, marketing would fund against real demand, and the territory carve would reflect reality.

Instead the org plans against a fiction that is too *low* and — most corrosively — teaches its best reps that the safe play is to hide pipeline.

2.7 Pathology 2 — Happy-ears

Lead-in: Happy-ears is when the rep over-categorizes a weak deal — calls a single-threaded, no-next-step deal a Commit — because the buyer was friendly, the demo went well, or the rep is behind quota. Clari's revenue-leak research estimates only about 20-25% of reps forecast within a reliable margin without manager inspection [Clari, Revenue Leak research].

Detection: Commit deals with one contact, no economic-buyer access, no scheduled next step, and no buyer-side activity in the last two weeks. Happy-ears is the pathology managers notice, because it produces the visible last-week slip.

Happy-ears is rarely dishonesty — it is a cognitive bias under quota pressure. A rep behind plan *wants* the deal to be real, and a friendly buyer gives just enough signal to believe it. The tell: 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").

A Commit defended entirely with sentiment is almost always happy-ears. The cure is not to argue — it is to ask the process questions and let the absence of answers do the work. Happy-ears collapses on "show me the calendar invite."

2.8 Pathology 3 — The silent slip

Lead-in: The silent slip is when nobody mis-categorizes anything — a deal simply goes quiet and stays in Commit because no one inspected it. Gong Labs research on deal signals shows deals with no buyer-side activity in the trailing ~11-14 days are dramatically more likely to slip [Gong Labs].

Detection: the rep last heard from the buyer 18 days ago, the next step keeps being "following up," and the deal rides the forecast until it slips in the final week. The silent slip is the most dangerous pathology precisely because there is no liar to catch — there is only an absence of inspection.

The silent slip is dangerous because it is *invisible to a status call by construction*. A status call asks "what category is this deal in?" and the silent-slip deal answers honestly — "Commit." It was a real Commit three weeks ago; nothing about the category is wrong. What is wrong is that the *world changed* and nobody re-checked: the champion got reorganized, priorities shifted, budget froze — and because the rep is still doing seller-side activity, the deal *looks* alive on the CRM surface.

Only a question about *buyer-side* activity in a tight recent window surfaces it. That is why the inspection set is built around buyer-side artifacts and a ten-day window: it is the only mechanism that catches a deal that has died but not yet been buried.

⚠️ Common Trap

Managers treat sandbagging as harmless ("at least we'll beat") and happy-ears as the only problem. Both are forecast errors. Sandbagging is just as damaging — it causes the org to under-hire, under-spend, and mis-allocate, and it trains your best reps to lie low [The Bridge Group, sales-management research]. Inspect both directions.

2.9 Forecast-Call Benchmarks — What "Good" Looks Like

These are not targets to recite — they are the evidence base for why each stage of the call exists. CATEGORIZE exists because under half of forecasted deals close as forecasted in low-maturity orgs. INSPECT exists because only ~20-25% of reps forecast reliably unaided.

REFORECAST exists because the ~14-15% revenue-leak figure is recoverable only when the gap is caught early. COMMIT exists because Gong's buyer-silence signal means an un-acted deal decays week over week. The numbers justify the ritual.

One caution on benchmarks: use them as a *direction*, not a verdict. Win rates and coverage ratios vary by segment and deal size — a 17% win rate is healthy for an enterprise motion, alarming for an inbound mid-market one. The value of a benchmark is the *gap it reveals* against a comparable cohort, not the absolute figure [The Bridge Group, SaaS AE Metrics].

The table is a teaching aid for *why the stages exist*, not a rep scorecard — the real scorecard is the team's own forecast-vs-actual history.

2.10 Part C — Forecast-Accuracy Self-Diagnosis (4 min)

Have every manager privately rate their own forecast call against five markers.

1. Lead-in: Category discipline — are Commit / Best Case / Pipeline defined in writing and enforced, or set by tone?
2. Lead-in: Inspection depth — does every Commit deal get pressure-tested against MEDDPICC and buyer activity, or just read aloud?
3. Lead-in: Reforecast honesty — does the call produce a real gap-to-plan early, or a comfortable number?
4. Lead-in: Action loop — does the call end in specific committed actions that get checked next week?
5. Lead-in: Forecast-vs-actual — over the last four quarters, is the manager's miss inside 5%, inside 15%, or wider?

A manager who is "tone-based, read-aloud, comfortable-number, no loop, >15% miss" is running a status meeting and calling it a forecast call. Use the scorecard below to translate the five markers into a maturity tier.

Scoring: 0-3 is a status meeting in forecast-call clothing; 4-6 is a team in transition; 7-10 is a genuine inspection ritual. The point is not the score — it is to make every manager name the single marker they will move up one tier this quarter.

SECTION 3 — DISCUSSION (0:30-0:40)

🟡 Coach Note

Ten minutes, eight prompts. Do not lecture — pull answers from the room and write the patterns on the whiteboard. The deliverable is an honest audit of last quarter's forecast-vs-actual by rep.

3.1 The eight discussion prompts

1. Lead-in: Category discipline. Pick last quarter. How many deals that you called Commit actually closed? If it is under 85%, your Commit category is really a Best Case category — what definition are you missing?
2. Lead-in: The single-threaded Commit. How many deals are sitting in your current Commit with exactly one contact? Per Gong-style data, single-threaded deals close at roughly half the rate. Should a single-threaded deal ever be a Commit?
3. Lead-in: Dark deals. Look at your Commit list. Which deals have had zero buyer-side activity — no email, no accepted meeting — in the last two weeks? What is your rule for a dark Commit deal?
4. Lead-in: Sandbagging detection. Which rep on your team chronically beats their own forecast? That is not a hero — that is a forecasting problem. How do you coach a sandbagger without punishing the beat?
5. Lead-in: Pull-forward pressure. When you are behind at week 8, the temptation is to lean on reps to "commit" more. Does pressure create pipeline, or just move happy-ears deals into Commit?
6. Lead-in: The slip conversation. When a rep needs to move a deal from Commit to Best Case, do they feel safe doing it — or do they hide it? What in your call rewards honesty over optimism?
7. Lead-in: Board-credibility math. A 19% miss the board did not see coming costs more than the 19%. What does it cost in CRO credibility, in next-quarter targets, in headcount approvals?
8. Lead-in: Overruling a rep. When a rep insists a deal is a Commit and the evidence says Best Case, do you overrule the category? When should the manager's call win?

3.2 The forecast-vs-actual audit table

As the room discusses prompt 4, have each manager fill this audit for their own team — one row per rep, last four quarters. The pattern in the right-hand column is the coaching agenda for the quarter.

A rep who is consistently accurate — Rep C — is more valuable to the forecast than a rep who beats erratically. Name that out loud: the goal of the call is not maximum optimism, it is minimum variance.

3.3 How to facilitate the eight prompts

Ten minutes for eight prompts is roughly seventy-five seconds each — not a deep debate, a *rapid surfacing exercise*. Three rules keep it on time: name the prompt, take two answers, move on; write the uncomfortable answers down, because a public number is harder to forget; and end on prompts 7 and 8, which carry the most strategic weight.

Prompts 4 and 8 are the two managers resist most. Prompt 4 — the sandbagger — is resisted because the sandbagger is usually a top performer the manager will not "punish." Reframe: you are not punishing the beat, you are recovering *visibility* — "I love that you beat, and I need your forecast to be a forecast." Prompt 8 — overruling a category — is resisted out of fear it damages trust.

Reframe: overruling is a rare last resort, and when used it is the *definition* doing the overruling — "our written rule says a deal with no engaged EB is Best Case; I am holding the rule, not overruling you." Overrule with the definition, not authority, and trust survives.

SECTION 4 — ROLE-PLAY x 2 (0:40-0:55)

🟡 Coach Note

Fifteen minutes, two rounds of about 7-8 minutes each. Pairs: one plays the manager running the 5-stage inspection, one plays the rep. Swap halfway. Observers note: did the manager INSPECT with "show me" or accept "I feel good"? Did they CHALLENGE the category calmly? Did the call end in a committed action?

4.1 Round 1 — The Sandbagger (~7-8 min)

Setup. It is week 4 of the quarter. Your rep, Dana, is carrying the "Northwind" deal in Best Case. On inspection it has: a confirmed economic buyer who has joined two calls, a documented decision and paper process, Legal already engaged, a mutual close plan, and a next step on the calendar for Thursday.

Dana's MEDDPICC is essentially complete. Dana has beaten her forecast three quarters running. She wants to keep Northwind in Best Case "so I don't jinx it."

Manager objectives.

• Lead-in: CATEGORIZE — name that this deal meets every Commit requirement.
• Lead-in: INSPECT — have Dana walk the MEDDPICC out loud so the room hears how complete it is.
• Lead-in: CHALLENGE — surface the sandbag without shaming: "this is a Commit by our own definition; carrying it as Best Case hides real revenue."
• Lead-in: REFORECAST — move Northwind into Commit and re-roll.
• Lead-in: COMMIT — get Dana to agree that a complete-MEDDPICC deal with a scheduled next step is, by team rule, a Commit.

Curveball. Dana says, "Last time I committed a deal it slipped and you remembered it for a year." The manager has to repair the safety problem: honest categorization, in both directions, is never punished — only mis-categorization is.

What good looks like. The manager does not order Dana to move the deal. The manager has Dana walk the MEDDPICC aloud so the room hears every element is present, then applies the definition: "by our own written Commit rule, this deal has every element; carrying it in Best Case hides real revenue." The manager handles the curveball head-on: "You are right that I remembered that slip too long, and that was my mistake.

The new rule applies to me too — the only thing remembered is *miscategorization*; an honest Commit that slips is a normal event." The round ends with Dana agreeing the *rule*, not just the deal. A manager who "wins" by asserting authority — "I'm moving it" — has fixed nothing; Dana will sandbag the next deal.

4.2 Round 2 — The Happy-Ears (~7-8 min)

Setup. Same week. Your rep, Marcus, is behind quota and is carrying the "Cascade" deal in Commit. On inspection: one contact only — a friendly mid-level manager who loved the demo.

No economic buyer identified. No paper process known. The "next step" is "Marcus will follow up next week" — nothing on a calendar.

Last buyer-side email was 16 days ago. Marcus says, "I just have a really good feeling about this one."

Manager objectives.

• Lead-in: INSPECT — ask the "show me" questions: who is the EB, when is the next step, show me buyer activity in the last 10 days.
• Lead-in: CHALLENGE — "Cascade is single-threaded, has no EB, no paper process, no scheduled next step, and 16 days of buyer silence. By our definition that is Pipeline, maybe Best Case if we earn a meeting."
• Lead-in: REFORECAST — move Cascade out of Commit and show Marcus the honest gap.
• Lead-in: COMMIT — turn it into action: "your job this week is to multi-thread to the EB and book a real next step."

Curveball. Marcus pushes back: "If I move Cascade out, my number looks terrible." The manager has to separate the forecast from the verdict on the rep — an honest low number plus a credible action plan is a *better* outcome than a happy-ears Commit that misses.

What good looks like. The manager resists arguing about feelings and runs the "show me" set, letting the absence of answers do the work: no buyer-side activity in ten days, no named EB, no dated next step. The manager states the verdict in terms of the *definition*: "Cascade fails all four Commit criteria — by our rule that is Pipeline, and it becomes Best Case the moment you earn an EB meeting." The manager handles the curveball by separating two numbers Marcus has conflated: "Your *forecast* is not a verdict on *you*.

An honest 70% plus a real plan to multi-thread Cascade beats a 100% that misses — the first I can help you with, the second blindsides us both." A manager who lets Round 2 become a debate about whether the buyer "likes us" has lost; sentiment is not inspectable, process evidence is.

4.3 Observer scorecard

Give every observer this scorecard. Score each round and read the lowest-scoring row aloud in the debrief — that is the team's coaching target.

🗺️ Role-Play Inspection Decision Path

flowchart TD A[Manager opens the deal] --> B{Can the rep produce buyer-side evidence} B -->|Yes complete MEDDPICC and dated next step| C{Current category} B -->|No missing EB or next step or activity| D{Current category} C -->|Carried as Best Case| E[Sandbag - move up to Commit] C -->|Carried as Commit| F[Correct - confirm and protect] D -->|Carried as Commit| G[Happy-ears - move down and assign action] D -->|Carried as Best Case| H[Honest - assign action to earn Commit] E --> I[Reforecast and log action] F --> I G --> I H --> I I --> J[Rep commits to one dated action before next call]

SECTION 5 — DEBRIEF + COMMITMENTS (0:55-1:00)

🟡 Coach Note

Last five minutes. Tight. Three questions, then written commitments. No new teaching.

5.1 Three debrief questions

1. Lead-in: Weakest stage. Which stage of the 5-stage call is weakest in your current forecast call — CATEGORIZE, INSPECT, CHALLENGE, REFORECAST, or COMMIT?
2. Lead-in: Live pathology. Which pathology is most alive on your team right now — sandbagging, happy-ears, or the silent slip — and how do you know?
3. Lead-in: Safety gap. What in your current call makes reps feel *unsafe* moving a deal down a category? Name one thing you will change.

5.2 Written commitments

Each manager writes down:

• Lead-in: One deal they will personally re-inspect against MEDDPICC before the next forecast call.
• Lead-in: One inspection question from the verbatim scripts they will adopt permanently into their weekly call.
• Lead-in: One definition — Commit, Best Case, or Pipeline — they will put in writing and send to their team this week.

📋 Leave-Behind

The Forecast Call Card. (1) Categories: Commit = confirmed date + engaged economic buyer + known paper process + scheduled next step; Best Case = winnable but missing one of those; Pipeline = not closing this quarter. (2) 5 stages: CATEGORIZE → INSPECT → CHALLENGE → REFORECAST → COMMIT.

(3) 7 inspection questions: Who is the EB and when did you last talk to them? What is the paper process and who signs? What is the buyer's decision process to close?

Show me buyer-side activity in the last 10 days. What is the next step and what date is it on? Is the deal multi-threaded?

What would have to be true for this to slip? (4) 3 pathologies: sandbagging (too low), happy-ears (too high), silent slip (un-inspected). (5) The rule: miscategorized is the only failure — honest movement in either direction is always safe.

5.3 When To Run This Training Again

Run it at the start of every quarter, after any missed quarter (most urgent — the miss is the curriculum), when a new front-line manager inherits a forecast call, when forecast-vs-actual drifts past 15% for two quarters running, before a board cycle where forecast credibility matters, and whenever a new forecasting tool or category model is rolled out.

Rotate the role-play scenarios: a multi-quarter slipping deal, a deal stuck in Procurement, a brand-new rep with no forecast history, an enterprise deal with a 14-stakeholder buying committee.

5.4 The 30-day adoption plan

A training that ends at the debrief is a training that decays. Give every manager a concrete 30-day adoption sequence so the ritual survives contact with the next four forecast calls.

The adoption plan is deliberately incremental. You do not flip the whole call to inspection mode in week one — that feels like an ambush. You install one stage per week, in order, so by month-end the full five-stage loop is running and the team owns it rather than endures it.

5.5 Common adoption failures and the fix

SECTION 6 — COUNTER-CASE: WHEN INSPECTION IS THE WRONG MOVE (read before you adopt this)

🟡 Coach Note

Spend three minutes here at the end of the Teach, or hand it out as part of the Leave-Behind. A framework taught without its failure modes gets over-applied. The 5-stage call is right most of the time — but a manager who runs it mechanically, in every situation, will do damage. Name the limits out loud so the room trusts the model.

6.1 Counter-case 1 — Inspection is not interrogation

The single most common way this training backfires is a manager who turns "show me" into a public cross-examination. If every forecast call becomes a witness stand, reps stop bringing forward the weak deals at all — they hide them until the last week, which is the exact failure the call was meant to prevent.

The fix: inspect the *deal*, never the *rep*; do the hardest challenges in a 1:1, not the group call; and visibly reward the rep who voluntarily moves a deal down a category. If your team has gone quiet in the forecast call, you have over-rotated.

6.2 Counter-case 2 — A brand-new rep has no forecast history to inspect

For a rep in their first two quarters, there is no forecast-vs-actual track record, no pattern of sandbagging or happy-ears, and often an incomplete MEDDPICC simply because they are still learning the motion. Running the full CHALLENGE stage on a new rep reads as "you are failing" when they are actually ramping on schedule.

The fix: for ramping reps, use the call to *teach* the categories and *build* the MEDDPICC habit — coach the inputs, do not grade the output, until they have one full quarter behind them.

6.3 Counter-case 3 — Transactional, high-velocity motions do not need deal-by-deal inspection

If you sell a $4K ACV product with a 14-day sales cycle and 600 deals a quarter, inspecting each deal against MEDDPICC is impossible and pointless. At that velocity the forecast is a *statistical* object, not a deal-by-deal object — you forecast off conversion rates, stage-to-stage velocity, and pipeline coverage, and you inspect *cohorts and trends*, not individual opportunities.

This training is built for considered B2B deals (roughly $25K+ ACV, multi-stakeholder, 30-day-plus cycles). Match the inspection depth to the deal size.

6.4 Counter-case 4 — Over-inspection can manufacture sandbagging

There is a self-defeating loop here: if a manager punishes every slipped Commit harder than they reward an honest Best Case, rational reps respond by under-categorizing everything — they sandbag to stay safe. The very rigor of the inspection, applied without psychological safety, *creates* the pathology in Part B.

The fix is structural: make the only punishable error *miscategorization*, treat an honest down-move as a neutral or positive event, and never let a forecast number double as a performance verdict on the person.

6.5 Counter-case 5 — The forecast call cannot fix a pipeline problem

Inspection makes a number *accurate*; it does not make a number *bigger*. If the team is at 1.8x coverage in week 2, no amount of CHALLENGE will conjure revenue — the honest output of the call is "we have a top-of-funnel problem," and the fix lives in demand-gen and outbound, not in the forecast meeting.

A manager who keeps re-inspecting the same thin pipeline hoping the number improves is avoiding the real conversation.

6.6 The synthesis

Run the 5-stage call as the default for considered B2B deals, with real psychological safety, adjusting depth for rep tenure and deal size — and know that it produces an *accurate* forecast, not automatically a *good* one. An accurate forecast that says "we will miss" is the training working, not failing.

🔗 Related Pulse Content

This is the thirty-seventh entry in Pulse Sales Trainings and a core RevOps coaching template — a fully runnable 60-minute live training for sales managers, directors, VPs of Sales, CROs, and RevOps leaders who own a weekly forecast call. It pairs the deal-inspection ritual with the forecast methodology (Commit / Best Case / Pipeline), MEDDPICC qualification, and the three forecast pathologies that distort most B2B SaaS numbers.

Closest siblings in the sales-training series: (st0001) (The Discovery Call Reset — the qualification work that feeds clean forecast categories upstream), (st0003) (Objection Handling "We Need to Think About It" — the post-demo stall that becomes a silent-slip deal), (st0031) (The Expansion QBR — expansion ARR that also has to be forecast), (st0032) (The Closed-Lost Win-Back Sprint — re-engaging the dead deals a reforecast pipeline-sprint targets), and (st0033) (The Champion Departure Save — the single biggest mid-deal slip risk a forecast call should flag).

Cross-references to the Pulse Q&A library — the forecasting cluster this training operationalizes:

• (q34) ("How do I run a 25-minute pipeline review that's actually useful?") — the shorter operational cousin of this 60-minute call; the inspection questions transfer directly.
• (q37) ("What's a good pipeline coverage ratio for forecasting accuracy?") — defines the ~3x coverage math that the REFORECAST stage checks against.
• (q236) ("When is a deal stage too early to commit to forecast — commit vs best case?") — the exact category-discipline question Stage 1 CATEGORIZE drills.
• (q48) ("What's the most reliable way to predict end-of-quarter shortfall?") — the early-warning logic behind running this call weekly.
• (q214) ("What signals from a CRM tell you a deal is about to slip 30+ days before it does?") — the CRM-signal layer that feeds silent-slip detection in Part B.
• (q233) ("How do you forecast deal slippage in the last week of the quarter?") — the last-week scramble this training is explicitly designed to prevent.
• (q294) ("How do probability weighting models prevent pipeline inflation in forecast accuracy?") — the modeling layer that sits beneath the human inspection ritual.
• (q296) ("Why do commit, best-case, and pipeline forecasts require different closing assumptions?") — the methodology rationale for keeping the three categories distinct.

Run st0037 as the live-training delivery of that cluster: the q-entries explain the *what*, this training installs the *how* as a weekly team ritual.

Hub: /sales-trainings.

Sources

1. The Bridge Group — SaaS AE Metrics & Sales Compensation benchmarking. https://www.bridgegroupinc.com/
2. Clari — "Definitive Guide to Sales Forecasting" and Revenue Leak research. https://www.clari.com/
3. MEDDIC Academy — the MEDDIC / MEDDPICC qualification framework. https://meddic.academy/
4. Gong.io — Gong Labs research on deal and forecast signals. https://www.gong.io/
5. CSO Insights / Korn Ferry — Sales Best Practices Study sales-process-maturity research. https://www.kornferry.com/capabilities/sell-talent-development
6. SaaStr — sales forecasting and CRO board-reporting guidance. https://www.saastr.com/
7. Pavilion — go-to-market leadership community and forecast-call practice. https://www.joinpavilion.com/
8. Salesforce — "State of Sales" report, forecast accuracy and pipeline-management research. https://www.salesforce.com/resources/research-reports/state-of-sales/
9. HubSpot — sales forecasting methodology and pipeline-stage guidance. https://www.hubspot.com/
10. Forrester — B2B revenue process and forecasting maturity research. https://www.forrester.com/