CR-YYYY-MM-DD: [Change Description]
1. Change Summary
| Field | Value |
|---|---|
CR ID |
CR-YYYY-MM-DD-NNN |
Date |
YYYY-MM-DD |
Priority |
[P1: Critical / P2: High / P3: Standard] |
Type |
[Configuration / Infrastructure / Documentation / Security] |
Status |
[Proposed / Approved / Implemented / Rolled Back] |
Requestor |
[Name / Team] |
Implementor |
Evan Rosado |
Current State vs Target State
| Component | Current (Before) | Target (After) |
|---|---|---|
[Component 1] |
[Current config/state] |
[Desired config/state] |
[Component 2] |
[Current config/state] |
[Desired config/state] |
3. Scope
3.1. In Scope
-
[Change item 1]
-
[Change item 2]
3.2. Out of Scope
-
[Explicitly excluded item 1]
4. Implementation Plan
4.1. Pre-Change Verification
# Commands to verify current state before making changes
4.2. Step 1: [Action]
# Implementation commands
4.3. Step 2: [Action]
# Implementation commands
4.4. Post-Change Verification
# Commands to verify the change worked correctly
5. Rollback Plan
|
Execute if post-change verification fails. |
# Rollback commands
6. Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
[Service disruption] |
[Low/Med/High] |
[Low/Med/High] |
[Strategy] |
7. Communication
| Audience | Timing | Method |
|---|---|---|
[Team / Users] |
[Before / During / After] |
[Email / Slack / Meeting] |
8. Post-Implementation Review
Change successful: [ ] Yes / [ ] No / [ ] Partial
Unexpected outcomes: [None / Describe]
Lessons learned: [What to do differently next time]