Definition · forecasting
Bottom-up forecasting
Bottom-up forecasting is building a forecast from granular unit-, rep-, or transaction-level inputs aggregated upward. For bottom-up forecasting, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
Also known as bottoms-up forecasting, bottom-up planning
Why it matters
Understanding bottom-up forecasting matters because planning only improves decisions when assumptions, drivers, owners, and time periods are explicit enough to revisit when actuals arrive. When the term is tied to a source system, owner, and review cadence, it becomes easier to audit assumptions, catch changes early, and keep operators aligned.
In practice
Planning example
Teams use bottom-up forecasting when a forecast, budget, or scenario needs an assumption that can be revisited. The finance team should know the driver, source data, owner, and period before using it in a model.
Review example
Bottom-up forecasting should be reviewed whenever the source system, calculation logic, time period, or decision owner changes. That keeps the definition useful instead of letting it drift into a label.
In practice, teams should define bottom-up forecasting with a clear source, owner, time period, and decision before they use it in reporting, planning, or operating reviews.
Understanding bottom-up forecasting matters because planning only improves decisions when assumptions, drivers, owners, and time periods are explicit enough to revisit when actuals arrive. When the term is tied to a source system, owner, and review cadence, it becomes easier to audit assumptions, catch changes early, and keep operators aligned.
A strong workflow for bottom-up forecasting separates the definition from the action: first agree what the term means, then decide how it is measured, when it changes, and who is accountable for the next step.
FAQ
What is bottom-up forecasting?
Bottom-up forecasting is building a forecast from granular unit-, rep-, or transaction-level inputs aggregated upward. For bottom-up forecasting, the useful boundary is the driver, assumption, source data, owner, time period, scenario logic, and decision the model is meant to support.
Why is bottom-up forecasting more detailed?
Teams use bottom-up forecasting when they agree on the source data, time period, owner, and decision it supports. Here, it covers building a forecast from granular unit-, rep-, or transaction-level inputs aggregated upward, so the term should be reviewed before it is used in reporting, planning, or operating decisions.