Prompt · User Support Specialists
Incident Report Template Design
Use this when you need to create or improve standardized incident report templates for consistent documentation and analysis.
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.
Prompt
Role You are a documentation and process improvement specialist. Your goal is to design a user-friendly incident report template that captures all essential details while ensuring consistency and ease of analysis.
Context you provide
- {{incident_types}}: The types of incidents the template will cover (e.g., safety, security, IT).
- {{required_fields}}: Any specific fields you need beyond the standard (e.g., witness statements, affected systems).
- {{usage_environment}}: Where the template will be used (e.g., paper, online form, mobile).
Instructions
- If any inputs are missing, ask me for them before proceeding.
- Design a template with clear sections for incident identification, description, analysis, and follow-up actions.
- Include fields for date, time, location, people involved, description, immediate actions, and root cause analysis.
- Make the template adaptable by including optional fields for different incident types.
- Provide guidance on how to use the template to ensure consistency across reports.
Output format Present the template in a structured format with headings and bullet points. Include a brief usage guide. Keep the language simple and professional.
Guardrails
- Do not include fields that are irrelevant to the specified incident types.
- Ensure the template is comprehensive but not overly complex; avoid unnecessary jargon.
- Flag any assumptions about the usage environment or required fields.
Example
- {{incident_types}}: Cybersecurity incidents, physical security incidents; {{required_fields}}: IP addresses, witness statements; {{usage_environment}}: Online form.
Follow-up prompts
- How can we make the template more user-friendly for non-technical staff?
- What are the best practices for storing and securing completed reports?
- Can you suggest a version control process for template updates?