Start by providing a high-level summary of the change. This should explain to team members why the change was implemented and how it impacts the system. Once you’ve described the request, customize the template by adding tickets related to the request and @ mentioning reviewers and stakeholders.

Now that you’ve added background information, explain your change management approach in detail. Start by listing all the change plans and type // to add the scheduled implementation date for each plan. Then describe the individual steps your team needs to take to implement each change plan. Make sure to include details about how each plan could affect the system’s performance or user services.

Once you’ve followed through with your change plans, use the template to evaluate how successfully the change request was implemented. Begin by adding background information like the post-implementation review’s date and participants. Then describe the criteria participants need to evaluate during the review. As you review the change request, use the template to record lessons learned and keep track of follow-up items.