The frequency of Highlight Reports is a primary, time-based control used by the Project Board to oversee progress within a management stage. According to PRINCE2, the 'Project controls' section of the Project Initiation Documentation (PID) is the authoritative place to define such control mechanisms, including the frequency of reporting. While the Communication Management Strategy also addresses the timing of communications, placing the frequency of a key control report in the Project Controls section ensures clarity and avoids potential contradictions. In a tailored environment with a "simple PID," as described in the scenario, removing this information from the strategy to consolidate it under Project Controls is a correct application of the 'tailor to suit the project environment' principle.

A. Delete entry 9 because activities for controlling the project should be planned as part of Project controls in the Project Initiation Documentation.

This is incorrect. A management strategy should define its own review cycle. Stating that the Communication Management Strategy will be reviewed at the end of each stage is appropriate content for this document.

B. No change to entry 9 because it describes the timing of performance reports.

This is incorrect because the reasoning is flawed. Entry 9 describes the review of the Communication Management Strategy itself, not the timing of performance reports like the Highlight Report.

1. AXELOS

"Managing Successful Projects with PRINCE2® 6th Edition" (2017)

Appendix A

Section A.21 - Project Controls. This section states that Project Controls describe how the Project Board will exercise control and should cover "reporting (the frequency and format of any reports to be used)". This supports the reasoning in option C that the frequency of Highlight Reports belongs in the Project Controls section.

2. AXELOS

"Managing Successful Projects with PRINCE2® 6th Edition" (2017)

Section 11.3.2 - Project controls. This section reinforces that reporting arrangements are a key element of the controls agreed upon during initiation and documented in the PID for the Project Board to exercise oversight.

3. AXELOS

"Managing Successful Projects with PRINCE2® 6th Edition" (2017)

Appendix A

Section A.5 - Communication Management Strategy. While this section notes that the strategy describes the "frequency of communication"

in the hierarchy of project documentation

the formal definition of a control (like reporting frequency) is primarily established in the Project Controls section. The strategy then details the execution of that communication. Therefore

consolidating the control definition in the Project Controls section is the superior approach.