Late revisions remained common
Forecast changes concentrated near month-end and quarter-end even when the underlying operating condition had emerged earlier.
← All use casesThe unexplained
Composite case 06
The unexplained
forecast pattern.
Each forecast was defensible. The recurring pattern was not.
Illustrative composite
Stonebridge Equity Partners, Vector Industrial Systems, their executives and the events described on this page are fictional. The case illustrates how Enterprise Reliability can examine recurring forecast variance. It does not present client information, documented results or field validation. Proprietary assessment instruments, scoring standards and implementation methods are not disclosed.
THE RECURRING PATTERN
No single forecast appeared unreasonable.
Stonebridge Equity Partners acquired Vector Industrial Systems three years earlier. Vector designed, installed and serviced automated production equipment for food, packaging and consumer-products manufacturers.
The company earned revenue from equipment sales, installation, replacement parts and maintenance contracts. Its projects required coordination among customers, engineering teams, equipment suppliers, field technicians and local permitting authorities.
Forecasting was never exact. Timing mattered.
The concern was not an occasional miss. Vector’s forecasts repeatedly changed late in the reporting period, after management had already affirmed the assumptions supporting them.
The explanations differed each time. A customer delayed facility access. A component supplier missed a delivery. An installation required additional engineering. A contract approval took longer than expected. A service renewal moved into the following quarter.
Each explanation was credible.
Together, they formed a pattern that the reporting process did not explain.
Finance introduced more detailed templates. Regional leaders submitted weekly updates. Sales opportunities received probability categories. Operations provided installation schedules. The executive team reviewed material projects twice each month.
Reporting increased.
Forecast reliability did not improve.
The company continued carrying expected revenue until late in the period. When the forecast changed, the revised explanation often described an event that operating personnel had known about weeks earlier.
The information existed. Its effect on the forecast arrived late.
WHAT THE SPONSOR SAW
The forecast moved after the time for useful action had narrowed.
Expected recoveries moved forward
Revenue that slipped from one period frequently appeared in the next forecast without a documented change in the conditions causing the delay.
Independent assumptions appeared reasonable
Sales, operations and finance could each defend their estimates. The consolidated forecast still relied on assumptions that had not been reconciled.
Challenge occurred near the top
The CFO and CEO became responsible for testing cross-functional assumptions that should have been resolved before the forecast reached them.
No single variance established a failure of management. Repetition made the pattern difficult to dismiss.
THE BUSINESS QUESTION
What caused reasonable operating assumptions to become an unreliable enterprise forecast?
The sponsor could have concluded that the forecasting model needed more detail, regional leaders were too optimistic or finance needed stronger controls.
Each explanation could account for part of the variance. None explained why experienced managers using increasingly detailed reports continued learning important facts too late.
The issue sat upstream of the spreadsheet.
Enterprise Reliability would examine how the forecast was produced through decisions, interpretations, commitments and dependencies across the company.
Did Vector’s forecast reflect the operating evidence available to the enterprise, or the assumptions that remained easiest for each function to defend?
01Operating signal emerged
→02Local interpretation formed
→03Commitment held
→04Challenge came late
→05Forecast reset
THE RECONSTRUCTED PROJECT FORECAST
One customer installation showed how the variance developed.
Vector had contracted to install an automated packaging line representing approximately $7.4 million in revenue. Most of the amount was expected in the fourth quarter.
Original commitment
The commercial team expected customer facility access in early October, and finance included the associated revenue in the fourth-quarter forecast.
First signal
The project manager learned that electrical work at the customer’s facility was behind schedule, but the customer expected to recover the time.
Operating dependency
Installation also depended on a control component from a supplier that warned production capacity was tight.
Commercial interpretation
The customer continued supporting the original completion target, so sales maintained its commitment.
Forecast review
Finance challenged the timing. Sales and operations each described a plausible path to completion, and the forecast did not change.
Combined exposure
Facility access remained delayed while the component shipment moved by ten days. Together, the events removed most of the schedule margin.
Expected recovery
Management approved additional labor and weekend work. The forecast continued assuming year-end acceptance.
Late revision
Customer access moved again in December, and finance shifted most of the project revenue into the first quarter.
THE INTERPRETATION
The late change did not begin in December.
Relevant evidence had accumulated over several months. No individual signal required immediate removal of the project from the forecast.
The weakness appeared in how the company combined those signals.
Sales evaluated customer intent. Operations evaluated installation feasibility. Procurement evaluated supplier timing. Finance evaluated revenue recognition. Each function answered a legitimate question.
The enterprise needed a different answer: could all required conditions still occur in sequence with enough margin to support the commitment?
No one owned that question.
The forecast survived because each dependency remained individually plausible. The company did not adequately examine the probability of all dependencies holding together.
The final variance appeared financial. Its origin was operational and organizational.
WHAT THE CASE REVEALED
The forecast was revealing the decision system behind it.
The forecast was an output of the decision system
Finance consolidated the forecast, but the assumptions behind it originated across sales, operations, procurement, project management and customers.
More reporting did not resolve different meanings
The company had extensive data but lacked consistent definitions of probability, commitment, readiness, recovery and completion.
Local accuracy produced enterprise error
Each function evaluated the part it understood best. No one owned the interaction among those parts.
Expected recovery became a recurring assumption
Delayed revenue entered the next period before the company fully reconsidered the capacity and dependencies required to deliver it.
Optimism was not the only issue
Managers had legitimate commercial and operating reasons for maintaining their commitments, and the decision environment rewarded recovery.
Senior leaders received unresolved assumptions
The CFO and CEO became the final challenge point for technical, customer, scheduling and capacity questions.
Variance reduced decision time
Late revisions left less time to adjust spending, staffing, financing, customer commitments or board expectations.
Annual results concealed decision variability
Revenue recovered later in some periods, reducing the apparent annual miss without restoring the decision time already lost.
The company’s problem was not uncertainty itself. It was the delay between changing evidence and changing commitment.
THE SPONSOR’S DECISION
Address the system producing the forecast.
The findings would not support replacing the forecast model without further evidence. Vector already had detailed templates, frequent reviews and experienced financial leadership.
They would not support assigning the entire problem to sales optimism or weak accountability.
The sponsor needed to address the conditions that allowed assumptions to remain unresolved until late in the reporting period. That included ownership of cross-functional commitments, the evidence required for base-forecast inclusion and the treatment of expected recoveries.
The purpose was not to eliminate uncertainty. Vector’s business contained real timing risk.
The purpose was to prevent known uncertainty from appearing as unexpected variance.
DIRECTION OF ACTION
What needed to change.
Define commitment levels
Commercial interest, customer intent, operating readiness and financial forecast inclusion should not be treated as equivalent.
Assign cross-functional ownership
One person should integrate the evidence and recommend the enterprise position for each material forecast item.
Make dependencies visible
Material revenue assumptions should identify the customer, supplier, capacity, approval and execution conditions they require.
Test recovery assumptions
Revenue moved into a later period should not enter the new forecast automatically without an updated operating basis.
Escalate contradictory evidence
Material disagreement among sales, operations and finance should remain visible until resolved.
Measure revision timing
Track when a signal first appeared, when management reconsidered the commitment and when the forecast changed.
Longer-term work would address forecast governance, decision rights, information flow, commitment standards and cross-functional dependencies. The proprietary assessment and redesign methods are outside this illustration.
A MORE RELIABLE FORECAST
What improvement would look like.
These are intended operating indicators. Because the case is fictional, no claim is made that an engagement occurred or produced actual results.
- Material assumptions identify their operating dependencies.
- Sales, operations and finance use consistent commitment definitions.
- Contradictory evidence remains visible until it is resolved.
- One person owns each material cross-functional recommendation.
- Forecast changes occur closer to the first material signal.
- Expected recoveries include a documented operating basis.
- Revenue timing and economic opportunity are reported separately.
- Senior management spends less time reconciling routine differences.
- Board discussions focus on material uncertainty and available action.
- Forecast confidence reflects the strength of supporting evidence.
A QUESTION FOR THE SPONSOR
Does the forecast change when the evidence changes, or only when the original commitment can no longer be defended?
The difference affects more than forecast accuracy. It determines how much time the enterprise retains to act.