# Change Management Checklist — Implementation Workbook

Version: 1.0
Published: 2026-07-27
Last updated: 2026-07-27
Owner: Rusaka Research
Review frequency: Every 6 months

## Decision statement

What decision must this workbook support?

________________________________________________________________________________

## Scope and exclusions

In scope:

________________________________________________________________________________

Out of scope:

________________________________________________________________________________

## Baseline evidence register

| Evidence item | Source | Date | Owner | Verified by | Status |
|---|---|---|---|---|---|
| | | | | | |
| | | | | | |
| | | | | | |

## Assumption register

| Assumption | Rationale | Decision affected | Downside case | Test | Owner | Review date |
|---|---|---|---|---|---|---|
| | | | | | | |
| | | | | | | |

## Options and decision criteria

| Option | Outcome | Feasibility | Cost | Time | Risk | Reversibility | Recommendation |
|---|---:|---:|---:|---:|---:|---:|---|
| | | | | | | | |
| | | | | | | | |

## Implementation plan

| Phase | Entry evidence | Actions | Owner | Control | Exit evidence | Due date |
|---|---|---|---|---|---|---|
| 1. Operations — Change Management Checklist | | During operations, use Change Management Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | |
| 2. Discovery — Change Management Checklist | | During discovery, use Change Management Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | |
| 3. Design — Change Management Checklist | | During design, use Change Management Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | |
| 4. Pilot — Change Management Checklist | | During pilot, use Change Management Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | |
| 5. Scale — Change Management Checklist | | During scale, use Change Management Checklist to verify that required evidence and approvals exist before proceeding. Start with system diagrams, service levels, traffic and data profiles, defects, incidents, delivery throughput, dependencies, and operating cost. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it. | | | Required output: a dated checklist with evidence links, exceptions, and owners. | |

## Measures and thresholds

| Measure | Definition | Source | Baseline | Target | Threshold | Owner | Frequency |
|---|---|---|---:|---:|---:|---|---|
| | | | | | | | |
| | | | | | | | |

## Risk and control register

| Risk | Cause | Impact | Preventive control | Detective control | Owner | Residual risk |
|---|---|---|---|---|---|---|
| | | | | | | |
| | | | | | | |

## Review checklist

- [ ] 1. Operating model: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 2. Architecture and integration: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 3. Risk and compliance: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 4. Economics and value: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 5. Delivery sequencing: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 6. Vendor and partner assessment: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 7. Measurement system: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 8. Quality assurance: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 9. Change management: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 10. Documentation: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 11. Scenario analysis: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 12. Security and resilience: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 13. Data governance: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.
- [ ] 14. Capability and resourcing: evidence is linked, ownership is named, exceptions are recorded, and the current decision is clear.

## Approval record

| Role | Name | Decision | Conditions | Date |
|---|---|---|---|---|
| Accountable owner | | | | |
| Subject-matter reviewer | | | | |
| Risk or control reviewer | | | | |

## Authoritative references

- https://www.gov.uk/guidance/government-design-principles — Authoritative reference 1 for the evidence and standards relevant to Digital Transformation and Enterprise Architecture. Confirm the current version and applicability before relying on it.
- https://www.nist.gov/ — Authoritative reference 2 for the evidence and standards relevant to Digital Transformation and Enterprise Architecture. Confirm the current version and applicability before relying on it.
- https://www.iso.org/standard/75546.html — Authoritative reference 3 for the evidence and standards relevant to Digital Transformation and Enterprise Architecture. Confirm the current version and applicability before relying on it.

## Related Rusaka resources

- https://www.rusaka.com/resources/checklists
- https://www.rusaka.com/resources/guides/transformation-governance-guide
- https://www.rusaka.com/resources/frameworks/digital-maturity-model
- https://www.rusaka.com/resources/checklists/release-readiness-checklist
- https://www.rusaka.com/resources/checklists/salesforce-implementation-checklist
- https://www.rusaka.com/resources/calculators/transformation-value-calculator
- https://www.rusaka.com/resources/templates/capability-map-template
- https://www.rusaka.com/resources/guides/digital-transformation-guide

## Important limitation

This educational workbook does not replace legal, investment, tax, accounting,
security, clinical, regulatory, or other qualified professional advice. Confirm
current requirements and obtain formal organisational approval where applicable.