Skip to content
Logo

Incident Log Template

Security SpecialistOperations & StrategyDevOps

Authored by:

Nick K
Nick K
Lido
EK
EK
Lido

🔑 Key Takeaway: The Scribe owns the live incident log. Timestamp decisions, actions, and links continuously so later investigation and post-mortems are reconstruction, not guesswork.

Use this template during active incidents. The Scribe owns this document.

How to Use

  1. Copy this template to your incident logs folder
  2. Name it: YYYY-MM-DD-brief-description (e.g., 2024-03-15-api-outage)
  3. Update in real-time as things happen
  4. Use UTC timestamps, 24-hour format
  5. More detail is better. You can summarize later

Incident:

TITLE

Summary

FieldValue
StatusActive / Mitigated / Resolved
SeverityP1 / P2 / P3 / P4 / P5
Start TimeYYYY-MM-DD HH:MM UTC
Resolution Time
Affected Services

Roles

RolePerson
Detector
Incident Leader
Scribe
Communication Manager
Responders

Communication Channels

  • Call: [link]
  • Chat: [channel]

Timeline

HH:MM UTC - Incident detected by [who/what]
HH:MM UTC - [Person] assigned as Incident Leader
HH:MM UTC - [Person] assigned as Scribe
HH:MM UTC - Initial assessment: [description]
HH:MM UTC - ...

Investigation

What We Know

Affected Services

ServiceImpactStatus

Root Cause (initial assessment)

Actions

Immediate

  • [Action] @[Owner]
  • [Action] @[Owner]

Resolution

  • [Action] @[Owner]
  • [Action] @[Owner]

Resolution Summary

Mitigation Applied

Verification

  • [Check 1]
  • [Check 2]

Communications Sent

TimeChannelSummary

Post-Incident

  • Post-mortem scheduled for: [date]
  • Post-mortem document created (save to your post-mortems folder)
  • Action items assigned
  • [Relevant dashboard]
  • [Relevant PR/commit]
  • [Screenshots]

Severity Reference

LevelDescription
P1Critical - funds at risk, active exploit
P2High - major impact, immediate response
P3Moderate - medium impact
P4Low - minor issues
P5Info - no action needed

See Incident Response Policy for full definitions.

Further reading