What is the effect of formal change control on project scope?

• A. It ignores stakeholder input
• B. It delays progress without benefit
• C. It validates proposed changes with stakeholders and re-baselines the plan
• D. It permanently locks scope with no changes

Answer: (C)

Formal change control ensures that any proposed change to the project scope is evaluated and approved with input from stakeholders, and the project plan is updated to reflect the approved change. When a change request comes in, its impact on scope, schedule, and budget is analyzed; if stakeholders agree, the scope baseline and related plans are re-baselined to match the new direction. This process keeps the project aligned with objectives and prevents uncontrolled scope creep, because only approved changes become part of the scope and all decisions are traceable. While changes can introduce some delay, the benefit is a governed, transparent path that safeguards the project’s goals. The other ideas don’t fit: stakeholder input isn’t ignored, progress isn’t simply delayed without value, and the scope isn’t permanently locked—changes are managed through an approved process.