PRINCE2 (TM) Highlight Report

To get an editable copy of this template to use on your project go to

Get Started. It's Free
or sign up with your email address
PRINCE2 (TM) Highlight Report by Mind Map: PRINCE2 (TM) Highlight Report

1. Document information

1.1. Project Name

1.1.1. [name]

1.2. Date

1.2.1. [date]

1.3. Release

1.3.1. Draft/Final

1.4. Author

1.4.1. [author]

1.5. Owner

1.5.1. [owner]

1.6. Client

1.6.1. [client]

1.7. Document Number

1.7.1. [number]

1.8. Revision, Approvals & Distribution

1.8.1. Revision History Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Revision # [....] Revision Date Previous Revision Date Summary of Changes Changes Marked Date of next revision: [....]

1.8.2. Approvals Approval # [....] Name Signature Title Date of Issue Version Approval # [....] Name Signature Title Date of Issue Version Approval # [....] Name Signature Title Date of Issue Version

1.8.3. Distribution Distribution # [....] Name Title Date of issue Version Distribution # [....] Name Title Date of issue Version

2. Overview

2.1. Purpose

2.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.

2.2. Contents

2.2.1. The Highlight Report should cover the following topics.

2.2.2. Status Summary

2.2.3. This Reporting Period

2.2.4. Next Reporting Period

2.2.5. Project and Stage Tolerance Status

2.2.6. Requests for Change

2.2.7. Key Issues and Risks

2.2.8. Lessons Report (if appropriate)

2.3. Advice

2.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

2.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.

2.3.3. The following quality criteria should be observed: The level and frequency of progress reporting required by the Project Board is right for the stage and/or project The Project Manager provides the Highlight Report at the frequency, and with the content, required by the Project Board The information is timely, useful, accurate and objective The report highlights any potential problem areas.

3. How to use this template

3.1. How to share this template with your team

3.1.1. Send an email 1. Click Share this map 2. Select Invite People 3. Write a message 4. Click Invite

3.1.2. Send a link 1. Click Share this map 2. Tick Link to share 3. Copy the link to share it

3.1.3. Export 1. Click down arrow, bottom right 2. Select the export option you want

3.2. How to complete this template

3.2.1. Complete the sections in square brackets [....]

3.2.2. Read these sections for help on this template Purpose Advice

3.2.3. Navigate using the links in Contents Contents

3.3. Attribution

3.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

3.4. Get this template here

4. This Report

4.1. Date of Highlight Report

4.1.1. [...]

4.2. Period Covered

4.2.1. [...]

5. Status Summary

5.1. [Give an overview of the status of the stage at this time]

6. This Reporting Period

6.1. Work Packages

6.1.1. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.1.2. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.1.3. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.1.4. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.1.5. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.1.6. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.1.7. [Work Package Ref] [Work Package Name] [Status] [Notes]

6.2. Products

6.2.1. [Product Ref] [Product name] [Status] [Notes]

6.2.2. [Product Ref] [Product name] [Status] [Notes]

6.2.3. [Product Ref] [Product name] [Status] [Notes]

6.2.4. [Product Ref] [Product name] [Status] [Notes]

6.2.5. [Product Ref] [Product name] [Status] [Notes]

6.2.6. [Product Ref] [Product name] [Status] [Notes]

6.2.7. [Product Ref] [Product name] [Status] [Notes]

6.3. Corrective Actions Undertaken

6.3.1. [Enter Corrective Actions taken during the period]

7. Next Reporting Period

7.1. Work Packages

7.1.1. [Work Package Ref] [Work Package Name] [Status] [Notes]

7.1.2. [Work Package Ref] [Work Package Name] [Status] [Notes]

7.1.3. [Work Package Ref] [Work Package Name] [Status] [Notes]

7.1.4. [Work Package Ref] [Work Package Name] [Status] [Notes]

7.1.5. [Work Package Ref] [Work Package Name] [Status] [Notes]

7.2. Products to be completed

7.2.1. [Product Ref] [Product name] [Notes]

7.2.2. [Product Ref] [Product name] [Notes]

7.2.3. [Product Ref] [Product name] [Notes]

7.2.4. [Product Ref] [Product name] [Notes]

7.2.5. [Product Ref] [Product name] [Notes]

7.2.6. [Product Ref] [Product name] [Notes]

7.3. Corrective Actions

7.3.1. [Enter Corrective Actions to be completed during the next period]

8. Project and Stage Tolerance Status

8.1. [Report how execution of the project and stage are performing against its tolerances (e.g. cost/time/scope actuals and forecast)]

9. Requests for Change

9.1. [Identify any changes raised, approved/rejected and pending]

10. Key Issues and Risks

10.1. [Summarise actual or potential problems and risks]

11. Lessons Report (if appropriate)

11.1. [Provide a review of what went well, what went badly, and give any recommendations for corporate or programme management consideration]