How-to guide

How to run a weekly sales forecast call

The forecast call is where "I think it will close" meets "prove it." Run it well and your commit holds within a few points of actuals every quarter. Run it poorly and you walk into the board meeting defending a number nobody believes. This guide covers the 45 to 60 minute weekly cadence VP Sales and GTM leaders use to pressure-test commit, best case, and pipeline deal by deal.

Before you start

What you need.

Time: 60 minutes

  • A single forecast owner for the call, typically VP Sales or the senior GTM leader on the segment
  • CRM forecast categories wired up as Commit, Best Case, Pipeline, and Omit with manager-editable overrides
  • A published quota and coverage target for the quarter visible to every participant before the call
  • Rep-level forecast submissions locked by Monday morning so managers can review before Tuesday or Wednesday meetings
  • A dashboard that shows commit versus quota, best case versus commit, and week-over-week delta per rep
Run a weekly sales forecast call

Step by step.

  1. 1

    Lock the submission window before the call

    A forecast call is only as honest as the data that walked in. Require every rep to submit their commit, best case, and pipeline numbers by the same deadline each week, typically end of day Monday for a Tuesday or Wednesday call. Lock the submission in the CRM so late edits are tracked, not silently overwritten. Reps who miss the deadline forfeit the right to argue new deals into commit on the call. Hold the line in week one and the behavior sticks. The point of the lock is not punishment, it is calibration. You cannot measure forecast accuracy if the "forecast" keeps mutating up to the moment actuals land. Store each submission as a durable record so you can score every rep on commit-to-close delta at quarter end.

    • Set a weekly submission deadline that gives managers at least 12 hours to review before the call
    • Freeze each rep submission as a timestamped record in the CRM
    • Report missed submissions to the VP in the opening minute of the call
    • Score every rep on commit-to-close accuracy at quarter end using the locked submissions
    Tip: If reps resubmit mid-week, keep the original and track delta. The delta is a leading indicator of a slipping deal.
  2. 2

    Set a tight agenda and defend it

    A 45 to 60 minute call falls apart without a published agenda. Open with 2 minutes on the quarter number: commit versus quota, best case versus quota, pipeline coverage, and week-over-week movement. Then spend 3 to 5 minutes per rep walking commit and top-of-best-case deals. Close with 5 minutes on cross-rep risks, help needed, and action items. That is the whole meeting. No slide decks, no retrospectives on last quarter, no demo prep. If a topic does not change this week's commit, it belongs in a different meeting. Defend the agenda ruthlessly. Managers who let the call drift into coaching or deal strategy burn the one hour where leadership actually locks the number for the week.

  3. 3

    Open with the number, not the deals

    Start every call with the headline metrics on screen before anyone speaks. Commit versus quota. Best case versus quota. Pipeline coverage for the remainder of the quarter. Week-over-week delta on each. This 2 minute open does two things: it anchors every rep on the gap you are trying to close, and it exposes any manager whose roll-up disagrees with the dashboard. Resist the urge to narrate. The numbers speak. If commit is 92 percent of quota with four weeks left and coverage is below target, the only acceptable response is a plan to move pipeline into best case or to pull forward deals, not a story about why last week was hard. Set the tone that this call runs on evidence and arithmetic.

    Tip: If a manager's roll-up does not match the dashboard, pause the call and reconcile in the room. Never debate forecasts on stale data.
  4. 4

    Walk each rep through commit deal by deal

    For every rep, spend 3 to 5 minutes on commit deals and the top of best case. For each deal ask three questions and accept no substitutes. What has to be true for this to close this quarter. What evidence do you have that it is true. What is on your calendar this week to prove or disprove it. "They said they would get back to me" is not a next step. "Legal review in progress" is not a next step unless you can name the lawyer, the redline round, and the target signature date. A next step is a confirmed calendar event with a named person on a specific date. Managers who enforce this standard every week see commit-to-close delta drop below 5 percent within two quarters. Managers who accept vague language are forecasting fiction.

    • Ask what must be true, what evidence exists, and what action is scheduled this week
    • Reject any next step that does not name a person and a date
    • Mark the deal with a risk flag if the rep cannot answer all three questions cleanly
    • Record the exchange in the opportunity notes so the next review has context
    Tip: If a rep names the same next step three weeks running, the deal is stalled. Push it out or push it to Omit.
  5. 5

    Pressure test commit with risk signals

    Commit is a promise. Treat it that way. For every deal in commit, scan for the risk signals that predict slip: no activity in 14 days, no decision maker named, next-step field older than 7 days, close date pushed more than once, no mutual action plan, no economic buyer verified, legal or procurement not yet engaged with less than 3 weeks left. If a commit deal carries two or more of those signals, demote it to best case live on the call unless the rep can produce evidence that overrides the signal. Do not negotiate. Strkr AI surfaces these risk flags automatically on the forecast board so the call runs on data, not debate. The outcome is a cleaner commit the moment the meeting ends, not a to-do list.

  6. 6

    Handle best case and pipeline with lighter touch

    Best case gets a condensed version of the commit treatment. Walk the top 3 to 5 deals per rep. Ask what would have to change this week to pull them into commit. If the answer is thin, leave them in best case and move on. Pipeline below best case gets even less airtime. Coverage math alone tells you whether pipeline is healthy. Reserve detailed pipeline review for a separate pipeline council meeting with marketing, SDR, and ops at the table. Mixing those conversations into the forecast call is the single most common reason the meeting runs long. The forecast call is about this quarter. Pipeline health conversations are about next quarter. Keep them separate and both meetings get faster.

  7. 7

    Capture decisions, next steps, and movements in writing

    A forecast call that ends without written outputs is a forecast call that will replay the same arguments next week. Assign a scribe, usually the sales operations partner, who logs every deal movement, every risk flag raised, and every action item owner. Movements that happened on the call, Commit to Best Case, Best Case to Commit, Pipeline to Omit, must be reflected in the CRM before the meeting ends. Do not accept "I will update it after." Updates after the meeting drift. Updates in the meeting stick. The scribe also captures the final commit number per rep and per segment so the dashboard reconciles against the call outcome by 5pm the same day.

    • Assign a scribe for every call, same person week over week where possible
    • Log forecast category movements in the CRM live during the call
    • Capture action items with owner and due date, never just owner
    • Reconcile the dashboard to the call outcome by end of day
  8. 8

    Close with the roll-up and the gap

    End the call the way you opened it: with the number. State the final commit for the segment, the final best case, the gap to quota, and the one or two levers you are pulling this week to close that gap. If commit is above quota, name the biggest risk that could pull it back below. If commit is below quota, name the specific deals or activities that need to move. This 2 minute close turns a tactical review into a leadership decision. It also sends every participant out of the room with the same mental model of where the quarter stands. Follow with a written recap in whatever channel the team actually reads, usually Slack or Teams, within an hour of adjournment.

    Tip: The written recap should be scannable in 30 seconds. Three bullets: the number, the gap, the lever.
  9. 9

    Score accuracy and recalibrate quarterly

    The forecast call compounds in value only if you measure it. At quarter end, pull every weekly commit submission and compare to closed-won by rep, by manager, and by segment. Score the delta. A rep who commits 100 percent of their number within 5 percent every week is a forecaster you can build around. A rep who commits plus or minus 25 percent is noise. Managers whose segment commits roll up tighter than their reps are earning their keep. Managers whose roll-up is looser than the reps underneath are either over-sandbagging or under-pressure-testing. Share the scorecard. Use it to decide who runs the deals on the next quarter list, who gets coached, and whether the forecast cadence itself needs to change.

    • Compare locked weekly commits to closed-won for every rep and manager
    • Publish a scorecard ranking reps and managers by commit-to-close delta
    • Flag any rep or manager with delta above 15 percent for a calibration session
    • Review the agenda, the risk signals, and the submission deadline once per quarter
Avoid

Common mistakes.

  • Letting the call become a coaching session. Deal strategy, objection handling, and discovery technique belong in 1 to 1s. The forecast call is for locking a number.
  • Accepting vague next steps like following up or awaiting response. If the rep cannot name a person and a date, the deal is not a commit, it is a hope.
  • Mixing pipeline council and forecast call into one meeting. Current-quarter commit and next-quarter pipeline health run on different tempos and different data. Keep them separate.
  • Allowing mid-week forecast resubmissions without tracking the delta. Silent revisions destroy the historical record you need to score accuracy at quarter end.
  • Running the call without a scribe. If movements and action items are not logged live, the next call rehashes the same arguments and the forecast drifts.
  • Skipping the quarterly accuracy scorecard. Without a published delta per rep and per manager, there is no feedback loop and the quality of commit stops improving.
FAQ

Frequently asked questions.

How long should a weekly forecast call be?

45 to 60 minutes is the right band for a single segment or region with 6 to 10 reps rolled up through 2 to 3 managers. Larger teams should split into segment-level calls rather than extending the meeting. Anything past 60 minutes signals that pipeline council, coaching, or deal strategy has crept into the agenda and needs to move out.

Who should attend the forecast call?

The forecast owner (usually VP Sales or GTM leader), every frontline manager, every rep whose deals are being reviewed, and one sales operations partner acting as scribe. Finance can attend as an observer late in the quarter. Marketing, SDR leaders, and customer success belong in the separate pipeline council, not the forecast call, because their inputs affect the next quarter rather than the current commit.

How is a forecast call different from a pipeline review or QBR?

The forecast call locks the current-quarter commit week by week and runs for less than an hour. Pipeline council is cross-functional and focuses on next-quarter coverage, lead quality, and conversion. A QBR is a board-oriented retrospective and plan that runs 2 to 4 hours once per quarter. Mixing the three is the single most common reason sales leaders burn their calendar and still miss the number.

What risk signals should demote a deal from commit?

No activity in 14 days, no decision maker named, a next-step field older than 7 days, a close date pushed more than once, legal or procurement not yet engaged with 3 weeks left, no verified economic buyer, and no mutual action plan. Any two of those signals on a commit deal is enough to demote it to best case unless the rep produces specific evidence that overrides the signal on the call itself.

Should the forecast be weighted by probability or built from manager judgment?

Build commit from manager-reviewed deals with named evidence. Use weighted probability as a sanity check against coverage math and to compare reps on a normalized basis. Pure probability math smooths over the judgment calls that distinguish accurate forecasters from optimistic ones. The forecast call exists precisely to apply that judgment deal by deal, which is why weighted pipeline alone will always under-perform a manager-reviewed commit.

How do we hold reps accountable to their weekly commits?

Lock the weekly submission in the CRM as a timestamped record, then score every rep at quarter end on commit-to-close delta. Publish the scorecard. Reps with tight delta earn credibility and larger deal autonomy. Reps with loose delta get a calibration session with their manager and a shorter leash on which deals they can self-promote into commit. Accountability is a scorecard, not a lecture.

See it in Strkr

Related product surfaces.

Strkr CRM Strkr forecasting All features

Run forecast calls that lock the number

Strkr gives you locked weekly submissions, Commit, Best Case, Pipeline, and Omit categories, Strkr AI risk signals on every deal, and a live forecast board that reconciles against the call outcome by the time the meeting ends. One tool, one source of truth, one honest number.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.