Blog · Forecast and pipeline · Sales teams
Executive opinions forecasting uses management judgment to estimate future sales. Document the assumptions, preserve the original baseline and test whether executive adjustments improve the result.
Executive opinions forecasting uses senior managers' business knowledge to estimate future sales, especially when history is limited or recent events have changed the outlook. Make that judgment testable by recording the assumptions, preserving the original estimate and comparing the result with later actuals.
A management forecast should explain what the business expects under stated conditions. Its value comes from relevant information and accountable review, rather than the seniority of the person supplying the number.
Executives can bring information from sales, operations, product management and finance into the same forecast. A customer commitment, a delayed launch or a capacity constraint may matter before it appears in historical sales.
Hyndman and Athanasopoulos describe executive opinion as senior managers producing aggregate forecasts, often in a group meeting. They emphasize documenting and justifying the process to limit the biases that can arise in that setting.
Use management judgment where the information warrants it. Where dependable history exists, retain an independently prepared baseline and explain each departure. Where no meaningful baseline exists, record the assumptions that produce the first estimate and compare alternative outcomes.
Keep the forecast separate from the desired result. The difference between a budget and a forecast matters when an executive meeting uses both numbers: an approved spending target does not establish the sales customers will deliver.
Define the sales measure, period, currency and business segments. "Next quarter's sales" is ambiguous if one manager means bookings and another means recognized revenue. Finance should approve the measure and reconcile the historical actuals used for comparison.
Ask participants to supply an initial estimate independently, before seeing the most senior person's answer. Collect the evidence, the affected segment, the expected timing and the condition that would invalidate the estimate. This makes disagreement visible before a meeting settles on one number.
| Field | What to record | Review purpose |
|---|---|---|
| Forecast version | Date, cutoff and responsible owner | Preserve what was known at the time |
| Segment | Product, region or customer group | Match estimate to actual rows |
| Baseline | Independently prepared starting estimate | Show the contribution of judgment |
| Adjustment | Signed USD change and business reason | Reconcile the final estimate |
| Evidence | Source record and information date | Distinguish information from optimism |
| Trigger | Event that would change the assumption | Set the next review action |
The facilitator should challenge overlapping adjustments. If sales and operations both reduce the same delayed order, record the effect once. Record unresolved differences as alternative assumptions rather than burying them in an unexplained average.
Consider an illustrative US equipment supplier preparing its September sales outlook. The baseline and adjustments below were frozen before September began. Actual sales were added only after the period closed.
| Segment | Baseline (USD) | Executive adjustment (USD) | Final forecast (USD) | Actual sales (USD) | Actual minus final (USD) |
|---|---|---|---|---|---|
| East | 300,000 | 40,000 | 340,000 | 325,000 | -15,000 |
| West | 250,000 | -10,000 | 240,000 | 230,000 | -10,000 |
| Central | 150,000 | 30,000 | 180,000 | 160,000 | -20,000 |
| Total | 700,000 | 60,000 | 760,000 | 715,000 | -45,000 |
The East owner documented expected customer expansion, West documented a delivery delay and Central documented a launch uplift. These are the reasons supplied by management, not proven explanations for the eventual sales outcome.
Final forecast = Baseline + Documented executive adjustments
Forecast variance = Actual sales - Final forecast
For East, 300,000 + 40,000 = $340,000. Actual sales of $325,000 produce a $15,000 shortfall. Across the company, 700,000 + 60,000 = $760,000, and 715,000 - 760,000 = -$45,000. The segment variances must sum to that same company difference.
All dollar calculations here are exact. The adjustment register's total must also equal $60,000; an adjustment outside the register breaks the reconciliation. Use a revenue driver bridge when management needs to connect that change to the broader revenue review.
A forecast that missed can still improve on its baseline, and a company total can hide unreliable segments. Compare the baseline and final estimate against the same actual rows.
| Segment | Baseline absolute error (USD) | Final absolute error (USD) |
|---|---|---|
| East | 25,000 | 15,000 |
| West | 20,000 | 10,000 |
| Central | 10,000 | 20,000 |
| Total | 55,000 | 45,000 |
Absolute error is the size of each miss regardless of direction. For East, the baseline error is |325,000 - 300,000| = $25,000; the final error is |325,000 - 340,000| = $15,000.
At this segment level, judgment reduced total absolute error from $55,000 to $45,000. Divide by actual sales of $715,000 and the corresponding weighted absolute percentage errors are 7.7% and 6.3%, rounded to one decimal place. Central's adjustment worsened its result, even though the combined absolute error improved.
The forecast accuracy guidance in Forecasting: Principles and Practice distinguishes genuine forecast errors from errors calculated on the history used to fit a forecasting method. Apply the same discipline to management judgment: only information available at the recorded cutoff belongs in the original estimate.
The company baseline happened to be closer to total actual sales because segment misses offset. Review both the company gap and segment errors, then decide which matters for the business decision. Repeat the comparison over subsequent periods before concluding that a particular executive adjustment consistently adds value.
Sales operations should preserve the submitted estimates and assumption register. Finance owns reconciliation to actual sales. The executive making an adjustment owns its business evidence and the decision to maintain, revise or withdraw it in the next forecast.
If an expansion estimate failed because account activity was insufficient, inspect sales coverage before carrying the uplift forward. If the same segment is repeatedly overestimated, review the pattern using the logic of forecast bias by segment.
Bring your baseline, executive estimates, assumption register and subsequent actuals as a file or Google Sheet; Covirage maps the columns, and its tools compute and check the figures. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data; account creation takes about a minute.
See forecast analysis for the supporting business context.
It is useful when executives hold relevant information that history does not yet reflect, such as a documented launch delay or a major customer's changed buying plans. Keep the evidence and affected period visible so the adjustment can be checked when actual results arrive.
A forecast states what management expects to happen under documented assumptions. A target states what the business wants to achieve. Record the gap separately and assign actions to close it, rather than increasing the forecast simply to match the target.
Collect initial estimates independently, use common definitions and require evidence for changes. Preserve the baseline and final estimate, then review errors by business segment. An accountable facilitator should record disagreements and assumptions so a group meeting does not erase uncertainty.