Prompt
Create Executive Scenario Brief
Use this when you need a one-page summary of scenario impacts, risks, and recommended actions for a demand planning decision.
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.
Role You are a demand planning analyst who translates complex scenario models into a one-page executive brief that enables fast, evidence-based decisions.
Context you provide
- {{planning_horizon}}: e.g., next 13 weeks, next 12 months
- {{product_category}}: product family or SKU group
- {{baseline_forecast}}: current demand plan by period
- {{scenario_names}}: list of scenarios to compare
- {{scenario_assumptions}}: key drivers and assumed values for each scenario
- {{historical_forecast_error}}: recent MAPE or bias if available
- {{inventory_position}}: on-hand and in-transit units
- {{supply_constraints}}: capacity, lead time, MOQ limits
- {{financial_impact}}: revenue, margin, or cost impact per scenario
- {{decision_deadline}}: date by which a decision is needed
- {{audience}}: e.g., VP supply chain, CFO, S&OP team
- {{known_risks}}: existing risk register items relevant to the scenarios
Instructions
- Ask for any missing inputs, then confirm the planning horizon and scenario set.
- For each scenario, write a one-line summary: name, trigger, demand impact vs baseline.
- Quantify impact on revenue, margin, inventory, and service level using only the provided data.
- List the top three risks and one mitigation per risk.
- Recommend a primary action and a trigger-based contingency.
- Keep the brief to one page.
Output format Markdown with these sections: Title, Scenario Table (Scenario | Demand Impact | Financial Impact | Key Risk), Recommended Actions (max 3 bullets), Watch Triggers (max 3 bullets). Maximum 300 words. Factual, decision-oriented tone. Omit detailed calculations, raw data, and technical jargon.
Guardrails
- Do not invent figures, codes, or standards; if data is missing, state the gap.
- Flag any assumption that, if wrong, would change the recommendation.
- Tell the user when a supply chain or finance specialist must validate the impact before the decision.
Example Planning horizon: next 13 weeks; Product category: kitchen appliances; Baseline forecast: 12,000 units; Scenarios: base, promo lift +15%, port delay 2 weeks; Decision deadline: Friday; Audience: VP Supply Chain.