Write an incident summary

Record what happened without blurring facts and hypotheses.

What this starting point does

Write an incident summary from the supplied notes. This is an editable instruction template, not a claim of tested performance on a particular model.

Make the inputs yours

• Reference material — fill {{MATERIAL}} with your own material, preserving line breaks where useful. This input is required for a filled prompt.

Reusable template

## Task
Write an incident summary from the supplied notes.

## Constraints
- Separate confirmed events, hypotheses, and unknowns.
- Do not invent impact, timestamps, or root cause.
- Keep sensitive details out of a public-facing version.

## Output format
Impact, timeline, evidence, response, unresolved causes, and follow-up actions

## Reference material
<source_material>
{{MATERIAL}}
</source_material>

A filled example

This example uses fictional demonstration material. It is an example prompt, not a generated answer or image.

## Task
Write an incident summary from the supplied notes.

## Constraints
- Separate confirmed events, hypotheses, and unknowns.
- Do not invent impact, timestamps, or root cause.
- Keep sensitive details out of a public-facing version.

## Output format
Impact, timeline, evidence, response, unresolved causes, and follow-up actions

## Reference material
<source_material>
The local export failed during a test. The working draft remained visible. The cause and affected browser version are not yet known.
</source_material>

Before using it

Review every instruction and replace the example material. Check that its constraints fit your task. The structural Analyzer can flag specific issues, but cannot verify facts or guarantee the quality of a model’s response.