When Issues Arise During Project Work, Change Requests Are Submitted
PMBOK v8 Definition
A change request is a formal proposal to modify a document, deliverable, or baseline. When issues are found while project work is being performed, change requests are submitted to modify project policies or procedures, project or product scope, project cost or budget, project schedule, or the quality of the project or product results. Change requests may include corrective actions, preventive actions, defect repairs, or updates that reflect modified or additional ideas or content.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about integrated change control, the Assess and Implement Changes process, and the relationship between issues and change requests. Expect scenario-based questions where an issue is discovered during execution, and you must identify the correct next step—submitting a formal change request—rather than directly modifying the work.
Key Points to Remember (for the exam)
- Definition: Change request = formal proposal to modify a document, deliverable, or baseline
- Trigger: Issues found while project work is being performed
- What Can Be Modified: Project policies or procedures, project or product scope, project cost or budget, project schedule, or quality of results
- Types of Change Requests: Corrective actions, preventive actions, defect repairs, or updates
- Required Information: Should typically include estimated schedule and cost impacts before approval
- Decision Makers: Approved, deferred, or rejected by designated person (project manager, sponsor, CCB) as specified in the project management plan
- Documentation: All dispositions recorded in the change log as a project document update
Typical PMI Exam Example
During project execution, a team member discovers that a critical deliverable does not meet quality standards due to a process flaw. The project manager receives this as an issue. What should the project manager do next? Answer: Submit a change request to modify project procedures, including estimated schedule and cost impacts, for review by the change control board.
PMI Exam Traps
-
Trap: Confusing "issue" with "change request"
-
Reality: An issue triggers a change request; they are not the same thing
-
Trap: Thinking change requests only modify scope
-
Reality: Change requests can modify policies, procedures, scope, cost, budget, schedule, or quality
-
Trap: Assuming the project manager can approve all change requests
-
Reality: Approval authority is defined in the change management plan; some changes require CCB approval, especially those impacting baselines
-
Trap: Confusing "corrective action" with "defect repair"
-
Reality: Corrective action brings future performance in line with plan; defect repair fixes nonconforming deliverables
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Change Management Plan | Input to change control process | Defines CCB authority and how the change control system is implemented |
| Change Log | Output/document update | Records disposition (approved, deferred, rejected) of all change requests |
| Integrated Change Control | Process area | Formal process to assess and implement changes that impact baselines |
| Approved Change Requests | Output of change control | Implemented via the Manage Project Execution process |
| Assess and Implement Changes | Performance domain | Example flow shows how changes are evaluated against scope, finance, schedule, resources, stakeholders, risk |
Quick Review Questions
- What four types of content can a change request include?
- Who determines whether a change request is approved, deferred, or rejected?
- Where is the disposition of all change requests recorded?
- What information should change requests typically include before they can be approved?
- What process implements approved change requests?
PMBOK v8 Reference
Section 2 – Project Management Performance Domains, pages 29-30 (Assess and Implement Changes process, Change Requests definition, Figure 2-11)