You may use outside sources to complete these documents. If you source something elsewhere, follow the integrity of the language, but make the document your own. Do not copy/paste from other established documentation.

VERSION HISTORY Provide information on how the development and distribution of the Change Management Plan, up to the final point of approval, was controlled and tracked. Use the table below to provide the version number, the author implementing the version, the date of the version, the name of the person approving the version, the date that particular version was approved, and a brief description of the reason for creating the revised version.] Version Implemented Revision Approved Approval Reason # By Date By Date 1.0 Note to the Author [This document is a template of a Change Management Plan. The template includes instructions CHANGE MANAGEMENT PLAN to the author, boilerplate text, and fields that should be replaced with the values specific to the organization Version Red italicized text enclosed in square brackets ([text]) provides instructions to the document author, or describes the intent, assumptions and context for content included in this document. . Red italicized text enclosed in angle brackets () indicates a field that should be replaced with information specific to the organization. Text and tables in black are provided as boilerplate examples of wording and formats that may be used or modified as appropriate to your organization. These are offered only as suggestions to assist in developing your organizational plan. When using this template for your project document, it is recommended that you follow these steps: 1. Replace all text enclosed in angle brackets (i.e., ) with the correct field values. These angle brackets appear in both the body of the document and in headers and footers. To customize fields in Microsoft Word (which display a gray background when selected): 1. Modify boilerplate text as appropriate to your organization. 2. To add any new sections to the document, ensure that the appropriate header and body text styles are maintained. Styles used for the Section Headings are Heading 1, Heading 2 and Heading 3. Style used for boilerplate text is Body Text. 3. To update the Table of Contents, right-click and select "Update field" and choose the option- "Update entire table" 4. Before submission of the first draft of this document, delete this "Notes to the Author" page and all instructions to the author, which appear throughout the document as red italicized text enclosed in square brackets.] Page 2 of 10TABLE OF CONTENTS 1 INTRODUCTION 1 INTRODUCTION.. 1.1 PURPOSE OF THE CHANGE MANAGEMENT PLAN 1.1 Purpose of The Change Management Plan ... Provide the purpose of the Change Management Plan. This document should be tailored to fit the particular organizational needs.] 2 CHANGE MANAGEMENT PROCESS. 2.1 Change Request Process Flow Requirements... The Change Management Plan documents and tracks the necessary information required to effectively manage change from the inception to delivery. 2.2 Change Request Form and Change Management Log.. 2.3 Evaluating and Authorizing Change Requests. The Change Management Plan is created during the Planning Phase of the project. Its intended audience is the project manager, project team, project sponsor and any senior 2.3.1 Change Control Board .. leaders whose support is needed to carry out the plan. 3 RESPONSIBILITIES. 2 CHANGE MANAGEMENT PROCESS APPENDIX A: CHANGE MANAGEMENT PLAN APPROVAL.. The Change Management process establishes an orderly and effective procedure for tracking APPENDIX B: REFERENCES... ....8 the submission, coordination, review, evaluation, categorization, and approval for release of APPENDIX C: KEY TERMS.. all changes to the project's baselines. APPENDIX D: CHANGE REQUEST FORM EXAMPLE.. .....10 2.1 CHANGE REQUEST PROCESS FLOW REQUIREMENTS [Outline the project teams agreed upon change request (CR) process flow. The following outlines a generic change request process flow.} Step Description Generate CR A submitter completes a CR. Form and sends the completed form to the Change Manager Log CR. Status The Change Manager enters the CR into the CR Log. The CR's status is updated throughout the CR. process as needed Evaluate CR. Project personnel review the CR. and provide an estimated level of effort to process, and develop a proposed solution for the suggested change Authorize Approval to move forward with incorporating the suggested change into the project product Implement If approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders Generate CR Evaluate CR Authorize CR Implement CR Log Updated Status Report Status Page 3 of 10 Page 4 of 10 2.2 CHANGE REQUEST FORM AND CHANGE MANAGEMENT LOG Testing CR work has been reviewed and is being tested List and define the data elements the project team needs to include on the Change Request Closed CR work is complete, has passed all tests, and updates have been released Medium I Change Insert the name, version number, description, and physical location of any documents Management Plan and agree with the approach it presents. Changes to this Change referenced in this document. Add rows to the table as necessary.} Management Plan will be coordinated with and approved by the undersigned or their The following table summarizes the documents referenced in this document. designated representatives. List the individuals whose signatures are desired. Examples of such individuals are Document Name Description Location and Version Business Steward, Project Manager or Project Sponsor. Add additional lines for signature as necessary. Although signatures are desired, they are not always required to move forward Document Provide description of the with the practices outlined within this document.] Version Number> Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title Role : Signature Date: Print Name: Title Role: Page 7 of 10 Page 8 of 10 Appendix C: Key Terms Appendix D: Change Request Form Example Insert terms and definitions used in this document. Add rows to the table as necessary. The attached example Change Request Form can be used to submit changes during the life Follow the link below to for definitions of project management terms and acronyms used in of the project. this and other documents. The following table provides definitions for terms relevant to this document. Term Definition [Insert Term] [Provide definition of the term used in this document.] [Insert Term [Provide definition of the term used in this document.) [Insert Term] [Provide definition of the term used in this document.] Page 9 of 10 Page 10 of 10Change Request Form Version: 1.0 Change Request Form (example) SUBMITTER - GENERAL INFORMATION CR# Submitter Name Brief Descr Request Date Submitted Date Required Priority Low Medium High Mandatory Reason for Change Other Artifacts Impacted Assumptions and Notes Attachments or Yes NO References Link: INITIAL ANALYSIS Hour Impact Duration Impact Schedule Impact Comments Recommendations CHANGE CONTROL BOARD - DECISION Decision Approved Approved Rejected | More Info w/Conditions Decision Date Decision Explanation Conditions Revision Date: 8/11/2024 Page 1 Change Request Form