PROGRAM & PORTFOLIO MANAGEMENT OFFICE (PPMO)
<PROJECT> CLOSURE REPORT
<Project Name> Closure Report
Project Manager
1.
<fill in>
<fill in>
First Name
e-mail
Last Name
<fill in>
Phone
<fill in>
DOCUMENT CONTROL
File Path: S:\ITS\Shared\Projects\PPMO\Projects\<fill in>
Version Control
Version
Number
v1
v2
v3
v4
Issue Date
<fill in>
<fill in>
<fill in>
<fill in>
Description, Reasons, Comments, Approvals
Initial draft
<fill in>
<fill in>
<fill in>
Note For standard sections of the Project Closure Report template that have been excluded from the
present document, the section headings have been moved to the Project Closure Report Sections Omitted
list at the end.
2.
PURPOSE OF REPORT
<Replace this text with your own statement of purpose, or use the following sample.>
The Project Closure Report is the final document produced for the project and is used by senior
management to assess the success of the project, identify best practices for future projects, resolve all
open issues, and formally close the project.
3.
GOALS OF REPORT
<Replace this text with your own statement of goals, or use the following sample.>
This Project Closure Report is created to accomplish the following goals:




4.
Review and validate the milestones and success of the project.
Confirm outstanding issues, risks, and recommendations.
Outline tasks and activities required to close the project.
Identify project highlights and best practices for future projects.
SUMMARY
4.1
Project Background Overview
<Replace this text with a brief description of the project background.
 What were the original goals, objectives, and success criteria?
 Refer to project overview statement and/or project charter for this information.>
4.2
Highlights and Best Practices
Project Highlights:

The University of North Carolina at Charlotte
Data Classification:
INTERNAL
<creation date>
Page 1 of 4
PROGRAM & PORTFOLIO MANAGEMENT OFFICE (PPMO)
<PROJECT> CLOSURE REPORT
Best Practices:

4.3
Closure Synopsis
<Replace this text with a brief description of why the project is being closed.
Is it being closed because all project objectives and deliverables have been met?
Or is it being closed for other reasons (loss of funding, shift in strategy, etc.)?>
5.
PROJECT METRICS PERFORMANCE
5.1
Goals and Objectives Performance
<Replace this text with a comparison of the actual project’s performance to goals and objectives>
5.2
Critical Success Factors
Performance Compared to Critical Success Factors
Evaluation *
CSF from Scope Statement
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
* Answer the following questions for each Criterion:
 To what level of success was criterion achieved?
 If not achieved? Why not? When (if ever) will it be achieved?
 Who is responsible for measuring continued progress toward achievement?
5.3
Milestones and Deliverables Performance
Schedule Control
Target
Date
Actual
Date
Milestone / Deliverable
Performance Evaluation *
<fill in>
<fill in> <fill in>
<fill in>
<fill in>
<fill in> <fill in>
<fill in>
<fill in>
<fill in> <fill in>
<fill in>
<fill in>
<fill in> <fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
<fill in>
* Was deliverable produced on time at acceptable quality? If not, why not? Is achievement anticipated
at a later date?
5.4
Schedule Performance Factors
5.4.1 Schedule Overview (Key dates: e.g. IT Governance 1st submittal, IT Governance approval /
PM appointed, Planning complete, Execution began & ended, Final acceptance)
The University of North Carolina at Charlotte
Data Classification:
INTERNAL
<creation date>
Page 2 of 4
PROGRAM & PORTFOLIO MANAGEMENT OFFICE (PPMO)
<PROJECT> CLOSURE REPORT

5.4.2 Schedule Control Process (briefly describe baseline schedule control process – see Lessons
Learned for evaluation)

5.4.3
Corrective Actions (briefly describe changes or interruptions to baseline schedule)

5.4.4 Schedule Integration with Project Management (briefly describe how Schedule Control
integrated with overall project management)

5.5
Budget Performance Factors
5.5.1
Budget Overview (Key subtotals of major categories of expenses)

5.5.2
Corrective Actions (briefly describe changes to baseline budget)

5.6
Recommendations for Future Performance Metrics (briefly describe suggestions for
more appropriate metrics and comment on those used that did not prove effective in
contributing to project success)

6.
PROJECT CLOSURE TASKS
6.1
Resource Management (highlight remaining steps to document project knowledge
(intellectual property, documents developed by individuals required for archives, etc.) and
how to handle release of resources)

6.2
Issue Management – do not attempt to close project until Sponsor has accepted all
deliverables or signed-off on reductions in Scope and other issue resolution.
6.3
Risk Management – do not attempt to close project until all risks have been
resolved or Sponsor has signed-off on accepting those risks and releasing ITS from future
commitments, involvement or risk responses.
The University of North Carolina at Charlotte
Data Classification:
INTERNAL
<creation date>
Page 3 of 4
PROGRAM & PORTFOLIO MANAGEMENT OFFICE (PPMO)
<PROJECT> CLOSURE REPORT
6.4
Quality Management (describe at a high level, how quality management processes
contributed to the project’s success, through quality assurance efforts monitoring the steps
to produce deliverables)

6.5
Communications Management (describe the highlights of successes and failures of
the communications management efforts)

6.6
Customer Expectations Management (describe the highlights of efforts to manage
the Sponsor’s and other stakeholders’ expectations. Did they vary during the project? If
so, how were these variations documented and related to the Scope baseline?)

6.7
Asset Management (describe any steps to return assets to other uses, disposal,
decommissioning, etc.)

6.8
Lessons Learned (See separate documentation – no need to repeat here)
6.9
Post-Project Tasks (list any efforts remaining to officially close the project and
indicate the responsible person with a due date for final reporting that the action was
completed)

6.10 Project Closure Recommendations (list steps to achieve Sponsor Final Acceptance,
documentation of successfully meeting Critical Success Factors, archiving documentation,
project celebration, etc.)

7.
PROJECT CLOSURE REPORT APPROVALS
Acceptance of Project Deliverables & Project Closure
Role
Name
Project Sponsor
<fill in>
Business / Service
Owner
<fill in>
PPMO
<fill in>
Project Manager
<fill in>
The University of North Carolina at Charlotte
Signature
_________________________
_________________________
_________________________
_________________________
Data Classification:
INTERNAL
Date
____/____/____
____/____/____
____/____/____
____/____/____
<creation date>
Page 4 of 4