Introduction
Change Enablement makes sure that changes to systems, services and configurations are planned, reviewed and approved before they are made, so that fixes do not cause new problems. A change is typically raised from a ticket or a problem when the fix requires altering something in the live environment.
A change record usually captures what will be changed and why, the risk and impact, the plan for carrying it out, the rollback plan if something goes wrong, the approval decision, and the outcome after implementation.
Raise a change from a ticket when a single ticket needs a change (section 2.2.16).
Raise a change from a problem when the root-cause fix needs a change (section 2.4).
Do not make the change until it is approved and scheduled.
Update the linked ticket or problem when the change is complete.
[To complete: navigation path, change list and form fields, approval steps and screenshots for Change Enablement]