Change Requests
A change request is a formal proposal to modify any document, deliverable, or baseline on a project. Change requests include corrective actions, preventive actions, defect repairs, and updates.
Know it well enough for the exam? Questions on Change Requests are scenario-based, not definitional.
Practice it freeExplanation
Change requests are generated throughout the project lifecycle and can originate from any stakeholder. They may arise from issues discovered during execution, variance analysis during monitoring, quality audits, risk responses, or stakeholder feedback. All change requests must be formally documented and processed through the Perform Integrated Change Control process, regardless of their magnitude.
There are four categories of change requests. Corrective actions realign project performance with the project management plan. Preventive actions proactively reduce the probability or impact of future negative events. Defect repairs address quality shortcomings in project deliverables. Updates are modifications to formally controlled project documents, plans, or baselines.
Once submitted, change requests are evaluated for their impact across all project constraints. The CCB or designated authority approves, rejects, or defers them. Approved change requests are implemented through the Direct and Manage Project Work process and their status is tracked in the change log. Even verbal requests from stakeholders should be documented formally before being processed.
Key Points
- •Formal proposals that must go through Perform Integrated Change Control
- •Include corrective actions, preventive actions, defect repairs, and updates
- •Can originate from any stakeholder at any point in the project
- •Must be documented regardless of size — verbal requests should be formalized
Exam Tip
On the exam, if a stakeholder asks for a change verbally, the correct first step is to document the change request formally and submit it through integrated change control — not to implement it immediately.
Frequently Asked Questions
Related Topics
Perform Integrated Change Control
Perform Integrated Change Control is the process of reviewing all change requests, approving or rejecting changes, managing changes to deliverables, project documents, and the project management plan, and communicating the decisions.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Change Log
A change log is a comprehensive list of all change requests submitted during the project, along with their current status (approved, rejected, or deferred) and key details.
Direct and Manage Project Work
Direct and Manage Project Work is the process of leading and performing the work defined in the project management plan and implementing approved changes to achieve the project objectives.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Part of
Integration Management
Practice Change Requests
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.