What it means
Project change control evaluates, authorizes, communicates, implements, verifies, and records proposed changes to scope, schedule, cost, quality, security, or operational configuration.
Why it matters
Uncontrolled changes can invalidate requirements, tests, budgets, and risk decisions; formal control preserves the connection between what was approved and what is delivered.
Practical focus
- Define the categories, thresholds, authorities, and records used to govern project changes before work is authorized or committed
- Use impact analysis, approval criteria, change boards, implementation plans, and closure evidence to make ownership, decisions, and exceptions traceable
- Review change status, decision rationale, affected requirements, validation, and residual risk at planned decision points rather than only at closure
- Prepare for an urgent or cumulative change bypassing security and operational review with escalation, recovery, and communication paths
Common mistakes
- Treating informal agreement as durable approval
- Leaving security ownership outside the project decision structure
- Recording activity without recording the decision and its rationale
- Discovering an urgent or cumulative change bypassing security and operational review only after operational handoff
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: