PMP Change Control Questions: A Request Is Not an Approval

The customer has a small request. It will only take a day. Probably. Someone has already promised it for Friday. If this sounds familiar, you understand why PMP change control questions are about judgment as much as terminology.

A request is information to evaluate. It is not automatically permission to commit resources, change an approved baseline, or ignore a valuable opportunity. Your response depends on the delivery approach and the project's agreed decision process.

Identify what the request would change

Clarify the intended outcome and the reason for the request. Then examine the relevant impacts: scope, schedule, cost, quality, resources, risks, and benefits. A feature that looks tiny to one person may require testing, documentation, support, and a dependency nobody mentioned in the meeting.

Do not confuse a friendly stakeholder conversation with formal authorization. You can be helpful without promising something before the right decision has been made.

Work through an original example

A predictive project has an approved scope baseline. A customer asks for an additional dashboard. The project manager and team have documented the request and assessed its impact. The project process requires a change control board decision, which has not yet occurred. What should happen next?

• A. Begin development because the analysis is complete.
• B. Submit the assessed request to the authorized decision process.
• C. Perform the same impact analysis again.
• D. Reject all additions after baseline approval.

B fits the stated sequence. Analysis is complete, but authorization is still missing. A skips the decision. C repeats work without a stated reason. D treats controlled change as forbidden change. The point of control is informed decisions, not preserving a plan in a museum.

After the decision, close the loop

If the change is approved, update the affected plans and baselines as appropriate, communicate the decision, and coordinate implementation. If it is rejected or deferred, communicate that outcome too. A change log with an unanswered request is not a substitute for keeping people informed.

Approval also does not make delivery automatic. Ownership, dependencies, and verification still need attention. Check that the implemented result matches the authorized change.

Do not force every approach into one workflow

In adaptive work, upcoming product needs may be refined and reordered through backlog management. That does not mean anyone can interrupt current work, bypass contractual obligations, or spend unlimited money. Read the roles, commitments, and constraints described in the question.

In hybrid projects, a backlog decision can still affect a shared milestone or an approved external commitment. Follow the stated governance and coordinate across the affected work rather than relying on the word agile as a universal permission slip.

Practice spotting the missing step

On your next question, identify whether clarification, analysis, authorization, communication, or implementation is missing. Our PMP mindset guide adds broader context. To apply this habit under time pressure, register for the free 25-question PMP practice exam and use the 30-minute session as a starting point for focused review.

Continue your PMP preparation

Practise identifying whether a situation is uncertain or has already occurred in our PMP risk versus issue questions guide.

Explore Zero to PMP, our PMP exam preparation program. The program is being updated with new learning resources, and enrollment is currently closed.

Written by Sabri Calisici, project management instructor since 2008.