The document provides a template for a project closure report with instructions for completing sections on the executive summary, stakeholder feedback, project performance outcomes, closure checklist, and approvals. It records final sign-off from the project sponsor and assesses success based on criteria in the project charter. Key information includes lessons learned, handing off deliverables and documentation, releasing project resources, and identifying any future related work.

1. Author:[Type the authorname]
Last Updated:November27,2014
Project Closure Report
[Insert Project Name]

2. ProjectClosureReport – [InsertProjectName]
Page | 1
File Location:[optiontoenterfile storage location]
Purpose of Project Closure Report
The project closure report is the final project management deliverable for a project and is used for senior management to assess the success of the project. The closure report
records the final project sign off from the Sponsor, assesses success, and initiates a number of activities: identifyand share best practices for future projects, identifyand assign
items to be addressed (issues, future initiatives, future projects), appropriately close current contracts, provide final project communication to stakeholders, release project
resources, and ensure appropriate operational transition. The closure report is part of the Portfolio Management Group’s closure process.
Project Closure Report Participants and Approvers
Input into the project closure report may come from many different sources including project documentation, and feedbackfrom stakeholders and those who participated on the
project according to the defined project roles in the project charter. Project documentation that should be referenced includes but is not limited to the project charter (scope,
objectives and success criteria), project management plan, risks, issues, approved changes to the project, stakeholder register, contracts and statements of work, and lessons
learned. Feedbackcan be in the form of group meetings, interviews and surveys. An impartial third party resource may be used to assist with project performance evaluation.
PMO resources are available to facilitate lessons learned and the closure process.
The author is the Project Manager. The approver of the project closure report is the Sponsor. An approved closure represents final sign off on the project, the final deliverable,
and agreement on project successes and improvement opportunities. It also represents the sponsor’s agreement that the closure content is accurate and ready to be shared.
Instructions
1. Review project information by reading documentation (such as charter, risks, issues, lessons learned, contracts and statements of work, stakeholder register, deliverable
documentation, approved changes).
2. Contact PMO to conduct satisfaction survey. Collect and document lessons learned.
3. Assess success of project based on the success criteria outlined in the charter and project management plan. Perform required measurements for success criteria.
4. Create the project closure report based on information from steps 1-4. The green italic text contains instructions for filling out the template and can be removed for the
final version of the document.
5. Review closure report with applicable stakeholders and sponsor for accuracy and completeness, if required.
6. Obtain appropriate approval for project closure to indicate agreement by the Sponsor.
7. Upload closure report to the Project Artifacts Library.
8. Share lessons learned with other Project Managers.
Next Steps
Once the project closure has been approved, the project is closed. Lessons learned should be shared with others. Schedule a closure meeting with PMG Management.

3. ProjectClosureReport – [InsertProjectName]
Page | 2
File Location:[optiontoenterfile storage location]
Executive Summary
This section shouldincludea brief overviewof theproject,highlight key projectperformanceratingsandhighlights,summarizethekey lessons
learned,andnextsteps or remainingactions.
[InsertExecutive Summary]
Stakeholder Feedback
Process
This section shouldincludea descriptionof howfeedbackwas/isbeing collected forlessonslearned, who feedbackwascollectedfrom(if specific
groupswerenottargetedfor feedbackthey shouldbementionedaswell with a reasonwhy they wereexcluded), and themeasuresagainst
successcriteria (includingstakeholdersatisfaction).
[Insertsummaryof feedbackprocess]
Feedback Results
Includethe results of the stakeholderfeedback,includingkey (1or 2) themes, key (1-3) thingsthatwere donewell, key (1-3) opportunitiesfor
improvementforthefuture,andnextsteps. This informationshouldbesummarizedfromtheclosuresurvey, lessonslearnedreport,andsuccess
criteria measurements.
[insertfeedbackresults]
Project Performance Outcome
This section should documenttheoutcomeof theprojectby comparingtheoutcometothe successcriteria statedin the charter(orthe approved
changed successcriteria documentedinthe ProjectManagementPlan) and explainany variances.Successisbaseduponwhethertheproject

4. ProjectClosureReport – [InsertProjectName]
Page | 3
File Location:[optiontoenterfile storage location]
delivered whatwasaskedfor,whetherthereare benefitsto whatwasdelivered,andthe processtoget there. If successcriteria haven’tbeen
defined up frontforthe project,the PMO is availablefor guidance.
In thechart below,recordthe successcriteria (fromprojectmanagementplan),expected results (fromprojectmanagementplan),actualresults,
variance& explanation,andaratingindicatinghowwell the successfor eachcategory wasmet/notmet. The measurementsfordeterminingthe
actualresults will be documentedinthecharter or projectmanagementplan. Theratingshouldbea collaborativeagreementbetweenthe
ProjectManagerandSponsor,atminimum,andmay also includefeedbackfromprojectgovernance,theprojectteam,andotherstakeholders
fromthe closuresurvey andotherdiscussions.
Category Performance
Success of
Product/
Service
Did the
product/
service deliver
what was
asked for,
relevant to
constraints
such as scope
(requirements,
functionality,
et cetera), and
quality?
Criteria ExpectedResult(s) Actual Result(s) Variance & Explanation Action(s) to address
variances (ifapplicable)
Overall Success of Product/Service (clickone checkboxbelow):
☐All ExpectationsWere Metand/orExceeded
☐Notall ExpectationsWere Met,ButStill MayBe (explainhow,who, andwhenbelow)
☐Some ExpectationsWillNotBe Met (explainimpactbelow)
☐DidNotMeetAnyExpectations
Comments(if applicable):
Success of
Outcome
Did the
product/
service
delivered
Criteria ExpectedResult(s) Actual Result(s) Variance & Explanation Action(s) to address
variances (ifapplicable)

5. ProjectClosureReport – [InsertProjectName]
Page | 4
File Location:[optiontoenterfile storage location]
provide benefit
to people using
it, and/or to
the business?
Overall Success of Outcome (click one checkboxbelow):
☐All ExpectationsWere Metand/orExceeded
☐Notall ExpectationsWere Met,ButStill MayBe (explainhow,who, andwhenbelow)
☐Some ExpectationsWillNotBe Met (explainimpactbelow)
☐DidNotMeetAnyExpectations
Comments(if applicable):
Success of
Process
Did the process
followed to
deliver the
product/
service work
well?
(management
of resources,
budget,
schedule,
project team,
change,
communicatio
n, transition to
operations,
procurement,
et cetera)
Criteria ExpectedResult(s) Actual Result(s) Variance & Explanation Action(s) to address
Variances (ifapplicable)
Overall Success of Process(clickone checkboxbelow):
☐All ExpectationsWere Metand/orExceeded
☐Notall ExpectationsWere Met,ButStill MayBe (explainhow,who, andwhenbelow)
☐Some ExpectationsWillNotBe Met (explainimpactbelow)
☐DidNotMeetAnyExpectations
Comments(if applicable):

6. ProjectClosureReport – [InsertProjectName]
Page | 5
File Location:[optiontoenterfile storage location]
Closure Checklist
This section includesa checklist of thingsthat shouldbedoneduring projectclosure,andincludes any notesthat may needto becarried through
transition to operations. Marktheseitemsas complete/notcompletewithan‘x’ (or N/A if notrelevantfor theproject) andaddany relevant
commentsbeforethesponsorapprovesthisclosurereport
Yes No N/A Comments
Are all deliverablescompletedand
transitionedtooperations?
Has deliverable documentationbeenhanded
overto stakeholdersandOperations?
Have all contracts beenclosed?
Have all payments(invoices,etcetera) been
made?
Has adequate knowledge transferandtraining
beencompleted?
Are there recurringmaintenance/operational
costs forthe productto be accountedfor? If
yes,indicate whatandwhoisresponsible in
the Comments.
Are there recommendedenhancementsor
updatesstill required? If yes,adddetailsin
the Comments.
Have all tasks beencompleted? If no,add
detailsinthe Comments.
Have any remainingissuesbeen
communicatedtooperations? Adddetailsof
any suchissuesinComments.

7. ProjectClosureReport – [InsertProjectName]
Page | 6
File Location:[optiontoenterfile storage location]
Yes No N/A Comments
Have any remainingrisksbeencommunicated
to operations? Adddetailsof anysuchrisksin
Comments.
Were stakeholdersprovidedwithan
opportunitytoprovide feedbackaboutthe
deliverablesandtheirsatisfaction?
Has the closure beencommunicatedtoall
stakeholders?
Has documentationbeenarchivedin the
appropriate repository?
Has team memberperformancebeen
communicatedtotheirfunctional managers,
where requested?
Has there beenappreciationexpressedtothe
projectteam,including anyrelevant
celebrations?
Have lessonslearnedbeencollectedand
completedbystakeholders?
If lessonslearnedhave beencollectedand
completed,have theybeenarchived
appropriatelyinarepositoryorknowledge
base?
Have projectteam membersbeenreleased
fromthe projector re-allocated?
Are there future recommendedprojectsor
initiativesrelatedtothisone? If yes,please
include detailsinComments,including
referencestoadditional documentation.

8. ProjectClosureReport – [InsertProjectName]
Page | 7
File Location:[optiontoenterfile storage location]
Yes No N/A Comments
Are there outstandingproject outcome
measurementsthatneedtobe done inthe
future andtransitionedtooperations? If yes,
include detailsof measure,timingandwhois
responsible inComments.
Have you had a closure meetingwiththe
PortfolioManagementGroup?
If the deliverablecreatesanewservice,or
impactsan existingservices,hasthe service
catalogue beenupdated?

9. ProjectClosureReport – [InsertProjectName]
Page | 8
File Location:[optiontoenterfile storage location]
Approvals
Thisreportformally closesthe [insertprojectname] project,basedonthe completionof deliverablesandassessmentof projectperformance
outlined.Thisapproval representsacceptance of the final deliverable basedonthe informationinthisreport,andreleasesall resourcesfrom
thisproject(financial andFTE). The closure performance ratingswillbe recordedinthe ITprojectportfolio,andrelevant information,suchas
opportunitiesforimprovement,maybe sharedwithotherprojects.
SponsorAuthorization: [printname of sponsor,title here]
___________________________________________________________________
Signature: _______________________________________ Date: ________________
ProjectManager Authorization: [printProjectManagername here]
___________________________________________________________________
Signature: _______________________________________ Date: ________________
RevisionHistory
Change Made By Date Change
Made
Detailsof Change Change
Reviewed/
Approvedby
Date change
reviewed/approved