Highlight Report Template - FMD Web viewPROGRAMME NAME. HIGHLIGHT REPORT TEMPLATE. Project Title. Release Status: DRAFT, REVIEW, FOR INFORMATION or FINAL

PROGRAMME NAME

HIGHLIGHT REPORT TEMPLATE

Project Title

Release Status: DRAFT, REVIEW, FOR INFORMATION or FINAL

Author: Insert Name

Date: 01 January 2016

Filename & Version: Insert details

Project ID: Insert ID

Methodology: PRINCE2™ 2009

FMD Consultants Limited assumes no responsibility for the usage of any information contained in this document and the way it is handled and disclaims all liability in respect of such information and its provision. Subject to this disclaimer, you may copy and utilise the material contained in the document.

This information is based on OGC PRINCE2™ material. PRINCE2™ is a registered trade mark of the Office of Government Commerce in the United Kingdom and other countries. All registered trademarks recognised & accepted.

Author, 01/03/-1,

General Guidelines:This document provides a template for the creation of a Prince2 Highlight Report conforming to the Office of Government Commerce (OGC) guidelines.Each section has comments which give guidance on the structure, content or options for that section. Whilst the comments reflect the OGC guidance, additional information in the form of examples, suggestions for content and areas for consideration have been provided.Comments can be managed via the ‘Review’ tab within MS Word. All comments can be displayed in a reviewing pane (horizontal or vertical) by clicking on the Reviewing Pane icon within the Review Tab. Individual comments or all comments can be deleted via the Delete icon in the Comments box on the Review Tab.The Highlight Report can be printed without comments by selecting the “Print what” dropdown on the Print screen and choosing “Document” rather than “Document showing markup”.It may be appropriate to delete all guideline comments before the Highlight Report is circulated for review, at which point reviewers will add their own review comments.Note: some organisations see the Highlight Report as a simple snapshot of project status and as such, may produce reports without pages 1 to 3 of this template, omitting the banner page, document history and index,. The snapshot report may commence with a simple heading followed by report date and the balance of this template contents.

1 Document History1.1 LocationThis document is stored in the following location:

Filename

Location

1.2 Revision HistoryThis document has been through the following revisions:

Version No.

Revision Date

Filename/Location stored:

Brief Summary of Changes

1.3 AuthorisationThis document requires the following approvals:

AUTHORISATION Name Signature Date

Project Manager

1.4 DistributionThis document has been distributed to:

Name Title Version Issued Date of Issue

1.5 Related Documents Summary of filenames and locations of related documents:

Document Type Filename/Location stored:

Project Mandate

Project Brief

Project ID: Doc Ref:

HIGHLIGHT REPORT TEMPLATE Page 2 of 7 Date of Issue:

2 Contents

1 DOCUMENT HISTORY..................................................................................................2

1.1 LOCATION....................................................................................................................21.2 REVISION HISTORY.........................................................................................................21.3 AUTHORISATION............................................................................................................21.4 DISTRIBUTION...............................................................................................................21.5 RELATED DOCUMENTS....................................................................................................2

2 CONTENTS..................................................................................................................3

3 DATE...........................................................................................................................4

4 REPORTING PERIOD....................................................................................................4

5 STATUS SUMMARY.....................................................................................................4

6 THIS REPORTING PERIOD............................................................................................4

7 NEXT REPORTING PERIOD...........................................................................................5

8 PROJECT AND STAGE TOLERANCE STATUS...................................................................5

9 REQUESTS FOR CHANGE..............................................................................................5

11 KEY ISSUES AND RISKS.............................................................................................6

12 LESSONS IDENTIFIED...............................................................................................6

13 SUPPORTING INFORMATION...................................................................................6



3 Date

4 Reporting Period

5 Status SummaryProject Status Last

Period

This Perio

d

Comments

Overall Project Status

R R

Time A ACost G GScope G GQuality G GBenefit G GRisk G G

Stage Status Last Period

This Perio

d

Comments

Overall Stage Status

G G

Time G GCost G GScope G GQuality G GBenefit G GRisk G G

6 This Reporting PeriodWork Package Name

Status Baseline Date

Forecast Date

Pending authorizationIn executionCompleted

Product Name Status Baseline Date

Forecast Date

Not startedIn developmentIn reviewApprovedHanded over



Author, 03/01/-1,

This Reporting Period:Baseline dates are from Stage Plan. Forecast date shows any variance.Work PackagesThe status of all work packages within the current reporting period.Pending authorisation are those work packages which do not have agreement to proceed e.g. may be dependant on previous uncompleted work or awaiting confirmation of regulatory changes.In execution are those under development at the reporting date.Completed are those completed and accepted as meeting functional and quality requirements.ProductsThe status of all products (deliverables) scheduled or in progress for this reporting period.Corrective ActionsChanges to the project need to be made in a considered and rational way. In taking corrective action, the objective is to select and, within the limits of the stage and project tolerances, implement actions that will resolve deviations from the plan.This corrective action is usually carried out with the approval of the Project Board and all actions should be detailed.

Author, 03/01/-1,

Status Summary:An overview of the status of the project to date and the stage at the reporting date. Last period and this period summaries should be filled to give an immediate visual image of status:RED - forecast that tolerances will be exceededAMBER - forecast that tolerances are in jeopardy due to risks and issues identifiedGREEN - forecast that tolerances will not be exceededComment fields are used to provide the Project Board and other interested parties with relevant information.

Author, 03/01/-1,

Reporting Period:The period this Highlight Report covers i.e. from the publication date of the last Highlight Report or from the initiation date of the project if there has not been a previous Highlight Report.

Author, 03/01/-1,

Date:The date the Highlight Report was published.

Summary of corrective action taken during the period

7 Next Reporting PeriodWork Package Name

Status Baseline Date

Forecast Date

Pending authorizationIn executionCompleted

Product Name Status Baseline Date

Forecast Date

Not startedIn developmentIn reviewApprovedHanded over

Summary of corrective action taken during the period

8 Project and Stage Tolerance StatusTolerance

Element

Actual Forecast Variance

Project TimeCostBenefitsScopeQualityRisks

Stage TimeCost



Author, 03/01/-1,

Project and Stage Tolerance Status:How the project is performing against their tolerances e.g. time actuals, forecast time and the variance percentage.

Author, 03/01/-1,

Next Reporting Period:Work PackagesThe expected status of all work packages within the next reporting period.ProductsThe status of all products (deliverables) to be produced within the next reporting period.Corrective ActionsSummary of corrective actions expected to be carried out in the next reporting period.

9 Requests for ChangeRef Description and update Status

RaisedApprovedRejectedPending

10



11 Key Issues and RisksRef Item Description and update

Problem or concernOff-specificationRiskRequest for Change

12 Lessons IdentifiedLesson Type

Lesson Detail Logged By

CorporateProgrammeProject

13 Supporting Information



Author, 03/01/-1,

Supporting Information:Optional section, add any supporting information, such as comments, charts, tables, documents or diagrams that will assist in improving understanding of the Highlight Report.

Author, 03/01/-1,

Lessons Identified:A review of what went well, what went badly, and any recommendations for corporate, programme or project management consideration.

Author, 03/01/-1,

Key Issues and Risks:Summary of actual or potential problems and risks which may impact the project along with a high-level summary of any corrective actions taken to minimise the risk.Problem or ConcernA type of issue (other than request for change or off-specification) that the Project Manager needs to resolve or escalate.Off-specificationSomething that should be provided by the project but which currently is not (or forecast not to be) provided e.g. missing product or product not meeting its specification.RiskAn uncertain event or set of events that, should it occur, will have an effect on the achievement of the objectives. Measured by probability of risk occurring magnified by the magnitude of its impact on objectives.Request for Change (RFC)A proposal for a change to a baseline.