Demand Forecasting Reasoning Chain

validated business chain v1.0.0 cc-by-sa

Block ID: 4ea49239-95c4-4243-8965-8f20e643143c

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Build a demand forecast for {forecast_context} that's honest about its own uncertainty. (1) Start from the base rate: the actual historical demand and its trend and seasonality, because a forecast anchored to demonstrated history is more reliable than one built from aspiration, and the most common forecasting error is starting from the target you want rather than the pattern you have. (2) Decompose demand into drivers you can reason about separately — underlying trend, seasonal pattern, known upcoming events, and any structural change — rather than forecasting the aggregate as one opaque number. (3) Adjust for what's genuinely different going forward (a new product, a market shift, a lost or won customer), distinguishing evidence-based adjustments from hopeful ones, since every optimistic tweak compounds into a forecast no one can hit. (4) Produce a range, not a point: a low, expected, and high scenario with the assumptions that separate them, because a single-number forecast hides the risk that actually drives planning decisions. (5) Identify the assumption the forecast is most sensitive to and how wrong it could plausibly be. (6) State the forecast range, its key assumptions, and how it should be used — for planning capacity and inventory against the range, not betting the business on the midpoint — and commit to revising it as actuals arrive rather than defending the original.

Build a demand forecast for {forecast_context} that's honest about its own uncertainty. (1) Start from the base rate: the actual historical demand and its trend and seasonality, because a forecast anchored to demonstrated history is more reliable than one built from aspiration, and the most common forecasting error is starting from the target you want rather than the pattern you have. (2) Decompose demand into drivers you can reason about separately — underlying trend, seasonal pattern, known upcoming events, and any structural change — rather than forecasting the aggregate as one opaque number. (3) Adjust for what's genuinely different going forward (a new product, a market shift, a lost or won customer), distinguishing evidence-based adjustments from hopeful ones, since every optimistic tweak compounds into a forecast no one can hit. (4) Produce a range, not a point: a low, expected, and high scenario with the assumptions that separate them, because a single-number forecast hides the risk that actually drives planning decisions. (5) Identify the assumption the forecast is most sensitive to and how wrong it could plausibly be. (6) State the forecast range, its key assumptions, and how it should be used — for planning capacity and inventory against the range, not betting the business on the midpoint — and commit to revising it as actuals arrive rather than defending the original.

Variables

Name	Type	Required	Trust level
forecast_context		yes

forecastingdemand-planningplanningchain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18