Incident Report Template

Post-broadcast incident documentation for continuous improvement.

Incident Information

Field Value
Date
Time
Duration
Severity
Stream/Event
Reported By

Severity Definitions

Level Definition Examples Response Time
Critical Stream is down or completely unusable; viewers cannot watch Complete audio/video loss, platform disconnection, system crash, encoding failure Immediate (drop everything)
Major Significant quality degradation affecting viewer experience Persistent frame drops (>5%), audio sync issues, single camera failure, visible artifacts Within 2 minutes
Minor Noticeable issues that don’t significantly impact viewing Momentary glitches (<10s), minor audio level fluctuation, brief frame stutter, cosmetic issues When convenient (don’t interrupt flow)

Severity Selection Guide:

  • If viewers are complaining or leaving → Critical
  • If the issue is visible/audible but stream continues → Major
  • If you noticed it but viewers likely didn’t → Minor

Incident Summary

Timeline

Time Event

Impact

Viewer Impact

  • Stream went offline
  • Video quality degraded
  • Audio quality degraded
  • Visible errors/artifacts
  • No viewer-facing impact

Estimated affected duration:

Approximate viewer count at time of incident:

Production Impact

  • Had to switch to backup
  • Lost content (not recorded)
  • Required restart of software
  • Required restart of hardware
  • Required manual intervention

Technical Details

System State

Hardware involved:

  • DeckLink/Video capture
  • MOTU/Audio interface
  • Cameras
  • Network equipment
  • Mac Studio
  • Other:

Software involved:

  • OBS Studio
  • Ableton Live
  • Dante Controller
  • Blender
  • Other:

Error Messages

[Paste error messages here]

System Resources at Time of Incident

Metric Value
CPU Usage
Memory Used
Disk Space
OBS Dropped Frames
Encoding Bitrate

Root Cause Analysis

What happened?

Why did it happen?

Could it have been prevented?

Were there warning signs?

Resolution

Immediate Actions Taken

1. 2. 3.

Was the resolution successful?

Follow-Up Actions

Preventive Measures

Action Owner Due Date Status
⏳ Pending
⏳ Pending

Documentation Updates

  • RUNBOOK.md - Add check for
  • TROUBLESHOOTING.md - Add section for
  • health-check.sh - Add validation for
  • Other:

Equipment/Software Changes

  • None required
  • Upgrade/replace:
  • Add redundancy:
  • Change configuration:

Lessons Learned

What went well?

-

What could be improved?

-

Key takeaways

1. 2. 3.

Attachments

  • OBS log file:
  • Screenshot:
  • Stream recording segment:
  • Other:

Sign-Off

Role Name Date
Incident Reporter
Technical Review
Actions Verified

Template version: 1.0.0