Preserve the number that would have been used without the adjustment
A forecast review meeting may change dozens of estimates, yet the final accuracy report often scores only the last version. That cannot tell management whether the adjustments helped. Save the incoming forecast, each material override and the final issued forecast so their errors can be compared against the same actual outcomes.
The question is specific: did a particular intervention improve the forecast for its intended decision? It is not a contest between a model and a person. A confirmed cancellation or a delayed opening may contain information absent from historical data. An unsupported sales aspiration can push the same number in the wrong direction.
Forecasting: Principles and Practice discusses structured judgmental adjustments and the importance of documenting information not already captured in a model. The review below applies that principle to a practical before-and-after record. Its arithmetic measures observed improvement; it does not establish a universal threshold for allowing an override.
References: Hyndman and Athanasopoulos: Judgmental forecasts
Use one error definition on the same forecast population
Suppose four monthly revenue forecasts, in thousands of dollars, entered review at 100, 110, 120 and 130. The adjusted values were 110, 130, 125 and 140. Actual revenue was 105, 112, 128 and 125. All values refer to the same entities, revenue definition and forecast horizon in this invented example.
The original absolute errors are 5, 2, 8 and 5, totaling 20. The adjusted absolute errors are 5, 18, 3 and 15, totaling 41. The average absolute error therefore increased from $5,000 to $10,250. One adjustment improved the result, one tied and two made it worse.
If the team defines forecast value added as error before adjustment minus error after adjustment, the aggregate value is negative $21,000, or negative $5,250 per month. State that sign convention. A report showing only how often an adjustment was directionally correct could miss how large the damaging changes were.
| Month | Original forecast | Adjusted forecast | Actual | Original / adjusted absolute error |
|---|---|---|---|---|
| 1 | $100,000 | $110,000 | $105,000 | $5,000 / $5,000 |
| 2 | $110,000 | $130,000 | $112,000 | $2,000 / $18,000 |
| 3 | $120,000 | $125,000 | $128,000 | $8,000 / $3,000 |
| 4 | $130,000 | $140,000 | $125,000 | $5,000 / $15,000 |
Explain each override using the information available then
Record the event, evidence date, affected amount, expected period and person supplying the information. A revised customer delivery date is more reviewable than a note saying management confidence. Preserve the original reasoning before the outcome is known; a later explanation cannot establish what informed the decision.
Classify adjustments by their mechanism: confirmed operational event, updated external fact, model defect, commercial judgment or target pressure. The categories should help the business improve its process. Avoid using them to imply that every adjustment in a broad class will have the same accuracy.
A failed prediction does not automatically mean the original evidence was unreasonable. A well-supported customer promise can still change. Review the information quality and the outcome separately so staff remain willing to report uncertainty instead of presenting every new fact as guaranteed revenue.
Separate the effect of an override from later information
The comparison becomes unfair if the original forecast was issued Monday and the adjusted version incorporates Friday's newly available invoices, while the review treats both as Monday predictions. Record issue times and information cutoffs. Compare the adjustment with the forecast that would otherwise have been available at that same decision point.
For a process with several stages, retain the output after each stage. Sales may add customer events, operations may constrain delivery and management may apply a final revision. Stage-by-stage comparisons can reveal where error changes, but only when the stage records and their timing are preserved.
Keep updates to actual history separate from forward overrides. Correcting a duplicated prior invoice changes the model's input data and may rightly change its forecast. Tag that correction as a data repair so its effect is not mistaken for the value of discretionary judgment.
Review the places where intervention helps or hurts
Check directional bias alongside absolute error. In the four-month example, original forecasts total $10,000 below actuals, while adjusted forecasts total $35,000 above them. Under a forecast-minus-actual convention, average bias moves from negative $2,500 to positive $8,750. That helps explain the repeated upward revisions, but it does not justify subtracting $8,750 from every future forecast. First identify whether the same evidence and adjustment behavior recur across a sufficiently relevant set of periods.
Look for repeated patterns in direction, horizon and event type. Small upward changes might differ from large revisions following confirmed disruptions, but let the observed evidence determine the finding. Four months, as in the example, is enough to demonstrate the calculation and too little to establish a stable rule for every business condition.
Report both the changed population and the complete forecast population. If only ten of a thousand rows are adjusted, including all unchanged rows can make the average effect look negligible. Reporting only a few selected successes creates the opposite problem. Retain the full set of eligible overrides and explain the denominator.
Consider the decision cost as well as the accuracy score. A cash forecast adjustment that identifies a payroll shortfall can be useful even if its dollar error does not improve. Record the intervention it supported and evaluate that purpose explicitly rather than quietly replacing the accuracy measure after seeing the result.
Turn the findings into a simpler approval rule
Require enough detail to understand a material change: what new information exists, where it belongs in the forecast and when it should expire or be reviewed. An adjustment added for a one-time event should not become a permanent uplift through repeated copying.
When repeated overrides repair the same missing process, improve the model or its data feed. A monthly manual correction for a known billing schedule is a candidate for a documented input rule. Test that change against the preserved history before removing the old review step.
Keep commercial targets visible in their own planning record. The issued forecast should retain the assumptions on which commitments depend. The review can then reduce unnecessary editing, preserve useful operating knowledge and show whether the forecasting process is becoming more reliable without rewriting its earlier decisions.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.