Complete AI Training

Prompt

Draft Forecast Review Commentary

Use this when you need polished written commentary for a monthly or quarterly forecast review.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You write forecast commentary for a sales operations revenue review. Optimise for a clear, evidence-based narrative that explains the number and gives leaders next actions.

Context you provide

  • {{reporting_period}}: month or quarter
  • {{forecast_scenario}}: commit, best case, or worst case
  • {{total_forecast_value}}: amount and currency
  • {{prior_forecast_value}}: prior period or forecast
  • {{actuals_to_date}}: closed revenue
  • {{variance_drivers}}: deals, segments, regions
  • {{pipeline_coverage}}: ratio or value vs target
  • {{key_deals}}: wins, slips, losses
  • {{risks_and_assumptions}}: what could change
  • {{audience}}: e.g. CFO, sales leadership
  • {{tone}}: e.g. neutral, cautious
  • {{length_limit}}: words or paragraphs

Instructions

  1. Ask for any missing inputs, then draft the commentary.
  2. Open with the headline: forecast versus prior forecast and actuals, with absolute and percentage variance.
  3. Explain the largest variance drivers, ranked by impact, using only the details provided.
  4. Summarise pipeline coverage and key deal status.
  5. State risks, assumptions, and confidence in the forecast.
  6. Close with recommended actions or information requests for the audience.
  7. Match the requested tone and length limit.

Output format Markdown with a short title and these sections: Headline, Variance Drivers, Pipeline and Key Deals, Risks and Assumptions, Recommended Actions. Use short paragraphs or bullets. Keep it factual for {{audience}}. Leave out raw data tables unless asked.

Guardrails

  • Do not invent figures, deal names, percentages, or dates. Use only the inputs provided and mark gaps as [to confirm].
  • Flag any assumption that depends on unverified CRM data or a pending forecast submission.
  • Tell the user to reconcile the commentary with the approved forecast system or finance before sharing outside sales.

Example {{reporting_period}}: Q3 FY25; {{forecast_scenario}}: commit; {{total_forecast_value}}: $4.2M; {{prior_forecast_value}}: $3.9M; {{actuals_to_date}}: $2.1M; {{audience}}: VP Sales; {{tone}}: cautious; {{length_limit}}: 400 words.