Scope creep is the most common cause of project budget overruns and schedule delays. It is not caused by stakeholders asking for changes — it is caused by changes being absorbed informally without proper evaluation or authorization. A working change control process is the structural fix.
- Scope creep is a governance failure, not a stakeholder behavior problem
- Every change request needs three things assessed: cost, schedule impact, and risk
- Change control is not bureaucracy — it is the mechanism that protects scope and baseline integrity
- A change log visible to the sponsor prevents the "I thought that was included" conversation
What change control is and is not
Change control is not about refusing changes — it is about evaluating and authorizing them with full visibility into their cost, schedule, and risk implications. A well-run change control process approves good changes quickly and rejects or defers bad ones with documented rationale.
The change request form
Every change request needs: description of the change, reason for the change, estimated cost impact, estimated schedule impact, risks introduced, recommendation (approve/defer/reject), and authorization signature. One page. Required for all scope additions above a defined threshold.
The approval workflow
Small changes (below a defined dollar threshold) can be PM-authorized. Medium changes require sponsor approval. Large changes require steering committee approval. Define the thresholds in the charter before the project starts — not when the first change request arrives.
The change log
Maintain a running log of all change requests, their status, and authorization. Share it with the sponsor in every status report. The change log is the most effective tool for preventing the revisionist history ("we always assumed that was in scope") that undermines change control in the late stages of a project.
Frequently asked questions
From project kickoff — not when the first scope addition is requested. Establishing the process before it is needed prevents the awkward conversation of imposing bureaucracy mid-project.
A clarification resolves ambiguity in already-approved scope. A scope change adds, removes, or substantially modifies scope. The distinction matters because only scope changes require change control. Document it explicitly.
Frame it as protection for the sponsor, not restriction on the team. A change log that documents every approved addition is the evidence that protects the project budget when the final cost is higher than the original estimate.
Request How to Build a Change Control Process
Answer a few quick questions. We will recommend the right engagement and follow up within one business day.
Ready to put this into practice?
PMOstart provides consulting, fractional PMO leadership, templates, and tools to help you apply what you just read.