Start with the governance decision, not the most active-looking answer
PMP situational questions often describe a defect, delay, stakeholder request or newly discovered constraint and then offer several plausible actions. The strongest answer usually preserves both leadership and control: understand the situation, involve the right people, evaluate consequences and follow the agreed decision process before changing controlled work.
Clarify → record → analyse → request → authorize → implement → update → verify. The exact level of formality depends on the delivery approach and project governance, but silently changing an approved baseline is rarely the right response.
An issue is a present condition. A proposed response may be corrective, preventive or a defect repair. A change request is the formal vehicle used when authorization is required. These labels answer different questions, so they can apply to the same situation.
Corrective action, preventive action, defect repair and change request
Corrective and preventive actions concern project performance. Defect repair concerns a result that does not conform. A change request concerns authorization and traceability. Repairing a faulty feature may also require a corrective process improvement and a change request if approved scope, cost, schedule or another controlled element must change.
Does the action stay within already approved authority and tolerances, or does it modify something that governance says must be controlled? The project management plan—not personal preference—defines the route.
The end-to-end integrated change-control sequence
Clarify the trigger
Separate fact from assumption. Identify the need, defect, issue, opportunity or external requirement and document it in the appropriate record.
Evaluate connected effects
Assess scope, schedule, cost, quality, resources, risk, procurement, compliance, benefits, customer outcomes and business value—not just the area named by the requester.
Use authorized governance
Submit the proposal with options and evidence. The person or group named in the plan approves, rejects, defers or requests more information.
Execute the approved path
Coordinate the work only after authorization when authorization is required. An unapproved idea is not part of the controlled plan.
Maintain one source of truth
Update relevant plans, baselines, backlog items, logs, forecasts, contracts and communications so teams do not work from conflicting versions.
Confirm the intended outcome
Inspect the repair or measure performance, close or monitor the action, record decisions and capture reusable learning.
A change control board (CCB) is one possible authority, not a mandatory answer in every scenario. The sponsor, customer, product owner, regulator or delegated manager may hold authority. Read the scenario for governance clues and avoid inventing a board when the plan assigns the decision elsewhere.
Do not confuse the issue log, change request and change log
Tracks a current problem, owner, priority, actions, status and escalation.
Describes the proposed modification, reason, analysis, options and recommendation.
Tracks submitted requests, status, decision, authority, date and implementation outcome.
The records are related but not interchangeable. A vendor delay belongs in the issue log. A proposal to move the committed milestone may become a change request. The approval or rejection belongs in the change log. Relevant learning can also enter the lessons learned register.
For the earlier distinction between uncertain and present conditions, use the risk register vs issue log vs assumption log guide.
Worked scenario 1: a vendor delay threatens a contractual milestone
Situation: A supplier confirms that a critical component will arrive ten days late. The project manager believes overtime could recover four days, while the remaining delay would affect testing and the customer milestone.
The delay now exists; assign ownership and capture its impact.
Compare overtime, re-sequencing, alternate supply and milestone effects.
Route any baseline or contract change to the authorized role.
Update approved records, communicate and monitor recovery.
Starting overtime immediately may look decisive but can create unapproved cost, fatigue and quality risk. Waiting for the sponsor without analysis is also weak. The project manager first develops evidence and options, then uses the defined authority.
Worked scenario 2: acceptance testing finds a calculation defect
The team should document and analyse the nonconformance, determine its cause and propose defect repair. If the fix fits authorized work, the team follows its quality and delivery process. If it changes controlled scope, schedule, cost or a contractual commitment, submit a change request. After repair, retest against the acceptance criteria.
Also consider preventive or corrective improvement: a missing review rule may need correction so future calculations follow the agreed method. Fixing only the visible output can leave the process failure in place.
Predictive, agile and hybrid change decisions
In predictive work, approved baselines provide the comparison point, and integrated change control evaluates proposed modifications across the plan. A stakeholder request should be understood and analysed before the baseline changes.
Adaptive delivery expects learning and reprioritization. The product owner manages ordering and value in the product backlog, while the delivery team protects the iteration or Sprint Goal and collaborates when new information appears. “Agile welcomes change” does not mean anyone can interrupt work or alter commitments without conversation and product governance.
Hybrid initiatives use both patterns. Product backlog items may evolve frequently, while release dates, regulatory evidence, contracts, budgets or hardware milestones remain formally controlled. First identify which part of the initiative the change affects. The agile vs predictive vs hybrid guide explains how uncertainty and governance shape that choice.
Use the expedited or emergency route defined by governance. Urgency can shorten the decision cycle, but it does not justify undocumented implementation. Preserve authority, traceability, communication and post-implementation review.
Common PMP situational-question traps
- Implementing a stakeholder request before analysing its full effect.
- Assuming the sponsor, CCB or project manager always has approval authority.
- Updating a schedule baseline before the request is approved.
- Treating corrective action and defect repair as synonyms.
- Escalating immediately when the team can first clarify and analyse.
- Rejecting a request without recording it because it appears inconvenient.
- Using “agile” as permission to disrupt an iteration or ignore contracts and compliance.
- Closing the change when work finishes without verifying the outcome.
Look for answers that demonstrate servant leadership and evidence-based governance: collaborate, investigate, analyse impacts, follow the plan, communicate and learn.
Practice checks with detailed explanations
A customer asks a developer to add a report during a predictive project. What should the project manager do first?
Best response: clarify the need and evaluate impacts with the team before routing the proposal through the defined change process. Immediate implementation bypasses governance; immediate rejection ignores potential value.
A quality review finds that one delivered component does not meet an approved tolerance. What action best describes correcting the component?
Best response: defect repair. Analyse whether the repair also needs authorization and whether corrective or preventive process action is warranted.
A recurring handoff delay is likely to affect future milestones. The team changes its review cadence without altering a baseline. What type of action is this?
Best response: corrective action because it seeks to realign future performance with the plan. Whether a formal request is needed depends on the project’s control thresholds and authority.
A hybrid team receives an urgent compliance requirement during an iteration. Should it simply add the work?
Best response: assess urgency and impact with the product owner, team and compliance authority, then use the project’s emergency and product-governance rules. Protect the iteration goal where possible while honoring mandatory obligations.
How this supports the active July 2026 PMP exam
PMI’s current examination content outline weights People at 33%, Process at 41% and Business Environment at 26%. It also describes an approximate mix of 40% predictive and 60% adaptive or agile and hybrid approaches. Change scenarios therefore test more than a memorized process: connect team collaboration, governance, compliance, value and business impact to the delivery context.
Use this guide to build a decision habit, then apply it in the free 180-question PMP mock test and the structured PMP course material.
Frequently asked questions
Is corrective action always a change request on the PMP exam?
Corrective action describes the purpose of an action: bringing expected future performance back in line with the plan. If that action changes an approved baseline, plan component, controlled document or deliverable, it must follow the applicable change-control process.
What is the difference between corrective action and defect repair?
Corrective action addresses future project performance, while defect repair modifies a nonconforming product or component. A single situation can require both, such as repairing a faulty release and improving the process that allowed the fault.
Who approves a PMP change request?
The project management plan defines the authority. It may be the sponsor, product owner, change control board, customer, regulator or another authorized role. The project manager facilitates analysis and follows that governance rather than assuming universal approval authority.
Can an emergency change bypass approval?
An emergency may use an expedited path defined by governance, but urgency does not erase authorization, traceability or communication. Record the reason, decision, implementation and follow-up review.
How does change control work in agile or hybrid delivery?
Adaptive work accepts reprioritization through product and backlog governance, while the team protects the current iteration goal. Funding, contracts, compliance, releases and predictive portions of a hybrid initiative may still require formal authorization.
Official PMI references
Verify current credential details on PMI’s PMP certification page, review the July 2026 exam update, consult the 2026 examination content outline, and check terminology in the PMI lexicon. ITCertPath provides independent, original preparation content and does not reproduce confidential exam questions.