Evaluate past forecast variances to set accurate targets
Analyze past forecast misses to identify systematic over- or under-projection patterns. Use this before locking in next quarter's revenue or operational targets.
You getError Summary Table, systematic Bias Analysis and corrective Rules for Next Cycle
Prompt
Act as a quantitative demand planner. I will provide past forecast numbers alongside the actual realized outcomes.
Evaluate the forecast errors using these rules:
- Calculate Mean Absolute Percentage Error (MAPE) and directional bias (systematic over-forecasting vs under-forecasting).
- Categorize the root causes into timing discrepancies, pipeline overestimation, or demand volatility.
- State which specific line items or segments show the lowest forecasting reliability.
- For operational planning purposes only; not formal accounting advice.
Output format:
1. Error Summary Table (Period/Segment, Forecast, Actual, Variance %, Error Type)
2. Systematic Bias Analysis (bulleted findings on recurring prediction flaws)
3. Corrective Rules for Next Cycle (3-4 explicit guardrails to apply to future projections)
Here are my historical forecasts and actual results:Example output
Paste your past projection figures along with actual results by month or quarter into Claude, ChatGPT, or Gemini. Follow up by asking what error threshold should trigger an automatic mid-quarter forecast adjustment.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build three scenarios for revenue and demand forecasts
Generate structured best, base, and worst-case forecast models to prepare for demand swings. Use this during annual planning or runway updates.
Isolate regional or platform drivers behind KPI drops
Break down aggregate product or revenue declines across platform and geographic dimensions. Use this when global numbers drop and leadership needs the root driver.
Analyze support ticket trends by category
Spot surging ticket drivers and recurring bugs across support logs. Use this to allocate team coverage and escalate product flaws quickly.
Convert monthly operations metrics to executive updates
Translate complex monthly performance metrics into a concise executive briefing. Use this before executive staff meetings to showcase key wins and blockers.
Summarize weekly metric anomalies into executive briefings
Convert raw week-over-week metric spikes and drops into concise executive briefs with business context and next steps.
Compare planned versus actual project hours
Spot budget leakages and hidden scope creep by auditing estimated versus actual hours. Use it during mid-project reviews or client budget checks.
- Select three core KPIs for your business goal
- Map and inspect an unfamiliar data export
- Create an anomaly investigation checklist for analytics teams
- Differentiate structural null values from missing data
- Estimate potential revenue recovery across funnel drop-off points
- Map inconsistent export columns to target schemas