In the context of PRINCE2 7 and the Progress practice, the Highlight Report is a vital time-driven management product used to provide the Project Board with a summary of the stage status at agreed intervals. It serves as the primary mechanism for facilitating 'Managing by Exception,' enabling the P…In the context of PRINCE2 7 and the Progress practice, the Highlight Report is a vital time-driven management product used to provide the Project Board with a summary of the stage status at agreed intervals. It serves as the primary mechanism for facilitating 'Managing by Exception,' enabling the Project Board to monitor the project's health without micromanaging the Project Manager's day-to-day work.
Unlike event-driven controls (such as the Exception Report), the Highlight Report is submitted at a specific frequency—e.g., weekly or monthly—defined during the 'Initiating a Project' process or updated at stage boundaries. Its core purpose within the Progress practice is to compare actual achievements against the authorized Stage Plan. The report confirms whether the stage is progressing within the agreed tolerances for time, cost, quality, scope, benefits, sustainability, and risk.
Typical contents of a Highlight Report include:
1. Date and period covered.
2. Budget and schedule status (often utilizing a Red/Amber/Green or 'RAG' status indicator).
3. Products completed during the current reporting period.
4. Products and Work Packages scheduled for completion in the next period.
5. A summary of current risks and issues, including any changes to the risk exposure.
By reviewing this report, the Project Board can maintain oversight and provide ad-hoc direction. If the report indicates that the stage is within tolerance, the Project Manager continues work; if the status indicates a potential tolerance breach, it serves as an early warning system, though the actual breach would require an Exception Report. Ultimately, the Highlight Report ensures a consistent flow of information, preventing the communication vacuums that often jeopardize project governance.
Guide to the Highlight Report in PRINCE2 Practitioner v7
What is a Highlight Report? A Highlight Report is a time-driven control document used by the Project Manager to report the status of the stage to the Project Board. It allows the Project Board to monitor stage and project progress at a high level without needing to get involved in the day-to-day management, thereby supporting the principle of Manage by Exception.
Why is it Important? The Highlight Report is the primary mechanism for the Project Board to maintain visibility during the Controlling a Stage process. It ensures the Board is aware of actual progress against the Stage Plan, current risks, and potential issues. It confirms whether the stage is remaining within agreed tolerances (time, cost, quality, scope, risk, and benefit). Without it, the Project Board would be 'flying blind' or would need to micromanage the Project Manager.
How it Works The frequency and format of the Highlight Report are agreed upon during the initiation stage and documented in the Communication Management Approach. For example, it might be required weekly, fortnightly, or monthly.
Key Contents usually include: • Date and Period: The specific timeframe covered. • Status Summary: A general overview of the stage health (often using Red/Amber/Green indicators). • This Reporting Period: Work packages completed, products delivered, and resources utilized. • Next Reporting Period: Work planned for the immediate future. • Tolerance Status: Current status of stage tolerances. • Issues and Risks: A summary of key risks and issues that affect the stage.
Exam Tips: Answering Questions on Highlight Report In the PRINCE2 Practitioner exam, questions about Highlight Reports often test your ability to apply the concept to a specific scenario.
1. Time-Driven vs. Event-Driven: Remember that Highlight Reports are time-driven (e.g., sent every Friday). Do not confuse them with Exception Reports (which are event-driven, sent only when a tolerance is forecast to be exceeded) or End Stage Reports (sent at the end of a stage).
2. The Hierarchy of Reporting: Ensure you identify the sender and receiver in the scenario: • Team Manager to Project Manager = Checkpoint Report. • Project Manager to Project Board = Highlight Report.
3. Tailoring: Pay attention to the project environment. For a small, internal project, a Highlight Report might be a simple email or a brief verbal update during a coffee meeting. For a large, complex project, it might be a formal slide deck. If an exam question suggests a 'heavy' document for a 'simple' project, that is likely an incorrect application of PRINCE2.
4. Management by Exception: If a question asks how the Project Board keeps control without attending meetings, the answer usually involves the review of Highlight Reports.
5. Content Check: If a question asks what should be included, look for 'summary' information. Detailed technical specifications or individual timesheets are usually too granular for a Highlight Report; it should focus on progress, future plans, and tolerance status.