RCA-YYYY-MM-DD-NNN: Change Description

1. Executive Summary

2. Timeline

Time Event

YYYY-MM-DD HH:MM

Symptom first noticed

+Xm

Investigation began

+Xm

Root cause identified

+Xm

Fix applied

+Xm

Resolution verified

3. Problem Statement

3.1. Symptoms

  • Symptom 1

  • Symptom 2

  • Symptom 3

3.2. Expected Behavior

3.3. Actual Behavior

4. Root Cause

4.1. 5 Whys Analysis

Why # Question and Answer

1

Why did the symptom occur?
Because: Immediate cause

2

Why did the immediate cause occur?
Because: Deeper cause

3

Why did the deeper cause occur?
Because: Systemic cause

4

Why did the systemic cause occur?
Because: Process or knowledge gap

5

Why did the gap exist?
Because: Root cause

4.2. Root Cause Statement

5. Contributing Factors

Factor Description Preventable?

Factor 1

How it contributed to the incident

Yes

Factor 2

How it contributed to the incident

No

6. Impact

6.1. Severity

Metric Value

Severity

P3

Duration

X minutes/hours

Users/Systems Affected

1 user, 1 system

Data Loss

None

6.2. Business Impact

  • Productivity impact

  • Downstream effects

7. Resolution

7.1. Immediate Actions

  1. Step 1

    # Command executed for resolution

  2. Step 2

7.2. Verification

# Commands used to verify the fix

8. Preventive Measures

8.1. Short-term (This Week)

Action Owner Status

Action item 1

Evan

[ ] Pending

Action item 2

Evan

[ ] Pending

8.2. Long-term (This Quarter)

Action Owner Status

Systemic improvement 1

Evan

[ ] Pending

Process change 1

Evan

[ ] Pending

9. Detection

9.1. How was it detected?

  • Manual observation

9.2. Detection Gap

10. Lessons Learned

10.1. What went well

  • Item 1

  • Item 2

10.2. What could be improved

  • Item 1

  • Item 2

10.3. Key Takeaways

  1. Takeaway 1

  2. Takeaway 2

  3. Takeaway 3

11. Related

12. Metadata

Field Value

RCA ID

RCA-YYYY-MM-DD-NNN

Author

Evan Rosado

Date Created

YYYY-MM-DD

Last Updated

YYYY-MM-DD

Status

Draft

Review Date

YYYY-MM-DD