1. Association for Project Management (APM). (2019). APM Body of Knowledge (7th ed.).
Section 3.3.5, 'Reporting': This section emphasizes that reporting should be timely, relevant, and appropriate for the audience, providing progress against the plan and highlighting exceptions. This supports the use of summary tools like RAG status (a form of exception reporting) and lists of key issues, rather than lengthy, detailed documents (refuting A).
Section 4.1.5, 'Issue management': This section details the process of managing issues, a key part of which is communicating their status. A project report is the formal vehicle for this communication (supporting C).
2. AXELOS. (2017). Managing Successful Projects with PRINCE2 (6th ed.). TSO (The Stationery Office).
Chapter 21, 'Management products', Section 21.2.10, 'Highlight Report': The PRINCE2 methodology specifies the 'Highlight Report' as the standard report from the Project Manager to the Project Board. Its template explicitly includes sections for the status of the stage and project (often using traffic lights/RAG) and for 'Major issues and risks'. This directly supports options B and C.
Section 21.2.2, 'Communication management approach': This document (analogous to a stakeholder management plan) is defined as a baseline management product created during initiation, confirming it is not part of a regular progress report (refuting D).
3. University of Washington. (n.d.). Project Management Center for Excellence, Templates.
The 'Project Status Report' template provided as a standard tool includes sections for "Overall Project Health" (with RAG indicators for Schedule, Scope, Budget, and Overall) and a dedicated section for "Issues". This serves as a practical example from a reputable institution that aligns with answers B and C.