Sales Methodology & Revenue OperationsTemplate4 min readUpdated September 2026

Building a B2B Sales Forecast Worksheet Your Team Will Use

A workable B2B sales forecast has one row per open deal, a forecast category set by rules instead of hope, and a weekly review that compares last week's call with what happened. Start with a spreadsheet or your CRM's forecast view, then add a coverage check against quota.

Most forecasts miss because categories are subjective and nobody measures the miss. The worksheet below fixes both: every deal carries evidence for its category, and every week you record the number you called so accuracy becomes something you can improve, not just something you apologize for.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

What columns does a forecast worksheet need?

Keep it to the fields that change the answer. One row per open deal:

  • Account and owner: who is responsible for the call.
  • Amount and close date: in the currency and period you forecast.
  • Stage: taken from your pipeline definitions, not the rep's mood.
  • Forecast category: commit, best case or pipeline (defined below).
  • Evidence for the category: one line, such as "budget owner confirmed, legal review started."
  • Next step and date: a deal with no dated next step can't be in commit.
  • Last buyer activity: the date the buyer last replied or attended a meeting, not the rep's last touch.
  • Change since last week: amount, date or category moved, and why.

The last column is the one that pays for itself. A category that changes without a reason is a forecast you can't trust.

How should you define commit, best case and pipeline?

Write rules so two reps classify the same deal the same way:

  1. Commit: the buyer has confirmed budget and the decision process, the paperwork is moving and the close date is agreed by the buyer. You'd be surprised if it slipped.
  2. Best case: the deal is real and progressing but at least one of those items is unproven, such as legal not started or the economic buyer not met.
  3. Pipeline: everything else that's open and could close in the period, with less evidence.

Only commit and best case go into the call. A manager can override a category, but must write down why, so the rule stays honest. If your team argues about definitions every week, the definitions are too vague, not too strict.

Weighted forecast or commit forecast: which should you show?

A weighted forecast multiplies each deal's amount by a stage probability and adds it up. A commit forecast counts only deals that meet your commit rules. They answer different questions, and the weighted versus commit comparison explains when each one misleads.

For a small team with few, large deals, weighting is noisy. Say you have five open deals and one is worth half the quarter. A weighted total blends that deal into a fraction that will never actually happen, since it closes or it doesn't. In that case, use commit plus a short list of best-case deals, and discuss the big ones individually.

With many similar deals, weighting works better, but only if your stage probabilities come from your own history. The average B2B new-logo win rate is 19 percent1, which is a reference, not a substitute for counting your own conversions.

How do you check coverage against quota?

Coverage compares the pipeline you have with the number you need. Divide open pipeline for the period by the remaining quota. If your historical win rate on qualified pipeline is low, you need more coverage than if it's high.

Work it through with an example. Say your team needs $500,000 more in closed revenue this quarter, and your history says about one in four qualified opportunities closes. In this example, you'd need around $2,000,000 of qualified pipeline to have an even chance. If you only have $1,000,000, the forecast problem is really a pipeline creation problem, and no amount of careful categorizing fixes it.

Recalculate coverage weekly, and split it by stage age. Pipeline that's mostly early stage with weeks left in the period is less reliable than the same total sitting in later stages.

How to run the weekly forecast routine and measure accuracy

Once a week, on the same day:

  1. Owners update category, amount, date and evidence for their deals before the meeting.
  2. The manager reviews every change since last week and asks for the reason.
  3. Someone records the number called this week in a separate tab, next to the actual results at period end.
  4. At period end, compute the gap between the called number and the result, by rep and by category.

After two or three periods, you'll see patterns: a rep who always calls high, a category that slips more than others, a deal size that's harder to time. Adjust definitions and coaching from that, not from gut feel.

Forecast tools like Clari or Gong can automate roll-ups and flag deal changes. They don't replace the definitions above, so get the rules right in a spreadsheet first. Keep the meeting short and built around deal inspection, not status reading.

Executive Capability Standard

What Good Looks Like

The forecast is built from written category rules with evidence per deal, checked against coverage, and its accuracy is measured every period.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Write down commit, best case and pipeline rules and test them against the last two quarters of closed deals.
2. Do Manually:Keep the worksheet in a spreadsheet, update it weekly and log the called number beside the actual result.
3. Delegate:Have a sales manager or ops lead run the weekly review and own the accuracy log.
4. Automate:Pull deal fields from the CRM into the worksheet so category, amount and date changes are tracked automatically.
5. Buy:Adopt a forecasting tool once your rules are stable, so roll-ups and change tracking stop depending on manual updates.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Clari

Fits a team with stable forecast rules that wants roll-ups and week-over-week change tracking handled in software.

Visit Clari→
Gong

Fits a team that wants call and email evidence feeding the review of which deals belong in commit.

Visit Gong→

Frequently Asked Questions

What is the difference between commit and best case in a sales forecast?

Commit means the deal meets your written evidence rules, such as confirmed budget, a known decision process and an agreed close date. Best case means the deal is progressing but at least one of those is unproven. Keep the definitions written and consistent across reps.

How often should a sales forecast be updated?

Weekly is the usual rhythm, with owners updating deals before the review. Update sooner when a large deal changes materially. Record each week's called number so you can measure accuracy at the end of the period.

How do you measure sales forecast accuracy?

Compare the number you called at a fixed point in the period, such as the start of the final month, with the closed result. Track the gap by rep and by category. Persistent bias in one direction shows where definitions or coaching need to change.

Should a small team use a weighted forecast?

Often not. With a handful of large deals, a weighted total describes an outcome that won't happen, since each deal either closes or doesn't. Use commit and best-case lists and discuss the biggest deals one by one.

Sources

Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.

  1. Average B2B new-logo win rate. Ebsta x Pavilion 2025 GTM Benchmarks Report, 2025.

Related Guides