It Incident Report

Draft a It Incident Report tailored to your inputs.

Prompt template

You are an IT incident report writer. Generate a professional IT incident report in Markdown format.

Incident Title: {{incident_title}}
Incident Date: {{incident_date}}
Description: {{description}}{{severity}}{{root_cause}}{{resolution}}

Write a structured IT incident report in Markdown with the following sections:
- Incident Summary
- Incident Details (date, severity if provided)
- Description
- Impact Assessment
- Root Cause Analysis (use provided root cause or write "Under investigation")
- Resolution & Remediation (use provided resolution or write "Pending")
- Timeline
- Recommendations
- Sign-off

Be professional, concise, and clear.

Fill the 6 fields below to customize.

Customize before copy

Fill these — your prompt updates live.

Stays in your browser. Nothing sent anywhere — we don't run a server for this.

Incident Title*{{incident_title}}

Incident Date*{{incident_date}}

Description*{{description}}

Severity*{{severity}}

Root Cause*{{root_cause}}

Resolution*{{resolution}}

Using Gemini, Llama, Mistral or local LLMs? Copy the prompt and paste — no deep-link supported.

Sample

Example output

What the prompt produced when KLI ran it for a real case. Yours will vary by model and inputs.

# IT Incident Report

## Incident Summary

**Title:** ${incidentTitle}
**Date:** ${incidentDate}
**Severity:** ${severity ?? "Not specified"}
**Status:** ${resolution ? "Resolved" : "Open"}

## Description

${description}

## Impact Assessment

This incident had an impact on system availability and/or data integrity. Further assessment is required.

## Root Cause Analysis

${rootCause ?? "Under investigation. A full root cause analysis will be conducted."}

## Resolution & Remediation

${resolution ?? "Pending. The team is working on a resolution."}

## Timeline

| Time | Event |
|------|-------|
| ${incidentDate} | Incident reported |
| TBD | Investigation started |
| TBD | Resolution applied |

## Recommendations

1. Review monitoring and alerting thresholds.
2. Update runbooks to address this incident type.
3. Schedule post-incident review meeting.

## Sign-off

| Role | Name | Date |
|------|------|------|
| Incident Manager | | |
| Technical Lead | | |
| Stakeholder | | |

Cyber Incident Response Plan

Draft a Cyber Incident Response Plan tailored to your inputs.

Privacy & Security

Data Breach Notice

Draft a Data Breach Notice tailored to your inputs.

Privacy & Security

Privacy TOS

🇮🇳

Draft a Privacy TOS tailored to your inputs.

Privacy & Security

Employee Privacy Policy

Draft a Employee Privacy Policy tailored to your inputs.