Change Control
A governed process for capturing, evaluating, deciding, implementing, and recording proposed changes to approved project baselines or controlled items.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/change-control/
01What 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.[1][2][3]
- 01Log requestRationale, origin, affected baseline, urgency
- 02Assess impactValue, scope, schedule, cost, quality, risk, people
- 03Compare optionsApprove, reject, defer, or use an alternative
- 04Record decisionAuthority, conditions, rationale, and owner
- 05Update + verifyPlans, contracts, forecasts, communication, result
Change control should match the consequence of the baseline change; treating every backlog adjustment as a formal change can suppress useful learning.
02Why 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.
03When 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.
04How it works
- Log the request with its rationale, originator, affected baseline items, urgency, and desired decision date.
- Screen for completeness and determine the appropriate impact-analysis depth and decision authority.
- Assess effects on objectives, benefits, scope, schedule, cost, quality, resources, risks, contracts, and stakeholders.
- Present alternatives and a recommendation; record approval, rejection, deferral, conditions, rationale, and accountable decision maker.
- Implement approved changes, update all affected baselines and records, communicate them, and verify the intended result.
05A 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.
06Where 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.
07Sources
- What Is Change Control?Association for Project Management · Professional practice guidanceWhat Is Change Control?
- Programme and Project Issues ManagementNorthern Ireland Department of Finance · Government project guidanceProgramme and Project Issues Management
- Gate 2 Review: Delivery StrategyUK Infrastructure and Projects Authority · Government assurance guidanceGate 2 Review: Delivery Strategy