When might change requests be initiated in project monitoring?

• A. To address team performance issues
• B. To manage changes in project scope only
• C. When there's a variance between actual results and planned results
• D. To update stakeholder engagement strategies

Answer: (C)

Change requests are often initiated in project monitoring when there is a variance between actual results and planned results. This situation highlights the need to assess and respond to discrepancies that may impact the project’s trajectory. When actual performance deviates from what was initially planned—whether in terms of schedule, cost, quality, or scope—project managers must analyze the cause of the variance. If the analysis concludes that adjustments are necessary to align the project with its objectives, a change request is created. This systematic response ensures that the project remains on track and helps in addressing issues proactively rather than reactively.

In contrast, the other options relate to specific scenarios but do not encompass the broader circumstances under which change requests are typically triggered during monitoring. For instance, addressing team performance issues or updating stakeholder engagement strategies may lead to change requests, but they don't necessarily arise directly from performance variances in project results. Managing changes in project scope is a narrower focus; while it is certainly a legitimate reason for a change request, it does not encapsulate all the reasons that might stem from variances in actual versus planned outcomes. Thus, the initiation of change requests in the context of monitoring is most accurately tied to discrepancies between expected and actual performance results.