---
ref_id: PR31
ref_type: Process
ref_name: "Perform Integrated Change Control"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1"
companion_ref_shortcode: PG-APG
related_skills:
  - SKL-05-02
related_artifacts:
  - A12
  - A14
file_path: "reference/processes/PR31-perform-integrated-change-control.md"
---
# PR31 — Perform Integrated Change Control

## Process Identity
| Field | Value |
|---|---|
| **Process ID** | PR31 |
| **Process Name** | Perform Integrated Change Control |
| **Process Group** | Monitoring and Controlling |
| **Knowledge Area** | Integration Management |
| **PMBOK Source** | Process Groups: A Practice Guide §7.2; PMBOK 8 §2.1.6.8 |

---

## Purpose
Review all change requests; approve changes and manage changes to deliverables, project documents, and the project management plan; and communicate the decisions. Allows documented changes to be considered in an integrated manner while addressing overall project risk.

---

## Inputs
| Input | Description |
|---|---|
| Project management plan | Change management plan, configuration management plan, scope/schedule/cost baselines |
| Project documents | Basis of estimates, change log, requirements traceability matrix, risk report |
| Work performance reports | Performance data from Monitor and Control Project Work |
| Change requests | Formal proposals to modify any document, deliverable, or baseline |
| Enterprise environmental factors | Regulatory requirements, organizational governance |
| Organizational process assets | Change control procedures, templates |

---

## Tools and Techniques
| Tool / Technique | Notes |
|---|---|
| Expert judgment | Evaluating impact of proposed changes |
| Change control tools | Configuration management system, automated workflows |
| Data analysis | Alternatives analysis, cost-benefit analysis |
| Decision making | Voting, autocratic decision making, multicriteria decision analysis |
| Meetings | Change Control Board (CCB) sessions |

---

## Outputs
| Output | Description |
|---|---|
| Approved change requests | Changes approved for implementation via Direct and Manage Project Work |
| Project management plan updates | Any component updated as a result of approved changes |
| Project documents updates | Change log updated with disposition of all requests |

---

## Key Concepts
- Performed throughout the project from start through completion.
- Before baselines are established, changes do not require formal control.
- Once baselined, all changes go through this process.
- Change requests may be approved, deferred, or rejected.
- A **Change Control Board (CCB)** may be used for larger or more complex projects.
- Applies to both **predictive** (formal change requests) and **adaptive** approaches (backlog management for adaptive).

---

## PMBOK 8 Alignment
- Corresponds to **Assess and Implement Changes** process in PMBOK 8 §2.1.6.8.
- Integrated change control is a core mechanism for maintaining the **Governance** performance domain.
- Supports the principle: *Navigate Complexity* and *Enable Change*.

---

## Common Pitfalls
- Allowing verbal changes without formal documentation.
- Bypassing the CCB for convenience.
- Failing to assess cross-domain impact (scope, schedule, cost, risk, resources).

---

## Related Processes
- Feeds from: PR30 (Monitor and Control Project Work), PR37 (Control Quality)
- Feeds into: PR28 (Direct and Manage Project Work) — for approved change requests
- Cross-links: PR32 (Validate Scope), PR33 (Control Scope), PR34 (Control Schedule), PR35 (Control Costs)

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A12 | Artifact | Primary artifact produced or updated by this process |
| A14 | Artifact | Primary artifact produced or updated by this process |
| SKL-05-02 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Is the change control board (CCB) composition and authority documented?
2. Are all change requests formally logged before assessment begins?
3. Are impacts on scope, schedule, cost, quality, and risk assessed for each change?
4. Are approved changes reflected in updated baselines and management plans?
5. Are rejected changes documented with rationale?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
