# Change Request: [change]

> Change management record (ITIL-shaped) – what changes, the risk,
> the plan, the rollback. Approved before touched.

| Field | Value |
|-------|-------|
| Change ID | CR-NNNN |
| Requester | @name |
| Implementer | @name |
| Type | Standard / Normal / Emergency |
| Priority | Low / Medium / High |
| Window | YYYY-MM-DD HH:MM to HH:MM [TZ] |
| Status | Submitted / Approved / Scheduled / Done / Rolled back |

## Description

What changes and why:

## Systems affected

| System | Impact | Users affected |
|--------|--------|----------------|
| | | |

## Risk assessment

| Question | Answer |
|----------|--------|
| What breaks if it goes wrong? | |
| Blast radius | [scope] |
| Service interruption expected? | Yes / No – duration |
| Similar change failed before? | |

## Implementation plan

1. [step with expected result]
2. [step]
3. Verification: [how to confirm success]

## Rollback plan

- Trigger: [conditions that force rollback]
- Steps: [reverse procedure]
- Decision owner: @name
- Rollback tested? Yes / No / N/A

## Approval

| Role | Approver | Decision | Date |
|------|----------|----------|------|
| Technical | @name | Approve / Reject | YYYY-MM-DD |
| Business / CAB | @name | Approve / Reject | YYYY-MM-DD |

## Post-implementation

- [ ] Verification checks passed
- [ ] Monitoring clean for N hours
- [ ] Stakeholders notified
- [ ] Documentation updated

Outcome: [success / partial / rolled back – what happened]