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.
Explanation
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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
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.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Part of
Integration Management
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.