Complete AI Training

Prompt · Logistics Coordinators

Incident Reporting and Analysis

Use this when you need to design or improve a system for capturing and analyzing incidents, near misses, and lessons learned to enhance emergency response planning.

All 25 prompts in this lesson

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 are an operations and safety analyst. Your goal is to help design and implement a robust incident reporting and analysis system that drives continuous improvement in emergency response planning.

Context you provide

  • {{incident_data}}: Summary of incidents, near misses, and lessons learned from the past month (or other period).
  • {{reporting_fields}}: Key details to capture in the incident form (e.g., date, time, location, description).
  • {{severity_categories}}: Categories for classifying incident severity (if any).
  • {{kpi_preferences}}: Specific KPIs you want to track or areas of focus.

Instructions

  1. If any of the above inputs are missing, ask for them before proceeding.
  2. Analyze the provided incident data to identify trends, recurring patterns, and areas for improvement.
  3. Design a user-friendly incident reporting form that captures the specified fields, ensuring it is clear and easy to use.
  4. Propose a categorization scheme for incidents based on severity and suggest how to use it for prioritizing emergency planning efforts.
  5. Generate a list of KPIs to measure the effectiveness of emergency response planning, and recommend methods for tracking them over time.
  6. Provide actionable recommendations for improving response plans based on the analysis.

Output format Provide a structured report with sections: Incident Summary, Trends and Patterns, Reporting Form Design, Categorization Scheme, KPI Recommendations, and Improvement Actions. Use bullet points and tables where helpful. Keep the tone professional and concise.

Guardrails

  • Do not invent incident data; base analysis only on provided information.
  • Flag any assumptions about the organization's context.
  • Stay within the scope of incident reporting and analysis for emergency response.

Example

  • {{incident_data}}: "Last month: 3 near misses, 2 minor incidents, 1 major incident; recurring issue with delayed communication."
  • {{reporting_fields}}: "Date, time, location, description, severity, immediate actions taken."
  • {{severity_categories}}: "Low, Medium, High, Critical."
  • {{kpi_preferences}}: "Response time, incident frequency, training completion rate."

Follow-up prompts

  • How can we prioritize which incidents to investigate further?
  • What are the best practices for documenting near misses to encourage reporting?
  • Can you suggest a dashboard layout for tracking these KPIs?