When you need it
Prepare this plan before changes begin affecting approved project baselines, or when inconsistent requests and approvals show that scope, cost, schedule, and technical decisions need a clearer shared control process.
DOCX /
AI tools and documents for engineering and project management.
Change Management Plan
Set the project process for requesting, assessing, deciding and implementing changes.
How to use this templateThis Word template contains prepared headings, tables, project fields and completion notes. Add your information, review the completed document and remove the notes before issue.
The form prepares a separate brief; it does not fill the Word or Excel file.
Read product descriptions in your language. The Word and Excel template files are in English.
Only selected pages are shown. This is not the complete template. The full editable Word or Excel file is supplied with purchase.
Learning
How to use this template
What it helps you decide
It establishes how changes are raised, assessed, decided, implemented, and verified, allowing legitimate adjustments to proceed while preserving traceability between the decision, affected baselines, and the work actually delivered.
How to complete it
- Identify Scope and controlled baselines, then assign Change roles and authority using the project's actual governance and contractual boundaries for different decisions.
- Describe Assessment and decision process, requiring proportionate impact evidence and identifying how Urgent changes and exceptions receive controlled treatment under project arrangements.
- Set Implementation and verification arrangements that update affected records, then define Communication and review so approved decisions reach the teams executing them.
Who prepares and reviews it
The project manager typically leads preparation with controls, commercial, engineering, and delivery representatives. Sponsor or governance authorities approve decision rights, while process owners confirm how the plan interfaces with contractual change mechanisms.
A mistake to avoid
Allowing approval of a technical sketch to stand in for all budget and programme decisions leaves the changed baseline and implementation authority ambiguous.
Illustrative example
Illustrative example: a logistics project receives frequent tenant layout revisions. The plan establishes who assesses structural, services, cost, and schedule consequences before a decision. An approved loading-area change then updates the relevant drawings and baseline records, while an unapproved office preference remains visibly pending.
Document contents
- Scope and controlled baselines
- Change roles and authority
- Assessment and decision process
- Urgent changes and exceptions
- Implementation and verification
- Communication and review
Required inputs
- Project name, location, company, document number and revision
- Actual project scope, source records and responsible roles
Practical tools.
Professional judgment.
Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.
Prepare project brief