END PROJECT REPORT v2.0

[YOUR LOGO HERE]
END PROJECT REPORT
Project:
Draft 
Final

Author:
Owner:
Client:
Document Number:
Location:
[Type the path to this document]
Revision:
Version
Number
Revision date
Previous
revision date
Summary of Changes
Changes marked
Approvals:
Name
Signature
Title
Date of Issue
Version
Distribution List:
Name
Title
Date of
Issue
Version
Quality Checked by:
1
[Date]
[Version]
[YOUR LOGO HERE]
END PROJECT REPORT
PURPOSE:
This report is used during project closure to review how the project performed against the version of the
Project Initiation Documentation used to authorize it. It also allows the passing on of any lessons that can
be usefully applied to other projects and details of unfinished word, ongoing risks or potential product
modifications to the group charged with future support of the project’s products in their operational life.
The template contains guidance for its completion. This purpose section and the guidance for each entry
should be deleted when used.
Table of Contents:
Page:
This plan contains the following entries for each interested party
1
Project Manager’s report
2
Business Case review
3
Project’s objectives review
4
Team performance review
5
Products review
6
Lessons report
1. Project Manager’s report:
Summarise the project’s performance.
2. Business Case review:
Sumamrise the validity of the project’s Business Case:
 Benefits achieved to date
 Residual benefits expected (post-proejct)
 Expected net benefits
 Deviations from the approved Business Case
3. Project’s objectives review:
Review of how the project performed against its planned targets and tolerances for time, cost, quality, scope,
benefits and risks. Review the effectiveness of the project’s strategies and controls.
4. Team performance review:
In particular, providing recognition for good performance.
2
[Date]
[Version]
[YOUR LOGO HERE]
END PROJECT REPORT
5. Products review:





Quality records – listing the quality activities planned and completed
Approval records - lisitng the products and their requisite approvals
Off-specifications – listing any missing products or products that do not meet the origianl requirements,
and confirmation of any concessions granted
Project product handover – confirmation (in the form of acceptance records) by the customer that
operations and maintenance functions are ready to receive the project’s products
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 risks
and issues, and any other activities needed to take the products to the next phase of their life
6. Lessons report:
A review of what went well, what went badly, and any recommendations for corporate or programme management
consideration (and if the project was prematurely closed, then the reasons should be explained).
3
[Date]
[Version]