In which situation would a change request typically be generated?

• A. When completing project documentation
• B. When assessing project contributions
• C. When addressing schedule variance
• D. When updating risk registers

Answer: (C)

A change request is typically generated when there is a need to modify some aspect of the project due to deviations from the original plan. Addressing schedule variance is a prime example of a situation that may necessitate such a request. When actual project performance reveals a discrepancy between planned and actual timing—such as delays that affect milestones or deliverables—project managers must assess the impact of this variance.

To correct or adapt to the schedule, it may become necessary to propose changes to the project plan, resources, or timelines. This process ensures that the project remains aligned with its goals, and stakeholders are informed and involved in decisions that alter the project's scope or timeline. Therefore, addressing schedule variance is an integral part of project monitoring and controlling that triggers the change management process, leading to the generation of a formal change request.

In contrast, completing project documentation, assessing project contributions, and updating risk registers, while essential project activities, usually do not inherently require changes to the planned scope, timelines, or resources, and therefore do not typically lead to change requests.