# Change Control

A governed process for capturing, evaluating, deciding, implementing, and recording proposed changes to approved project baselines or controlled items.

- Type: practice
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/change-control/>)

## What it means

Change control manages requests to alter approved scope, schedule, cost, quality, benefits, requirements, or other baselined elements. A request is logged, analyzed for consequences and alternatives, and approved, rejected, or deferred by the appropriate authority. Approved changes are then incorporated into relevant plans, configurations, contracts, forecasts, and communications with traceable implementation.

## Why it matters

Projects must adapt, but unmanaged adaptation creates conflicting expectations, hidden cost, and unreliable reporting. Change control makes tradeoffs explicit and preserves the integrity of the current baseline. It helps decision makers see cumulative effects, protects teams from informal scope expansion, and creates an audit trail explaining why commitments changed.

## When to use it

Apply change control once a baseline or controlled configuration has been approved. Scale the pathway to materiality: small changes may use delegated authority, while changes affecting business cases, safety, contracts, benefits, funding, or major milestones need broader review. Emergency pathways should still document retrospective authorization and consequences.

## How it works

1. Log the request with its rationale, originator, affected baseline items, urgency, and desired decision date.
2. Screen for completeness and determine the appropriate impact-analysis depth and decision authority.
3. Assess effects on objectives, benefits, scope, schedule, cost, quality, resources, risks, contracts, and stakeholders.
4. Present alternatives and a recommendation; record approval, rejection, deferral, conditions, rationale, and accountable decision maker.
5. Implement approved changes, update all affected baselines and records, communicate them, and verify the intended result.

## A practical example

A regulator adds a reporting requirement during a software implementation. The team logs the request, estimates design and testing work, identifies a two-week launch effect, and presents phased and full-compliance options. The steering group approves phased delivery, updates scope and schedule baselines, funds the work, and records the compliance decision.

## Where it breaks

Heavy governance can slow necessary learning, especially when every minor backlog adjustment is treated as a baseline change. Conversely, fast approval without integrated analysis merely formalizes poor decisions. Change control cannot rescue an obsolete business case, and approved changes may still fail if affected plans, teams, suppliers, or users are not updated.

## Common mistakes

- Implementing a requested change before the authorized decision is recorded.
- Assessing only schedule or cost while ignoring benefits, risk, quality, and operations.
- Approving changes individually without considering their cumulative effect.
- Updating one plan while leaving requirements, contracts, forecasts, or communications inconsistent.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/change-control/#visualization-change-control>)

## Sources

1. [What Is Change Control?](<https://www.apm.org.uk/resources/what-is-project-management/what-is-change-control/>) — Association for Project Management · Professional practice guidance
2. [Programme and Project Issues Management](<https://www.finance-ni.gov.uk/articles/programme-and-project-issues-management>) — Northern Ireland Department of Finance · Government project guidance
3. [Gate 2 Review: Delivery Strategy](<https://www.gov.uk/government/publications/gate-review-2-delivery-strategy/gate-2-review-delivery-strategy>) — UK Infrastructure and Projects Authority · Government assurance guidance

## Related topics

- [Project Charter](<https://wiki.soroush.uk/topic/project-charter/>)
- [Issue Log](<https://wiki.soroush.uk/topic/issue-log/>)
- [Earned Value Management](<https://wiki.soroush.uk/topic/earned-value-management/>)
