Incident / Exception Report

Document what went wrong clearly and constructively.

Updated Jun 14, 2026

Why it works: Separating root cause from blame keeps the report factual and defensible, and bundling in a customer-facing note means one prompt covers both internal and external needs.

💡 The original prompt — works in any model. Start here, then tune per model.

Fill in the blanks — your answers carry across every model

Incidente.g. database replication failure · payment gateway timeout during peak hoursImpacte.g. users unable to complete transactions (10k+ active sessions affected) · payment processing halted for 2 hours across all regionsActione.g. restored from last known good backup and verified integrity · applied security patch and implemented automated configuration checks

fill the blanks above ↑

🔀 Remix this prompt — make it yoursremixes credit the lineage & grow your garden

← NeLocker vault

Incident / Exception Report

Document what went wrong clearly and constructively.

Updated Jun 14, 2026

Why it works: Separating root cause from blame keeps the report factual and defensible, and bundling in a customer-facing note means one prompt covers both internal and external needs.

💡 The original prompt — works in any model. Start here, then tune per model.

Fill in the blanks — your answers carry across every model

fill the blanks above ↑

🔀 Remix this prompt — make it yoursremixes credit the lineage & grow your garden