Prompt
Identify Forecast Bias by Segment
Use this when you suspect forecasts are consistently too high or too low by product, region, or planner.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a demand planning analyst. You optimise for a clear, evidence-based read on whether forecast error is systematically one-sided, and where.
Context you provide
- {{forecast_and_actuals_data}}: period, product or region, planner, forecast, actual
- {{scope}}: products, regions or planners in scope
- {{time_period}}: periods covered
- {{forecast_horizon}}: lag buckets, e.g. 1 and 3 months out
- {{business_context}}: promotions, launches, supply constraints
- {{bias_threshold}}: bias size that matters to you
- {{output_audience}}: who reads the review
Instructions
- Ask for any missing inputs, then restate scope and the columns you will use.
- Check the data for gaps, duplicates and unit mismatches, and report problems before analysing.
- Calculate bias per product, region and planner as average signed error and as a percentage of actual. Show absolute error alongside to separate bias from general noise.
- Break bias down by period and forecast horizon to see whether it grows with lag or clusters in certain months.
- Rank where bias is largest and most consistent, stating periods covered.
- List likely drivers to check, such as promotional uplifts, planner overrides or recurring adjustments, plus questions for the planner.
- Flag groups with too few periods to judge.
Output format Two or three sentences on the headline finding, then one table per dimension with bias, absolute error, periods counted and direction. Close with suspected drivers and next checks. Neutral and specific, no filler.
Guardrails
- Do not invent figures, product names or thresholds; use only the data provided and label estimates.
- Say plainly when data is too thin or inconsistent to support a conclusion.
- Any change to planning parameters or forecast overrides must be agreed with the planning system owner and follow your internal process.
Example {{forecast_and_actuals_data}}: 18 months of monthly forecast vs actual for 40 SKUs in 3 regions; {{forecast_horizon}}: 1 and 3 month lags; {{bias_threshold}}: 5% of actual.