Blog · Forecast and pipeline · Sales teams
A useful sales forecast meeting explains what changed, which deals support the number and who will act next. Build the review from frozen pipeline snapshots, check the movement by deal and rep, and leave with an evidence-based action list.
A sales forecast meeting should explain what changed in the forecast, test the evidence behind those changes and assign the actions needed before the next submission. Start with two frozen pipeline exports for the same sales period. An unchanged total can conceal a slipped deal, a larger order and a new commitment that carry very different risks.
Choose the measure first: bookings, invoiced revenue or recognized revenue. A pipeline close date can support a bookings forecast without proving when revenue will be recognized. Finance and sales must agree on the period, currency and measure before discussing confidence.
Export the prior submitted snapshot and the current review snapshot. Keep the original exports intact. Each needs a snapshot date, stable deal ID, account, rep, expected close date, amount, forecast category and submitted forecast contribution. Include the evidence date and the next customer milestone where those fields exist.
Build a comparison containing every deal ID from either snapshot. A deal that disappears must remain visible until someone establishes whether it was lost, moved outside the period or excluded by a filter. A zero is appropriate for a confirmed absence from the chosen period; an unmatched or missing value needs investigation.
Use the same rules for sales forecast categories in both snapshots. Save category-definition debates for a separate discussion unless the definition itself changed the submission. The review needs a consistent basis that everyone can test.
Consider a fictional US industrial distributor reviewing October 2026 bookings. Its October 9 and October 16 submissions contain the following contributions. Amounts are submitted forecast dollars, not additional probability-weighted amounts.
| Deal | Rep | Prior forecast (USD) | Current forecast (USD) | Change (USD) | Evidence or reason |
|---|---|---|---|---|---|
| Atlas | Elena | 120,000 | 120,000 | 0 | Purchase approval unchanged |
| Beacon | Elena | 80,000 | 0 | -80,000 | Customer moved signing to November |
| Cedar | Marcus | 60,000 | 90,000 | 30,000 | Revised order scope received |
| Delta | Marcus | 0 | 50,000 | 50,000 | Newly included October commitment |
| Total | 260,000 | 260,000 | 0 |
Place those columns in A:F, with data in rows 2:5. In Excel, calculate the change in E2 and fill down:
=D2-C2
Return only changed rows to the review agenda:
=FILTER(A2:F5,E2:E5<>0,"No changes")
Microsoft documents FILTER as returning rows according to defined criteria. Keep the full comparison alongside the filtered agenda so unchanged material deals remain available for inspection.
The headline is flat, but the absolute movements total $160,000: $80,000 + $30,000 + $50,000. That figure describes changed contributions; it is not an additional forecast. For the detailed arithmetic behind larger comparisons, use the deal-by-deal forecast bridge.
The first check is an identity:
Prior forecast + Sum of deal changes = Current forecast
Here, $260,000 - $80,000 + $30,000 + $50,000 = $260,000. The spreadsheet check should return zero:
=SUM(C2:C5)+SUM(E2:E5)-SUM(D2:D5)
Then reconcile by rep. If H2 contains Elena, these formulas return her prior contribution, current contribution and change:
=SUMIFS($C$2:$C$5,$B$2:$B$5,H2)
=SUMIFS($D$2:$D$5,$B$2:$B$5,H2)
=SUMIFS($E$2:$E$5,$B$2:$B$5,H2)
Microsoft's SUMIFS reference explains how the function sums rows matching criteria. Use the same approach with a region or forecast-period column when needed. Covirage is not affiliated with Microsoft.
| Rep | Prior forecast (USD) | Current forecast (USD) | Change (USD) |
|---|---|---|---|
| Elena | 200,000 | 120,000 | -80,000 |
| Marcus | 60,000 | 140,000 | 80,000 |
| Total | 260,000 | 260,000 | 0 |
The rep totals must match the deal totals and the actual submitted number. If a deal changed owners, retain both snapshot owners and identify the transfer separately; otherwise a transfer can look like new selling activity.
Circulate the comparison before the meeting. Ask each owner to correct missing evidence before the cutoff, then preserve the version being reviewed. Use this agenda:
For Beacon, the question is whether the documented November signing date removes the deal from October. For Cedar, verify that the revised scope supports the additional $30,000. For Delta, identify the customer milestone supporting October rather than accepting the new category as evidence by itself.
Record an action in observable terms: Elena confirms Beacon's revised signing date with procurement; Marcus obtains Cedar's approved order scope. Give each action a specific deadline before the next submission. The sales manager accepts the forecast assumption; sales operations preserves the record; finance checks how the decision affects the planning measure.
If the discussion needs a downside case, link the assumption to a conservative sales forecast. If product composition explains the change, review a sales mix forecast separately rather than extending this meeting into a full margin review.
Bring your prior and current pipeline exports and the actual results for the same period. Covirage maps the columns, and its tools compute and check deal and rep movements; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.
See Covirage for sales teams for the supporting workflow.
The sales manager owns the submitted forecast, sales operations prepares comparable snapshots, and deal owners explain material changes. Finance should participate when the number feeds revenue planning. Invite other teams only when they own a decision or dependency on the agenda.
Set the cadence around your sales cycle and planning deadlines. A weekly review can suit an active closing period, while longer sales cycles may need less frequent full reviews. Keep the snapshot cutoff consistent so each meeting compares the same elapsed interval.
Discuss changed deals, material risks and decisions that need help. Circulate the complete deal list before the meeting so attendees can inspect unchanged rows. A stable headline total still needs review when losses and additions offset each other underneath it.
Produce an agreed submission with its cutoff, a reconciled explanation of changes, and a dated action list. Keep unresolved evidence separate from confirmed facts. Record who accepted each assumption so the next meeting can test what happened rather than repeat the discussion.