Professional Documents
Culture Documents
Project Closure Document For: Roject AME
Project Closure Document For: Roject AME
Author:
Project Number:
Release Date:
Business Sponsor:
Page 1 of 8
Project Closure Document
TABLE OF CONTENTS
1. Instructions.....................................................................................................................................3
1.1. Purpose 3
1.2. Methodology 3
1.3. Procedure 3
2. Version History...............................................................................................................................4
5. Project Performance......................................................................................................................5
5.1. Project Objectives 6
5.2. Project Milestones & Deliverables 6
5.3. Project Schedule Performance 6
5.4. Project Budget Performance 6
5.5. Customer Satisfaction 6
Page 2 of 8
Project Closure Document
1. Instructions
This section provides instructions for how to complete this form. You may delete the entire page(s) from the final version.
1.1. Purpose
The purpose of this document is to close off and evaluate a project that is coming to/has ended.
The detail that is contained here will depend on the project, but should be sufficient to allow project closure.
1.2. Methodology
The content of this report should be obtained from all of or a combination of the following project resources:
1.3. Procedure
Once the project closure document is completed, the document should be sent out for review. A minimum review team
should be the project team (including the Users) plus stakeholders.
The stakeholders and the Sponsor, Business Liaison and project manager must sign-off the Project Closure document.
The objectives and project schedule must now be reviewed to identify any significant changes to the original baseline.
Inform all stakeholders of the location of the Project Closure document in this communication.
Page 3 of 8
Project Closure Document
2. Version History
Page 4 of 8
Project Closure Document
Provide a brief description of the project. List the main points the summary will cover in the same order as they appear in
the main report;
Purpose
Message
Key Recommendations
Add any supporting or explanatory sentences as needed, avoiding unnecessary technical material or jargon
Examples;
Other Reason:
5. Project Performance
For further guidance or larger projects refer to Post Implementation Review;
http://eudocs/sites/operations/change_management/Shared%20Documents/Process/toolkit/Templates/new_project_dir_with
%20templates/7_review/Post%20Implementation%20Review%20V2.ppt
http://eudocs/sites/operations/change_management/Shared%20Documents/Process/toolkit/Templates/new_project_dir_with
%20templates/7_review/PIR%20Template%20V1.ppt
Page 5 of 8
Project Closure Document
5.1. Project Objectives
How satisfied were the stakeholders and end users with the project?
Where stakeholders and end users were not satisfied, provide details of how this was managed?
Complete the table of any issues or risks outstanding at the end of the project. Provide the mitigation and/or contingency
plan for resolving the issue and assign responsibility to each.
Note: There should be no go live critical issues listed as project should not have gone live with critical issues outstanding
Page 6 of 8
Project Closure Document
Page 7 of 8
Project Closure Document
List the Project Working Group & Key Resources on the project.
Provide dates when they are rolling off the project.
Capture;
Page 8 of 8