Endprojectreport

HOW TO USE THIS TEMPLATE:
Introduction
The template reflects the steps set out in the PRINCE2 Method and is
designed to prompt the Project Manager and help in the creation of the End
Project Report. There is also a Product Description for the End Project Report
at Appendix A of the PRINCE2 Manual.
Loading the file
This template has been produced using Microsoft Word 2003. To use it, load
up the file directly from the directory and starting from page 1 follow the
prompts (in [...] brackets).
Deleting the [....] text
When the template is complete, the End Project Report can be printed and
approved.
Prior to printing, you should delete all [....] prompt text.
Saving the End Project Report under its own name
Save the End Project Report by selecting the “SAVE-AS” command; this will
avoid overwriting the standard template. You must specify your own Project
Directory.
Once your End Project Report is complete check the document against
the following Quality Criteria:
 Any abnormal situations are described, together with their impact
 At the end of the project, all Issues should either be closed or be the
subject of a follow-on action recommendation
 Any available useful documentation or evidence should accompany the

follow-on action recommendation(s)
 Any appointed Project Assurance roles should agree with the report
PROJECT DOCUMENTATION
END PROJECT REPORT
Project:
Release:
Date:
PRINCE2
Author:
Owner:
Client:
Document Ref:
Version No:
Insert Project Name
End Project Report
Date: 22 June 2024
Page 2
Insert Project Name
End Project Report
Date: 22 June 2024
1 End Project Report History
1.1 Document Location

This document is only valid on the day it was printed.
The source of the document will be found at this location – [insert folder structure]
1.2 Revision History

Date of this revision:
Date of next revision:
Revision Previous Summary of Changes Changes marked

date revision
date
First issue
1.3 Approvals
This document requires the following approvals.
Signed approval forms should be filed appropriately in the project filing system.
Name Signature Title Date of Version

Issue
1.4 Distribution
This document has been distributed to:
Name Title Date of Version

Issue
Page 3
Insert Project Name
End Project Report
Date: 22 June 2024
2 Table of Contents
Page
1 End Project Report History 1

1.1 Document Location 1
1.2 Revision History
1.3 Approvals
1.4 Distribution
2 Table of Contents
3 Project Manager’s Report
4 Review of the Business Case
5 Review of Project Objectives
6 Review of Team Performance
7 Review of Products
8 Lessons Report
Page 4
Insert Project Name
End Project Report
Date: 22 June 2024
3 Project Manager’s Report

[A summary of the project’s performance]
4 Review of the Business Case

[Summarising the validity of the project’s Business Case:
- Benefits achieved to date
- Residual benefits expected (post-project)
- Expected net benefits
- Deviations from the approved Business Case]
5 Review of Project’s Objectives

[A review of how the project performed against its planned targets and tolerances for
time, cost, quality, scope, benefits and risk. Review the effectiveness of the project’s
strategies and controls]
6 Review of Team Performance

[In particular, providing recognition for good performance]
7 Review of Products
- Quality records Listing the quality activities planned and completed
- Approval records Listing the products and their requisite approvals
- Off-specifications Listing any missing products or products that do not meet

the original requirements, and confirmation of any concessions granted
- Project product handover Confirmation by the customer that operations and

maintenance functions are ready to receive the project product
- Summary of follow-on action recommendations Request for Project Board

advice about who should receive each recommended action. The
recommended actions are related to unfinished work, ongoing issues and
risks, and any other activities needed to take the products to the next phase of
their life
Page 5
Insert Project Name
End Project Report
Date: 22 June 2024
8 Lessons Report
[A review of what went well, what went badly, and any recommendations for corporate or
programme management consideration (if the project was prematurely closed, then the
reasons should be explained)]
Page 6

Endprojectreport

Uploaded by

Copyright:

Available Formats

Endprojectreport

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Endprojectreport

Uploaded by

Copyright:

Available Formats

HOW TO USE THIS TEMPLATE:

Loading the file

Deleting the [....] text

Prior to printing, you should delete all [....] prompt text.

Saving the End Project Report under its own name

 Any abnormal situations are described, together with their impact

 Any available useful documentation or evidence should accompany the

END PROJECT REPORT

1 End Project Report History

1.1 Document Location

1.2 Revision History

Revision Previous Summary of Changes Changes marked

Name Signature Title Date of Version

Name Title Date of Version

1 End Project Report History 1

3 Project Manager’s Report

4 Review of the Business Case

5 Review of Project Objectives

6 Review of Team Performance

3 Project Manager’s Report

4 Review of the Business Case

- Benefits achieved to date

- Residual benefits expected (post-project)

- Expected net benefits

- Deviations from the approved Business Case]

5 Review of Project’s Objectives

6 Review of Team Performance

- Approval records Listing the products and their requisite approvals

- Off-specifications Listing any missing products or products that do not meet

- Project product handover Confirmation by the customer that operations and

- Summary of follow-on action recommendations Request for Project Board

You might also like