Incident Note Template
A compact operator note format for capturing symptoms, checks, decisions, and follow-up while the issue is fresh.
Good For
- support handoff
- post-incident review
- change notes
- repeat troubleshooting
How to Use It
- Symptom: What broke, who saw it, and when it started.
- Scope: Affected users, systems, sites, services, and networks.
- Checks: Commands, logs, dashboards, and observations with timestamps.
- Action: What changed, who approved it, and what risk it carried.
- Validation: How you proved the issue was fixed or contained.
- Follow-up: Any cleanup, monitoring, documentation, or prevention work.
Execution Modes
- local
Inputs and Outputs
Inputs
- symptom
- scope
- timeline
- checks
- actions
- validation
Outputs
- operator-notes
Validation
- Another operator can understand the timeline without asking for context.
- The note separates observations from guesses.
- Follow-up tasks are specific and assigned.
Reporting
- ticket note
- handoff note
- post-incident summary
Safety Notes
- Separate observations from assumptions.
- Avoid including secrets or sensitive customer data in reusable templates.