Change Control: Assess and Approve Before You Implement
Good change follows a path, not a hasty decision.
- Request — Document the change request
- Assess impact — Its impact on scope, time, cost, and risk
- Board decision — Approve, reject, or defer
- Update baseline — Update baselines and inform stakeholders
No change is applied just because it is requested; it follows a disciplined path: the change request is documented, its impact on scope, time, cost, and risk is assessed, then it is approved or rejected, in large projects through the Change Control Board, and on approval the baselines and documents are updated and stakeholders are informed. The goal is to protect the project from uncontrolled change and scope creep.
Implementing a change directly because it is small or the customer asked. Instead, assess and approve it first, however minor.
Assess, then approve, then update the baseline, in that order.
Ready to start serious PMP prep?
Subscribe now →Read the details
Integrated change control is the process that ensures any proposed change is evaluated before it is applied. The path begins by documenting the change request, then assessing its integrated impact on scope, schedule, cost, quality, and risk, then deciding to approve, reject, or defer it, in large projects through the Change Control Board. On approval, the affected baselines and documents are updated and stakeholders are informed, keeping the project coherent and protected from uncontrolled change and unmanaged scope creep.
Frequently asked questions
Do I implement a change just because it is requested?
No; it follows a path: document the request, assess its impact, approve or reject it, then update the baselines.
What is the role of the Change Control Board?
In large projects, it assesses change requests and decides to approve or reject them.
What happens after a change is approved?
The affected baselines and documents are updated, and stakeholders are informed.
Why assess even a small change?
Because small accumulated changes cause scope creep and disrupt schedule and cost.
What is the goal of change control?
To protect the project from uncontrolled change and unmanaged scope creep.