Integrated Change Control: A Practical How-To Guide
Every project encounters changes. Requirements evolve, technical constraints emerge, stakeholder priorities shift. The question is not whether changes will occur, but whether they will be managed well. Integrated change control (ICC) is the process by which all proposed changes are reviewed, assessed, approved or rejected, and documented — and it is one of the most important disciplines in project management.
What Is Integrated Change Control?
Integrated change control is the process of reviewing all change requests and managing changes to deliverables, organisational process assets, project documents, and the project management plan. It operates across the entire project life cycle, from the moment baselines are established until the project is closed.
The PMI Guide to the Project Management Body of Knowledge (PMBOK Guide) identifies ICC as a core process in the Monitoring and Controlling process group. The process has three key outputs: approved change requests (which are then implemented), rejected change requests (which are documented and closed), and updates to the project management plan and project documents.
Why "Integrated"?
The "integrated" in integrated change control is the critical word. A change to scope does not exist in isolation — it almost always has implications for the schedule, the budget, the quality plan, the risk register, and the resource plan. A project manager who approves a scope addition without assessing its schedule and cost implications is not controlling the project; they are allowing it to drift.
ICC forces a holistic assessment of every change. Before any change is approved, the team must understand its full impact across all project constraints. This is why the process is "integrated" — it integrates the assessment of scope, time, cost, quality, risk, and stakeholder impacts into a single decision.
The Change Control Process: Step by Step
Submit — Anyone on the project (team member, stakeholder, sponsor) can submit a change request. Requests should be formal and documented, not verbal.
Log — Every change request is logged in the change log with a unique identifier, the date received, the requester, and a brief description.
Assess — The project team analyses the impact of the proposed change on scope, schedule, cost, quality, and risk. For significant changes, this analysis may require specialist input.
Review — The Change Control Board (CCB) reviews the change request and the impact assessment.
Decision — The CCB approves, rejects, or defers the change request. In some organisations, the project manager has authority to approve minor changes without escalating to the CCB.
Communicate — The decision is communicated to all affected parties.
Implement — Approved changes are implemented, baselines are updated, and the project management plan is revised to reflect the approved change.
Close — The change request is marked as closed in the change log, with the decision and outcome recorded.
The Change Control Board
The Change Control Board is the governance body responsible for reviewing and approving or rejecting change requests. The composition of the CCB varies by organisation and project size. On large programmes, the CCB might include the project sponsor, key stakeholders, the project manager, and technical leads. On smaller projects, the CCB might simply be the project manager and sponsor.
The CCB should meet on a regular cadence — weekly or bi-weekly on active projects — so that change requests do not sit unresolved for extended periods. Delays in the change control process are themselves a source of project risk: a team that does not know whether a change has been approved may either stop work (causing delay) or proceed on the assumption of approval (causing rework if the change is rejected).
Preventing Informal Scope Changes
One of the most common failure modes on projects is informal scope change — sometimes called "scope creep." This occurs when changes are agreed verbally between a team member and a stakeholder, without going through the formal change control process. The result is that scope expands without any corresponding adjustment to the schedule or budget, and the project manager has no record of what was agreed or why.
ICC prevents scope creep by establishing a clear rule: no change is approved unless it goes through the formal process. Project managers should reinforce this consistently with both team members and stakeholders. The standard response to any informal request should be: "That sounds like a reasonable change — please submit a change request so we can assess the full impact."
ICC and Configuration Management
ICC is closely related to configuration management, which is the process of identifying and documenting the characteristics of project products and ensuring that changes to those characteristics are properly controlled. Where ICC governs the decision to change, configuration management governs what exactly is being changed and ensures that the approved version of each deliverable is clearly identified and controlled. Together, ICC and configuration management ensure that the project team always knows what it is building and that any change to the plan is deliberate and documented.
XNM Consulting delivers project management advisory and hands-on delivery support to organisations managing complex programmes. To learn how we can help, visit our Program and Project Delivery page.