HKSM
Change Control System
A documented framework of processes that specifies how change requests to project deliverables and documents are submitted, analyzed, approved or rejected, implemented, and recorded.
Key Points
- Defines clear steps to propose, evaluate, approve or reject, and log change requests.
- Assigns decision-making roles (often including a change control board) and escalation paths.
- Ensures baselines and related documents are updated after approved changes.
- Works with configuration management to maintain version control and traceability.
Example
A stakeholder asks to add a new reporting feature mid-project. The team submits a change request using the standard form, the impact on scope, cost, and schedule is analyzed, and the change control board reviews it. After approval, the scope baseline and schedule are updated, the change is recorded in the change log, and updated documents are version-controlled.
PMP Example Question
Which statement best describes the primary purpose of a change control system?
- To determine the root causes of defects in deliverables
- To formalize how changes to deliverables and documents are proposed, evaluated, decided upon, and documented
- To create and maintain the WBS dictionary
- To manage day-to-day team communications
Correct Answer: B — A formal process for proposing, evaluating, deciding on, and tracking changes
Explanation: The change control system defines the procedures to manage and control modifications to project deliverables and documentation; the other options address different project management activities.
