Explain Forecast Changes with an Evidence Log

A forecast revision is more useful when someone can explain why it changed. Replacing last week's number with this week's number hides whether the difference came from buyer news, a corrected amount, a timing change, or a new forecasting rule. Keep the prior view and build a short bridge to the current one.

This article concerns internal sales planning, not financial reporting or investment advice. Use your organization's approved definitions for contract value, revenue, currency conversion, and forecast categories. The change log should preserve those definitions so a revised total is not mistaken for an equivalent measure calculated differently.

Freeze the comparison before explaining the movement

Record the prior submission date, period, currency, included opportunities, and measurement basis. Then record the equivalent current view. If the basis changed, explain that first; comparing weighted pipeline with total contract value would produce a misleading difference even if no buyer changed their plans.

HubSpot: Use the forecast tool documents past forecast submissions in supported HubSpot setups. Verify subscription, permissions, and the history actually available in your account. If your approved system lacks the needed snapshot, preserve a proportionate internal record before the next submission rather than claiming you can reconstruct data that was never retained.

A system history answers what changed in the system. Your explanation also needs the relevant business evidence and any assumptions that remain unresolved.

Use a reason code that preserves causality

Useful categories include buyer-confirmed timing change, scope revision, record correction, duplicate removal, and methodology change. Allow more than one category when necessary, but separate the amount attributable to each rather than attaching a vague market conditions label to the entire movement.

For each changed opportunity, retain its identifier, old and new values, supporting source, effective date, entry date, owner, and remaining uncertainty. A source date and the day someone edited the CRM may differ. Preserve both when the distinction matters to the review.

Complete an illustrative forecast bridge

A fictional team submits an October forecast of US$220,000 on 9 October 2026. It uses unweighted expected contract amounts under a defined internal inclusion rule. On 23 October, the equivalent estimate is US$170,000. These figures illustrate arithmetic and documentation, not real performance or a recommended forecasting method.

The change log contains three entries:

• Opportunity A17: US$40,000 removed from the October period. A buyer's 16 October message says its decision will not occur before December. The record is updated on 17 October. December is an earliest boundary, not a confirmed closing date; the opportunity is not automatically added to a December commitment.

• Opportunity B08: amount reduced from US$50,000 to US$35,000 after a buyer-agreed scope reduction recorded on 20 October. The US$15,000 decrease concerns scope, not confidence. Final contracting remains unconfirmed.

• Opportunity C22: US$5,000 added after correcting an omitted approved option in the internal estimate. The correction is dated 22 October and linked to the existing scoped document. It is labeled data correction, not new buyer progress.

The bridge is US$220,000 minus US$40,000 minus US$15,000 plus US$5,000, producing US$170,000. Keep the original US$220,000 submission intact. The current view is different because the evidence and record changed, not because history is being restated.

Separate a corrected past report from a new forecast

Sometimes a prior submission contained an error under the rules that already applied at the time. Preserve the original and mark any authorized corrected version explicitly. Do not silently replace it and then judge the original decision against the corrected data as though everyone knew it earlier.

A new assumption is different. If management changes the inclusion rule, show a methodology effect separately from deal-level changes. Otherwise a more conservative policy may look like sudden deterioration in buyer behavior, or a looser policy may look like improved sales performance.

Explain uncertainty without hiding behind it

Write the unresolved question in practical terms. Opportunity A17 still lacks an agreed decision date; B08 still requires final contracting; C22's amount was corrected but its stage did not advance. Those statements tell a reviewer what could change the next forecast.

Avoid attaching invented probabilities to missing facts. A precise-looking confidence score cannot repair an unsupported timing assumption. Follow the team's defined methodology and flag where evidence is inadequate for its use.

End the review with the current estimate, the bridge, and the next evidence that would justify another revision. A transparent decrease is often more useful than an unexplained stable number. The log should make changed expectations understandable without turning yesterday's uncertainty into a story that appears inevitable today.

Continue with Create a Weekly Pipeline Review That Ends with Decisions or Keep Research Notes Separate from Customer Commitments.