Forecast reporting governance

A forecast is a time-bound view of expected business, not a permanent property of an opportunity. Govern the view and the evidence separately.

Forecast contract

Field	Question
Snapshot time	When was the view taken?
Population	Which opportunities were eligible?
Amount	Which amount field and currency?
Stage	Which stage definition and date?
Judgment	Who set the category and when?
Evidence	What activities or milestones supported it?
Outcome	What happened later?

Do not overwrite a past forecast with today's category. Store a snapshot or versioned event.

Review changes, not just totals

At each review, show new, advanced, slipped, closed, and removed opportunities. Tie each movement to a milestone, stage change, amount change, owner change, or data correction. A total that moved without a reason code is a follow-up item.

Ownership and access

Name who owns forecast category definitions, who enters judgment, who approves a rollup, and who can correct source fields. Restrict sensitive forecast data using the platform's current sharing and permission model. Verify Salesforce forecast features in the official forecast documentation or HubSpot's current sales reporting documentation before implementation.

Caveats

State whether the report includes open records, whether late updates are backfilled, and how currency conversion works. Keep the caveats next to the metric, not in a separate document nobody reads.

Preserve the forecast as known then

A current opportunity record cannot answer what the team believed at an earlier forecast call. Capture dated snapshots or forecast events for amount, stage, close date, category, owner judgment, manager adjustment, and relevant currency basis. Keep the current view for action and the historical view for learning.

Separate source facts from judgment. Stage, amount, and close date may come from the opportunity; forecast category and manager adjustment express a point-in-time view. Report both without pretending they are interchangeable. Require a reason when a material amount, timing, or category changes inside the forecast period.

Run a useful review

Compare opening forecast, current forecast, actual outcome, slipped value, new value, and changes by reason. Inspect records that moved materially, not only the final rollup. Track update coverage and age so apparent stability is not caused by stale opportunities. When definitions or stage rules change, mark the reporting boundary and avoid comparing periods as though nothing changed.

Related: History and snapshot design, Metric ownership and source of truth, and GTM operating review template.