A communications management plan is a document that defines how important information will be communicated to stakeholders throughout the project12. It should include the purpose, methods, frequency, and roles of communication, as well as any contractual obligations that may affect the communication process12.
By ensuring that the communications management plan covers contractual obligations, the project manager can avoid any confusion or conflict between the subcontractors and the client, as well as establish clear expectations and boundaries for communication. This can help improve the quality and efficiency of communication, as well as the overall success of the project12.
1: How to Create a Project Management Communication Plan 2: How to create a project management communication plan - Lucidchart

Project artifacts (documents, approvals, and records) are essential for regulated or legal-influenced projects.
To ensure transparency, traceability, and compliance, the project manager should:
A: Use a governance system to track documentation and ensure control.
D: Keep documents current and accessible to stakeholders.
E: Define processes with the team for consistent artifact management.
Option B focuses on assessment over storage and access.
Option C inappropriately delegates core project management responsibilities to a single function (legal).
References:
PMBOK Guide - Seventh Edition, Information and Documentation Management PMI Governance of Portfolios, Programs, and Projects Framework
##############################################

According to the PMBOK Guide, the project manager should plan, manage, and monitor the communication activities throughout the project life cycle. The project manager should also consider the stakeholder needs, preferences, and expectations when choosing the communication methods, tools, and technologies. The project manager should also update the communications management plan as needed to reflect any changes in the communication requirements or approach. Therefore, the project manager should update the communications management plan based on the product owner's preferences and distribute it to the team.
This will ensure that the communication is effective, timely, and consistent among the project stakeholders. References: PMBOK Guide, 6th edition, pages 361-362, 368-369.

When a key stakeholder requests additional work that is not in the scope, the first action a project manager should take is to evaluate the impact of the requested change. This involves assessing how the change will affect the project's scope, schedule, budget, quality, risk, and benefits. After a thorough evaluation, the project manager should submit a change request. This formalizes the process and ensures that the requested change is documented, evaluated, and approved (or rejected) systematically within the project's change control procedures.
References: = The PMBOK Guide outlines the importance of evaluating the impact of scope changes and the process for submitting change requests. It emphasizes that changes should be formally documented and processed through the project's change control system12. This approach is aligned with best practices in project management for handling out-of-scope requests3.