PRINCE2 (TM) Highlight Report
To get an editable copy of this template to use on your project go to http://www.stakeholdermap.com/project-templates/prince-2-templates.html
1. This Report
1.1. Date of Highlight Report
1.1.1. [...]
1.2. Period Covered
1.2.1. [...]
2. Status Summary
2.1. [Give an overview of the status of the stage at this time]
3. This Reporting Period
3.1. Work Packages
3.1.1. [Work Package Ref]
3.1.1.1. [Work Package Name]
3.1.1.2. [Status]
3.1.1.3. [Notes]
3.1.2. [Work Package Ref]
3.1.2.1. [Work Package Name]
3.1.2.2. [Status]
3.1.2.3. [Notes]
3.1.3. [Work Package Ref]
3.1.3.1. [Work Package Name]
3.1.3.2. [Status]
3.1.3.3. [Notes]
3.1.4. [Work Package Ref]
3.1.4.1. [Work Package Name]
3.1.4.2. [Status]
3.1.4.3. [Notes]
3.1.5. [Work Package Ref]
3.1.5.1. [Work Package Name]
3.1.5.2. [Status]
3.1.5.3. [Notes]
3.1.6. [Work Package Ref]
3.1.6.1. [Work Package Name]
3.1.6.2. [Status]
3.1.6.3. [Notes]
3.1.7. [Work Package Ref]
3.1.7.1. [Work Package Name]
3.1.7.2. [Status]
3.1.7.3. [Notes]
3.2. Products
3.2.1. [Product Ref]
3.2.1.1. [Product name]
3.2.1.2. [Status]
3.2.1.3. [Notes]
3.2.2. [Product Ref]
3.2.2.1. [Product name]
3.2.2.2. [Status]
3.2.2.3. [Notes]
3.2.3. [Product Ref]
3.2.3.1. [Product name]
3.2.3.2. [Status]
3.2.3.3. [Notes]
3.2.4. [Product Ref]
3.2.4.1. [Product name]
3.2.4.2. [Status]
3.2.4.3. [Notes]
3.2.5. [Product Ref]
3.2.5.1. [Product name]
3.2.5.2. [Status]
3.2.5.3. [Notes]
3.2.6. [Product Ref]
3.2.6.1. [Product name]
3.2.6.2. [Status]
3.2.6.3. [Notes]
3.2.7. [Product Ref]
3.2.7.1. [Product name]
3.2.7.2. [Status]
3.2.7.3. [Notes]
3.3. Corrective Actions Undertaken
3.3.1. [Enter Corrective Actions taken during the period]
4. Next Reporting Period
4.1. Work Packages
4.1.1. [Work Package Ref]
4.1.1.1. [Work Package Name]
4.1.1.2. [Status]
4.1.1.3. [Notes]
4.1.2. [Work Package Ref]
4.1.2.1. [Work Package Name]
4.1.2.2. [Status]
4.1.2.3. [Notes]
4.1.3. [Work Package Ref]
4.1.3.1. [Work Package Name]
4.1.3.2. [Status]
4.1.3.3. [Notes]
4.1.4. [Work Package Ref]
4.1.4.1. [Work Package Name]
4.1.4.2. [Status]
4.1.4.3. [Notes]
4.1.5. [Work Package Ref]
4.1.5.1. [Work Package Name]
4.1.5.2. [Status]
4.1.5.3. [Notes]
4.2. Products to be completed
4.2.1. [Product Ref]
4.2.1.1. [Product name]
4.2.1.2. [Notes]
4.2.2. [Product Ref]
4.2.2.1. [Product name]
4.2.2.2. [Notes]
4.2.3. [Product Ref]
4.2.3.1. [Product name]
4.2.3.2. [Notes]
4.2.4. [Product Ref]
4.2.4.1. [Product name]
4.2.4.2. [Notes]
4.2.5. [Product Ref]
4.2.5.1. [Product name]
4.2.5.2. [Notes]
4.2.6. [Product Ref]
4.2.6.1. [Product name]
4.2.6.2. [Notes]
4.3. Corrective Actions
4.3.1. [Enter Corrective Actions to be completed during the next period]
5. Project and Stage Tolerance Status
5.1. [Report how execution of the project and stage are performing against its tolerances (e.g. cost/time/scope actuals and forecast)]
6. Requests for Change
6.1. [Identify any changes raised, approved/rejected and pending]
7. Key Issues and Risks
7.1. [Summarise actual or potential problems and risks]
8. Lessons Report (if appropriate)
8.1. [Provide a review of what went well, what went badly, and give any recommendations for corporate or programme management consideration]
9. Document information
9.1. Project Name
9.1.1. [name]
9.2. Date
9.2.1. [date]
9.3. Release
9.3.1. Draft/Final
9.4. Author
9.4.1. [author]
9.5. Owner
9.5.1. [owner]
9.6. Client
9.6.1. [client]
9.7. Document Number
9.7.1. [number]
9.8. Revision, Approvals & Distribution
9.8.1. Revision History
9.8.1.1. Revision # [....]
9.8.1.1.1. Revision Date
9.8.1.1.2. Previous Revision Date
9.8.1.1.3. Summary of Changes
9.8.1.1.4. Changes Marked
9.8.1.2. Revision # [....]
9.8.1.2.1. Revision Date
9.8.1.2.2. Previous Revision Date
9.8.1.2.3. Summary of Changes
9.8.1.2.4. Changes Marked
9.8.1.3. Revision # [....]
9.8.1.3.1. Revision Date
9.8.1.3.2. Previous Revision Date
9.8.1.3.3. Summary of Changes
9.8.1.3.4. Changes Marked
9.8.1.4. Date of next revision:
9.8.1.4.1. [....]
9.8.2. Approvals
9.8.2.1. Approval # [....]
9.8.2.1.1. Name
9.8.2.1.2. Signature
9.8.2.1.3. Title
9.8.2.1.4. Date of Issue
9.8.2.1.5. Version
9.8.2.2. Approval # [....]
9.8.2.2.1. Name
9.8.2.2.2. Signature
9.8.2.2.3. Title
9.8.2.2.4. Date of Issue
9.8.2.2.5. Version
9.8.2.3. Approval # [....]
9.8.2.3.1. Name
9.8.2.3.2. Signature
9.8.2.3.3. Title
9.8.2.3.4. Date of Issue
9.8.2.3.5. Version
9.8.3. Distribution
9.8.3.1. Distribution # [....]
9.8.3.1.1. Name
9.8.3.1.2. Title
9.8.3.1.3. Date of issue
9.8.3.1.4. Version
9.8.3.2. Distribution # [....]
9.8.3.2.1. Name
9.8.3.2.2. Title
9.8.3.2.3. Date of issue
9.8.3.2.4. Version
10. How to use this template
10.1. How to share this template with your team
10.1.1. Send an email
10.1.1.1. 1. Click Share this map
10.1.1.2. 2. Select Invite People
10.1.1.3. 3. Write a message
10.1.1.4. 4. Click Invite
10.1.2. Send a link
10.1.2.1. 1. Click Share this map
10.1.2.2. 2. Tick Link to share
10.1.2.3. 3. Copy the link to share it
10.1.3. Export
10.1.3.1. 1. Click down arrow, bottom right
10.1.3.2. 2. Select the export option you want
10.2. How to complete this template
10.2.1. Complete the sections in square brackets
10.2.1.1. [....]
10.2.2. Read these sections for help on this template
10.2.2.1. Purpose
10.2.2.2. Advice
10.2.3. Navigate using the links in Contents
10.2.3.1. Contents
10.3. Attribution
10.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS
10.4. Get this template here
11. Overview
11.1. Purpose
11.1.1. A Highlight Report is used to provide the Project Board (and possibly other stakeholders) with a summary of the stage status at intervals defined by them. The Project Board uses the report to monitor stage and project progress. The Project Manager also uses it to advise the Project Board of any potential problems or areas where the Project Board could help.
11.2. Contents
11.2.1. The Highlight Report should cover the following topics.
11.2.2. Status Summary
11.2.3. This Reporting Period
11.2.4. Next Reporting Period
11.2.5. Project and Stage Tolerance Status
11.2.6. Requests for Change
11.2.7. Key Issues and Risks
11.2.8. Lessons Report (if appropriate)
11.3. Advice
11.3.1. The Highlight Report is derived from the: Project Initiation Documentation; Checkpoint Reports; Issue Register, Quality Register and Risk Register; Stage Plan and actuals: and Communication Management Strategy
11.3.2. The Highlight Report can take a number of formats, including: Presentation to the Project Board (physical meeting or conference call); Document or email to the Project Board; Entry in a project management tool.
11.3.3. The following quality criteria should be observed:
11.3.3.1. The level and frequency of progress reporting required by the Project Board is right for the stage and/or project
11.3.3.2. The Project Manager provides the Highlight Report at the frequency, and with the content, required by the Project Board
11.3.3.3. The information is timely, useful, accurate and objective
11.3.3.4. The report highlights any potential problem areas.