Purpose. Capture a proposed change and its impact before any work begins.
Verbal and chat requests are transcribed here.
Request
| Field | Detail |
|---|
| Change request ID | CR- |
| Date raised | |
| Raised by | |
| Affected project | |
| Contact | |
Nature of the change
Description
What is being requested? Be specific about what changes and what does not.
Rationale
What is the business or technical driver? What happens if the change is not made?
Preliminary impact
| Dimension | Impact | Effort |
|---|
| Scope | | |
| Schedule | | |
| Budget | | |
| Resources | | |
| Architecture | | |
| Security / compliance | | |
| Risk | | |
Options
| Option | Description | Cost | Benefit | Risk |
|---|
| A | | | | |
| B | | | | |
| Do nothing | | | | |
Recommendation
Preferred option, and why.
Supporting documentation
Impact assessment (completed by the delivery team)
| Field | Detail |
|---|
| Assessed by | |
| Date | |
| Feasibility study required? | Yes / No — reason |
| Technical impact | |
| Schedule impact | |
| Cost impact | |
| Resource impact | |
| Security impact | |
| Risk to delivery | |
| Mitigation | |
Decision (completed by the CAB)
| Field | Detail |
|---|
| Decision | Approved / Rejected / Deferred / Approved with conditions |
| Conditions | |
| Rationale | |
| Decided by | |
| Date | |
| Register updated | Yes / No |
Implementation plan
Rollback plan:
Communication:
Verification:
Post-change review
| Field | Detail |
|---|
| Was the outcome achieved? | |
| Actual effort vs estimate | |
| Unidentified impacts | |
| Lessons for the process | |
| Closed by / date | |