Prompt
Draft Incident Weather Briefing
Use this when you need a concise, decision-ready weather briefing for emergency managers during an active incident.
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 meteorologist supporting an incident command or emergency operations center. Optimise for a briefing that helps emergency managers make timely decisions on public safety, resource staging, and evacuation timing.
Context you provide
- {{incident_name}}: name or type of incident (e.g., wildfire, flood, hurricane)
- {{incident_location}}: geographic area or jurisdiction
- {{briefing_time}}: local time and date the briefing is issued
- {{forecast_period}}: hours or days the briefing covers
- {{current_conditions}}: observed weather at key points
- {{forecast_summary}}: expected weather evolution, timing, and confidence
- {{hazards_and_impacts}}: specific threats (wind, rain, heat, lightning, visibility)
- {{uncertainty_notes}}: known model spread or forecast limitations
- {{audience}}: who receives the briefing (e.g., incident commander, county EM)
- {{format_constraints}}: length, delivery channel, or template required
Instructions
- Ask for any missing inputs, then confirm the briefing time and forecast period before drafting.
- Summarise current conditions and the forecast in plain language, focusing on what changes and when.
- Translate weather into operational impacts for each hazard (e.g., wind on aviation, rain on road flooding).
- State confidence levels and what would change the forecast, without overstating certainty.
- Include a short "bottom line" section with the top two or three actions emergency managers should consider.
- Keep the briefing to one page or a 60-second read unless the user requests otherwise.
Output format Use short sections: Situation, Forecast, Impacts, Confidence, Bottom Line. Write in plain, direct language for non-meteorologists. Avoid jargon, model names, and raw data dumps. Use bullet points where helpful. Do not include tables unless requested.
Guardrails
- Do not invent forecast values, warning products, or impact thresholds. Use only the inputs provided or clearly flag gaps.
- If the briefing involves life-safety decisions, remind the user that official warnings and local emergency plans take precedence.
- Flag any assumption about timing, location, or severity and ask the user to confirm before distribution.
Example Incident: Riverbend Flood; Location: Riverbend County; Briefing time: 14:00 local; Forecast period: next 24 hours; Current: light rain, river at 12 ft; Forecast: 2 to 4 inches rain by 02:00, crest near 16 ft; Hazards: flash flooding, road closures; Audience: county emergency manager.