PMP · Question #1023
A multimillion-dollar project has started and is in the execution phase. A local regulatory authority has just announced changes to the requirements that will need to be implemented in 6 months…
The correct answer is A. Review the new requirements with the compliance department to determine if a change request is. When mandatory regulatory changes arise during project execution, the project manager must first review these requirements with the compliance department to assess their impact and determine the need for a change request.
Question
A multimillion-dollar project has started and is in the execution phase. A local regulatory authority has just announced changes to the requirements that will need to be implemented in 6 months, prior to completing the project execution phase. What should the project manager do next?
Options
- AReview the new requirements with the compliance department to determine if a change request is
- BProceed with the defined project requirements and delay implementing the new requirements
- CAdd the new requirements to the project scope immediately since they are mandatory changes
- DIgnore the new requirements as the current budget and schedule do not allow for any changes
How the community answered
(26 responses)- A77% (20)
- B12% (3)
- C8% (2)
- D4% (1)
Why each option
When mandatory regulatory changes arise during project execution, the project manager must first review these requirements with the compliance department to assess their impact and determine the need for a change request.
When faced with new mandatory regulatory changes, the project manager's immediate step is to review them with the compliance department to understand their exact implications, assess the impact on the project, and then follow the integrated change control process, which often begins with a change request. This ensures legal adherence and proper project adjustment.
Delaying implementation of mandatory regulatory changes can lead to legal non-compliance and severe consequences for the project and organization.
Adding new requirements immediately without proper review and change control can disrupt the project, bypass impact assessment, and potentially lead to budget overruns or scope creep.
Ignoring mandatory regulatory changes is a serious breach of compliance and can result in legal penalties, project failure, or even organizational shutdown.
Concept tested: Integrated change control for regulatory compliance
Topics
Community Discussion
3
Bao N.Jul 5, 2026A is correct. You never just absorb new regulatory requirements into scope without running them through the change control process, and the compliance department is your first stop to figure out what the change actually means for the project. C trips people up because the requirements are mandatory, but mandatory does not mean skip the process. B and D are flat out wrong since you cannot ignore or delay compliance, and the real PMP move is to assess the impact first, then submit a formal change request.
Fatima Z.Jul 5, 2026A is correct because regulatory changes must be evaluated before you touch the project scope, so you loop in the compliance department first to figure out if a formal change request is even needed. C is the trap because mandatory does not mean "skip the change control process and dump it into scope immediately." D and B are both fast tracks to a compliance violation, which will sink a multimillion-dollar project faster than any schedule slip. Saw this exact scenario on my exam last spring and almost clicked C because the word "mandatory" made me panic, but I remembered my little mnemonic "RACE" - Review,
Orla P.Jul 5, 2026Confirmed A on exam last week. You never absorb regulatory changes straight into scope without running them through compliance and the change control process first, no matter how mandatory they seem.