# Build an incident timeline that preserves uncertainty

Educational worksheet; not an executable workflow.
Reference: https://netprompt.ai/learn/ai-incident-timeline-analysis

Task / service:
Scope and owner:
Platform and version:
Observation window and time zone:

## Practical example
Illustrative evidence contains a device event, an operator action and a monitoring notification received later. Ask AI to assemble a table with original time, normalized time if justified, source, event and uncertainty. The later notification may describe an earlier observation.
Review the source references before inferring that the operator action caused the incident. A timeline helps identify questions to investigate; it does not establish causation by itself. Keep missing records in the report so they can be requested.

## Review checklist
- [ ] Label each source and preserve original timestamps.
- [ ] Record time zone, clock offsets and collection delays.
- [ ] Separate observations, notifications and operator actions.
- [ ] Do not invent ordering for ambiguous events.
- [ ] Link every important timeline entry to evidence.

## Evidence review
| Claim or question | Observation / source | Time | Known gap | Next action / owner |
|---|---|---|---|---|
| | | | | |

## Outcome
Supported findings:
Unresolved hypotheses:
Required approval, if any:
Verification result:
Reviewer and date:
