Change Control
The formal process of identifying, evaluating, approving, and recording changes to the project baseline.
Definition
Change Control is the integrated process by which proposed modifications to scope, schedule, cost, quality, or contract terms are documented, analysed for impact, approved or rejected by an authorised body, and reflected in the project baselines. It is the discipline that protects a project from uncontrolled scope creep while preserving the ability to adapt.
History
Formal change control matured inside the U.S. defence and aerospace sectors during the Apollo program and was codified in MIL-STD-973 and later in ISO 10007. PMI integrated it as Perform Integrated Change Control in the PMBOK® Guide.
Principles
- Every change is logged — approved, rejected, or deferred.
- Impact analysis covers scope, schedule, cost, risk, and quality before a decision is made.
- A single Change Control Board (CCB) holds approval authority within delegated thresholds.
- Approved changes flow into the baseline and the configuration record on the same day.
Applications
Change control is contractually mandatory on EPC, defence, and public-infrastructure work. On agile programs the equivalent mechanism is backlog refinement combined with release-level governance.
Common Mistakes
- Approving changes verbally and reconciling paperwork later — the audit trail never recovers.
- Bundling unrelated changes into a single request to push it through.
- Skipping the schedule-impact analysis because "it's only a small change."
Frequently Asked Questions
Who sits on the Change Control Board?
Typically the project sponsor or their delegate, the project manager, technical lead, cost and schedule controllers, and — on contracted work — a representative of the owner or client.Which calculators on PMMilestone.org apply to Change Control?
For Change Control, the most relevant tools on the flagship platform are the EVM Calculator (integrated cost-schedule performance). They reproduce the formulas referenced in this entry against your own project data.What is a common misconception about Change Control?
That integration means a single dashboard. Real integration is one WBS, one cost breakdown structure and one master schedule shared across planning, cost, risk and change — the dashboard is the by-product.Which related encyclopedia entries should I read alongside Change Control?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.How does Dr. Hassan Eliwa's research treat Change Control?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Change Control is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.How is Change Control defined on PMMilestone Research & Insights?
The formal process of identifying, evaluating, approving, and recording changes to the project baseline. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.
Related Entries
Further reading on PMMilestone.org
Curated companion resources hosted on the flagship platform,PMMilestone.org.
- For practitioners who want to go deeper, the Learning Tracks.
- Engineers researching this topic typically continue with the Books & Publications.
- A practical companion to this entry is the Schedule Health Checker.
- Closely related on the flagship platform is the Risk Register Template.
- Useful alongside this article is the PMMilestone.org knowledge hub.