stakeholdermap.

com
Project Management, project planning, templates and advice

<PROJECT NAME>
<PROJECT REFERENCE>

CHANGE MANAGEMENT PLAN

stakeholdermap.com
 CHANGE MANAGEMENT PLAN

DOCUMENT CONTROL

DOCUMENT INFORMATION

Information

Document Id [Document Management System #]

Document Owner [Owner Name]

Issue Date [Date]

Last Saved Date [Date]

File Name [Name]

DOCUMENT HISTORY

Version Issue Date Changes

[1.0] [Date] [Section, Page(s) and Text Revised]

DOCUMENT APPROV ALS

Role Name © Signature Date

Project Sponsor

Project Review Group

Project Manager ©

stakeholdermap.com i
 CHANGE MANAGEMENT PLAN

Quality Manager

(if applicable)

Procurement Manager

(if applicable)

Communications Manager

(if applicable)

Project Office Manager

(if applicable)

stakeholdermap.com ii
 CHANGE MANAGEMENT PLAN

Table of Contents
<PROJECT NAME> ......................................................................................................................................................... I

<PROJECT REFERENCE>................................................................................................................................................ I

CHANGE MANAGEMENT PLAN ................................................................................................................... I

DOCUMENT CONTROL................................................................................................................................. I
DOCUMENT INFORMATION ............................................................................................................................................... I

DOCUMENT HISTORY ...................................................................................................................................................... I

DOCUMENT APPROVALS ................................................................................................................................................. I

TEMPLATE GUIDE ...................................................................................................................................... 1

CHANGE MANAGEMENT APPROACH: ........................................................................................................... 2

DEFINITIONS OF CHANGE: ........................................................................................................................... 2

CHANGE CONTROL BOARD: ........................................................................................................................ 3

CHANGE CONTROL PROCESS:..................................................................................................................... 3

CHANGE CONTROL MEETINGS ..................................................................................................................... 4

stakeholdermap.com iii
 CHANGE MANAGEMENT PLAN

TEMPLATE GUIDE

How to use this template

This is a guide to the common sections included in a Change Management Plan. Sections
may be added, removed or amended to suit your project. Example tables have been added
(where relevant) these are just a suggestion, you may decide to format these sections
differently.

Text in Blue italics is designed to assist you in completing the template. Delete this text
before sharing the final document.

stakeholdermap.com 1
 CHANGE MANAGEMENT PLAN

CHANGE MANAGEMENT APPROACH:

Describe change control policies and procedures and how change control will interface with
other aspects of project management.

DEFINITIONS OF CHANGE:

In this section explain what a change is as opposed to an expected variance. It is likely that
you will refer to the project’s cost, schedule and scope tolerances aka variance thresholds in
this section. For example, cost variances of <1% might not require change control. Refer to
the project management plan for the variance thresholds.

Find out more about Project Tolerances.

Change type Change definition

Schedule Confirm what would constitute a schedule change and trigger a change
change: request versus a schedule revision. For an example see Schedule
Variance Threshold.

Budget Define a budget change versus an update. Show when a budget

change: variance would exceed the project tolerance and trigger the change
control process.

Scope change: Define a scope change as opposed progressive elaboration. Describe

when a scope variance would exceed project tolerance and trigger the
change control process.

Project Explain when changes to the project management documentation will

document need to go through change control for re-baselining. For example,
changes: changes to the project management plan or KPIs in the Business Case.

stakeholdermap.com 2
 CHANGE MANAGEMENT PLAN

CHANGE CONTROL BOARD:

List the members of the change control board along with their role, responsibilities and sign-
off authority. You might also identify any person they delegate their authority to if they are
not available.

Name Role Responsibility Authority

Board Their role in the The responsibilities The persons sign-off authority
member’s name board and tasks required i.e. what changes they can
of the role. approve.

CHANGE CONTROL PROCESS:

Detail each step in the change control process. Include the people involved and any systems
e.g. IT systems used.

Process step Description

Change request submittal Describe how change requests are submitted, including
which form or system is used and any unique ID or
referencing that is used. Include who will receive the change
requests and if any change type will be routed to differently
e.g. cost changes might go to project accounting.

Change request tracking Describe how change requests will be tracked from

stakeholdermap.com 3
 CHANGE MANAGEMENT PLAN

submission to closure. Include details of any IT systems

used and any network or file locations.

Change request review Describe how changes will be reviewed. Including how each
change will be analyzed in relation to the project business
case, project management plan, schedules, risk register etc.

Change request disposition Document the possible statuses that a change can have
once it has been reviewed for example, accepted, deferred
or rejected.

CHANGE CONTROL MEETI NGS

Change Control Meetings are for evaluating changes, creating options, and preparing
change requests for submittal to whoever has authority to approve those changes (PM,
Change Control Board, or sponsor).

Document the meetings that will be held to manage changes. For example, this may include
meetings to prepare changes for submittal to the board along with the board meetings.
Include the meeting:

• Frequency

• Attendees

• Timings and location

• Details of the Scribe, what information will be captured, and how actions will be
monitored.

• Details of the Chair and their responsibility.

MORE FREE PROJECT MANAGEMENT TEMPLATES

Microsoft Project Plans [tried and tested]

Project Management Templates [FREE]

Stakeholder Management Templates

stakeholdermap.com 4