Free Change Management Plan Template
Word Download
Stop scope creep before it starts. Define exactly how changes get raised, assessed, approved and implemented on your project — with a 6-step process, CCB setup, approval thresholds by cost and schedule impact, and a change register framework all in one ready-to-use Word document.
No email required. Instant Word download.
What's in the Template — 6 Sections
The Change Management Plan template covers everything needed to establish a functioning change control process on a project of any size. Each section includes guidance text explaining the intent and what a complete entry looks like.
The Change Control Process — Step by Step
The template defines a six-step change control process. These steps are embedded in Section 2 of the template with owner, trigger and output for each — ready to customise to your project's specific roles.
Setting Up Your Change Control Board
The CCB is the decision-making body for change requests that exceed the PM's authority level. The template includes fields for five standard CCB roles — adapt these to match your project's organisational structure.
Change Approval Thresholds — How to Set Them
The threshold table in Section 4 of the template defines who can approve what. The template ships with suggested thresholds — replace the bracketed values with the actual limits agreed with your sponsor and finance team before the project starts.
| Authority Level | Schedule Impact | Cost Impact | Approval Route |
|---|---|---|---|
| Project Manager | Up to 3 days | Up to $5,000 | PM decision only. Log in register. Notify sponsor. |
| Change Control Board | 4–14 days | $5,001–$25,000 | Majority CCB vote at scheduled or emergency meeting. |
| Project Sponsor | 15–30 days | $25,001–$100,000 | Sponsor sign-off required. CCB recommendation provided. |
| Executive / Board | > 30 days | > $100,000 | Board or investment committee approval. Formal re-baseline. |
Setting Realistic Thresholds
Thresholds that are too tight slow the project down with unnecessary bureaucracy. Thresholds that are too loose let significant changes slip through without proper scrutiny. A good rule of thumb: the PM's authority should cover genuine day-to-day scheduling adjustments without requiring a CCB meeting. The CCB should handle meaningful scope or cost changes that affect the business case. The sponsor should be involved only for changes that materially affect the project's strategic value or cost envelope.
Using This Plan to Prevent Scope Creep
Scope creep — the gradual, uncontrolled expansion of project scope without corresponding adjustments to time, cost or resources — is one of the most common causes of project failure. A change management plan does not prevent change; it prevents unmanaged change.
The Three Most Common Sources of Scope Creep
1. Informal verbal agreements. A stakeholder asks the developer "can you just add this small feature?" and the developer agrees without raising a CR. The "small feature" takes three days. Multiply by ten similar conversations and the project is two weeks over schedule with no paper trail. The fix: make the change process visible, simple and consistently enforced from day one.
2. Gold plating. Team members add functionality or quality beyond what was agreed because they think it will be appreciated. Even when well-intentioned, this consumes time and budget allocated to agreed deliverables. The fix: ensure the team understands that delivering agreed scope on time and budget is the measure of success — not exceeding it.
3. Scope ambiguity in the original requirements. When requirements are vague, everyone interprets them differently. The customer's interpretation is always bigger. The fix: invest in precise scope definition upfront and use the change management plan as the mechanism for handling the inevitable gaps when they surface.