The AE reads from the CRM. The manager nods. Then the same deals that were "on track" last week are "pushed one week" this week. And next week. Until they disappear. Most forecast calls aren't forecast calls — they're status recitals. Here's how to run one that actually moves the number.
There's a version of the weekly forecast call that every frontline sales manager has run at some point: thirty minutes, ten AEs, each one reading from their pipeline. "GlobalCorp is at stage four, expect to close by end of quarter." Manager says "good." Next AE. Rinse, repeat. Call ends. Nothing changed. Deals still slip. Forecast still misses.
The problem isn't the format. It's the question being asked. "Where does this deal stand?" is a status question. It tells you what the AE believes. It tells you nothing about what's actually true. The question that matters is different: "What evidence do you have, and what's the gap?"
That one shift — from status to evidence — changes everything about how the call runs, what gets surfaced, and what you can actually do about it before the quarter closes.
CommitTrack's Manager Rollup shows you evidence gaps by deal, by AE, before you get on the call — so you spend 30 minutes coaching, not interrogating.
Try the Forecast Checkup free →For every deal in your top-5 commits, run these five questions. Three minutes per deal, no exceptions. The goal isn't to quiz the AE — it's to find the gap before the call ends.
Not "have you spoken to the EB" — that's a status question. The evidence question is: when did the EB last take an action? Attended a demo, replied to an email, signed off on a proposal. If the last EB action is more than two weeks old, this deal is at risk regardless of what stage it's in. See the 5-axis scoring rubric for how to grade EB engagement against a defensible standard.
Every AE says their buyer has a problem. The question is whether the buyer has put a number on it. "They need better forecasting" is not quantified pain. "$2.4M in missed deals last quarter because of forecast misses" is. If the AE can't give you a number the buyer used, the pain isn't quantified. That's a coaching conversation, not a checkbox.
Who signs? Who has veto power? What are the procurement and legal steps, and how long do they actually take — not how long the AE estimates? The gap between "legal usually takes a couple weeks" and the actual six-week security review is where deals go to die in Q4. Push for specifics: names, steps, deadlines, who owns each one.
Not the AE's next action — the customer's. "I'm following up on Friday" is not a commitment. "CFO will review the business case and reply by Thursday" is. If there's no customer commitment on the table, the deal isn't being worked. There's a reason the next call hasn't happened. Find it now.
The AE said "end of quarter." Who said that, and why? If the deadline came from the AE's quota, that's not a compelling event — that's wishful thinking. A compelling event is a business consequence that the buyer named: a go-live date, a contract expiry, a board meeting. If the AE can't name it with specificity, it doesn't exist.
Before the 5-question review, spend five minutes on movement — not status. Movement means something actually changed in the deal: a commit date moved, an ARR number shifted, a new stakeholder got added, a risk appeared. "We had a call" is not movement. "CFO joined the technical review — hadn't been in the process before" is.
The reason to track movement explicitly is pattern recognition. If the same three deals have been "one week from close" for the past six weeks, that's not bad luck — that's a systemic problem in how those deals are being worked or qualified. You can't see the pattern if you're only hearing status.
The rule: if a commit date moved, you need to know the specific reason it moved and who on the buyer side communicated it. If the AE doesn't know, that's the coaching conversation.
Every deal that slipped past its commit date since last week gets two minutes. Not "what happened" — that's a post-hoc status question. The discipline is: what's the root cause code, and what's the correction path?
Root cause codes worth tracking: champion changed roles, economic buyer never engaged, budget reallocated, procurement scope underestimated, competitor entered evaluation, compelling event was assumed not verified, stakeholder turnover. (The full list of 7 hidden slip causes is worth sharing with your team.)
If you can't code the slip in two minutes, the deal wasn't well-understood to begin with. That's information. Capture it now so the same mistake doesn't repeat next quarter.
Good managers don't use the post-mortem to assign blame. They use it to build a feedback loop: over four quarters, the pattern of root causes tells you where your team's process has systematic gaps. Procurement scope is a qualification problem. Champion engagement is a discovery problem. Both are solvable if you know they're real.
Every deal that stays in the forecast exits the call with one explicit customer commitment: what the buyer will do before the next forecast call, who will do it, and by when.
No commitment = deal not real. If the AE can't name a customer action, the deal is on pause — it just hasn't been classified that way yet. Either you help the AE identify a way to create a commitment (a re-engagement play, a next step with a new stakeholder), or you move the deal out of Commit and into Best Case until there's buyer-side action.
The specificity principle matters here. "I'll follow up" is not a commitment. "Sarah will send procurement requirements by EOD Wednesday" is. The more specific the commitment, the easier it is to hold to and verify next week.
The mistake most managers make is running the forecast call as an interrogation: "Why don't you have EB engagement?" "How did procurement slip?" The AE gets defensive. The call turns into a performance review. Nobody learns anything.
The better model: manager as gap-coach. Your job isn't to surface the gap so you can document it — it's to help the AE understand what it means and what to do about it. Four common coaching scenarios:
Don't ask why the EB isn't engaged. Ask what a warm re-engagement looks like — what's the hook, who's the right person to make the introduction, what's the business reason for the EB to show up now.
Ask the AE what the buyer's last major initiative cost them. Sometimes the number is in a prior conversation and the AE just didn't capture it. Sometimes it requires a direct question in the next meeting. Script that question together.
Map it out in the call. Who does the AE know? Who haven't they met? What's the likely procurement path based on company size and industry? Identify the next discovery question to fill the gap.
Most AEs haven't asked for the compelling event directly — they've inferred it. Script the direct question: "What happens to your team if this decision doesn't get made this quarter?" Let the buyer answer.
Here's the agenda structure. Time-box it. The call ends at 30 minutes regardless. If you can't cover everything in 30 minutes, you have too many deals in Commit or the deals aren't well-understood.
| Time | Block | What Happens | Output |
|---|---|---|---|
| 0–5 min | Movement Review | Manager calls out deals that moved since last week (dates, amounts, risks). AEs confirm or correct. | Delta log — what changed and why |
| 5–20 min | 5-Question Deal Review | Top 5 commits only. 3 min per deal. Five evidence questions. Manager coaches gaps in real time. | Evidence score per deal, gap actions |
| 20–25 min | Slip Post-Mortem | 2 min per slipped deal. Root cause code + correction path. No blame, just diagnosis. | Root cause log, AE coaching actions |
| 25–30 min | Carry-Forward Commits | One customer commitment per deal before next call. Manager confirms each one is specific and accountable. | Commitment list — who, what, when |
Download the fillable version: Forecast Call Agenda Template →
CommitTrack's Manager Rollup scores every Commit deal on all five axes — so you walk into the forecast call knowing exactly where to focus. Try it free.
Try Manager Rollup Free →The call is where you find the gaps. The work happens after. Three things to do in the 24 hours after every forecast call: