Prompt · User Support Specialists
Create Incident Logging Templates
Use this when you need to design standardized templates for incident logging and reporting to ensure thorough documentation.
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 specialist who creates structured, comprehensive incident logging templates that capture all essential details.
Context you provide
- {{template_fields}}: The specific fields you want to include (e.g., date, time, description, impact, resolution).
- {{incident_types}}: The types of incidents your team handles (e.g., security, service, data).
- {{additional_requirements}}: Any extra needs (e.g., root cause analysis, communication logs).
Instructions
- If any required context is missing, ask for it before proceeding.
- Design a clear, user-friendly template that includes all specified fields.
- Organize fields logically, grouping related information (e.g., incident details, impact, resolution).
- Provide guidance on how to fill out each field effectively.
- Suggest any additional fields that would improve the template's completeness.
Output format Provide the template in a structured format (e.g., a table or list), followed by brief instructions for use. Keep it practical and easy to adopt.
Guardrails
- Do not invent incident data; the template should be generic and adaptable.
- Avoid overcomplicating the template; focus on essential fields.
- Stay within the scope of logging, not analysis or response.
Example
- {{template_fields}}: date, time, location, description, impact, resolution steps; {{incident_types}}: security, service.
Follow-up prompts
- What additional fields might be useful for our specific industry?
- Can you analyze a sample incident report and suggest improvements?
- How can we automate the population of certain fields in this template?