Scope changes are not the problem. Unmanaged scope changes are. A project that can evaluate a change request, communicate its impact, and get proper approval before proceeding can absorb changes without losing control. A project that accepts changes informally cannot.
Why Change Management Matters
Every project change has a cost. Sometimes the cost is time. Sometimes it is budget. Sometimes it is both. When changes are accepted verbally, without impact assessment, the cost is invisible until the end of the project when someone asks why delivery is late and over budget.
The purpose of change management is not to prevent changes. It is to make the cost of every change visible before it is accepted. A stakeholder who understands that adding this feature moves delivery by two weeks can make an informed decision. One who does not cannot.
How to Handle a Change Request
Write It Down Immediately
Every change request goes in writing the moment it is made - in a meeting, on a call, in a conversation. If the requester did not put it in writing, you write it for them and confirm that your description is accurate. Verbal change requests that are not documented become disputes about what was agreed.
Assess the Impact Before Responding
How many additional hours or days does this change require? What does it cost in additional budget? Which other tasks does it delay? Which deliverables does it affect? Complete this assessment before accepting or declining the change. An impact you have not calculated is an impact you cannot communicate.
Get Approval From the Right Person
The person who approved the original scope must approve any change to it. Not the person requesting the change. Not the project manager. The original approver - the project sponsor or the client. Changes approved by anyone else are not really approved.
Update All Affected Documents
The project plan, the scope document, the budget, and the timeline all get updated to reflect the approved change. Not as a note in the change log. As actual updates to the working documents. Future readers of those documents need to see the current agreed scope, not the original one with a list of amendments attached.
Communicate the Change to the Full Team
Tell everyone on the project team what changed, why it changed, and what it means for their work. Surprises during project execution - finding out two weeks in that the scope changed without being told - erode team trust faster than almost any other project management failure.
What to Do When Requests Come Informally
When a stakeholder makes a change request in a casual conversation, the right response is: let me write that up and we can evaluate it properly. That is not bureaucracy. It is the process that protects both the project and the stakeholder from a change that seemed small and turned out not to be.
For more on this topic, read How to Say No to a Stakeholder. You may also find How to Write a Project Plan From Scratch useful as a next step.
Available Now
The Accidental Project Manager
For the person who was handed a project and told to figure it out. The 15-minute daily system, scope lock framework, and AI prompts that get any project back on track. No certification required.
Get the Book on Gumroad