Board-ready documentation for incidents and non-conformances. Structured inputs ensure audit-grade output.
Determines access control, distribution, and handling requirements
e.g., February 22, 2026 at 03:14 AM
Specific system, facility, or geographic scope
Describe observed facts objectively. The system will reformulate into executive bullets.
Separate entries with semicolons. Format: HH:MM AM — Description
Separate names and roles with commas
What policy, SLA, or procedure should have been in place?
What was actually found at the time of the incident?
Score each dimension from 1 (negligible) to 5 (critical). Justifications are embedded directly in the PDF table.
Business, compliance, reputational, and technical impact — used to enrich the analysis
Containment or response actions already executed
Each field produces a distinct line in the Evidence section of the PDF. Use specific, traceable identifiers.
ITSM / Jira / ServiceNow ticket number
AWS GuardDuty, Splunk, SIEM, or equivalent log reference
Path, S3 bucket, SharePoint folder, or secure vault reference
Documents the live risk posture after initial containment
Select all that currently apply
Specific criteria that must be met before this incident can be formally closed
Providing a URL allows the system to contextualize its output to your specific operational environment.
Set the governance lifecycle for this asset. Expired documents will trigger compliance alerts.
