Which project document is updated in the Control Stakeholder Engagement process?

According to the PMBOK® Guide (Project Management Body of Knowledge), specifically within the Project Stakeholder Management knowledge area and the Monitor Stakeholder Engagement process (referred to as " Control Stakeholder Engagement " in some exam versions):

Issue Log (Option B): This is a primary project document updated during this process. As stakeholders are engaged and their concerns or requirements are addressed, new issues may be identified or existing issues may be resolved. The Issue Log is used to document and track these items, ensuring that someone is assigned to resolve them and that the resolution is communicated back to the relevant stakeholders.

Project Reports (Option A): While communication is a key part of stakeholder engagement, " Project Reports " are typically an input to the process (providing information to share) or an output of Monitor and Control Project Work. They are not classified as a " Project Document Update " in the specific context of this process ' s standardized outputs.

Lessons Learned Documentation (Option C): While lessons learned are captured throughout the project, the formal update to the Lessons Learned Register is more characteristic of the Manage Project Knowledge or Close Project or Phase processes.

Work Performance Information (Option D): This is a Work Performance Data transformation that occurs during the process, but it is classified as a Process Output, not a " Project Document Update. " Project document updates refer specifically to existing files like the Issue Log, Stakeholder Register, or Project Schedule.

In the PMI framework, the Issue Log serves as a critical tool for maintaining trust with stakeholders. By actively documenting and addressing their concerns, the Project Manager can manage expectations and ensure that project objectives remain aligned with stakeholder needs.