Scribd
Upload
31 views3 pages

Project Closure Template

The project closure document formally closes a project and transfers responsibilities to operations. It summarizes the project name and details, scope, accomplishments including delivering on objectives, final project milestones and budgets, lessons learned, and acceptance from leadership marking the official end of the project.

Uploaded by

Vinit Kant Majumdar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views3 pages

Project Closure Template

The project closure document formally closes a project and transfers responsibilities to operations. It summarizes the project name and details, scope, accomplishments including delivering on objectives, final project milestones and budgets, lessons learned, and acceptance from leadership marking the official end of the project.

Uploaded by

Vinit Kant Majumdar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Project Closure Document

Project Name:

Business Unit(s):

Client:

Executive Sponsor:

Project Manager:

Date:

Related Project#: (Future Use. Remove if not needed)

Purpose: The purpose of the Project Closure document is to formally close a project and authorize the
handoff from project to operations. It would include final information about the project deliverables, scope,
milestones and budget, as well as lessons learned.

1. Project Description
(Insert the basic description of the project – often from the initial charter document.)

2. Scope Statement
(Insert the scope of the project here as a reference to what was accomplished.)

3. Project Accomplishments
(From the Charter, insert the intended goal and objectives. If the project was on track, you can talk about
these items now as what the project was able to accomplish. If any of these items changed, you should
address why and how.)

1.1. (Accomplishment 1)
1.1.1. (Details)
1.1.2. (Details)

1
2. Project Milestones

Milestone Target Date Completed Date

3. Financial Summary

Project Costs Project Budget Project Actuals

Hardware

Software

Installation Services

Other

Project Totals

Notes:

On-going (Annual) Costs Project Budget Project Actuals

Salaries

Benefits

Maintenance (Software & Hardware)

Depreciation of Hardware

External Vendor Services

Other

On-going Totals

Notes:

2
4. Transfer to Operations
(Describe the handoff of ongoing tasks to operations, including identifying operational roles.)

1.1. (Task 1)
1.1.1. (Detail)
1.1.2. (Detail)

Role Name Transition Date

Functional Owner

Service Owner

Service Manager

5. Lessons Learned
(Transfer a bulleted list of lessons learned from your team or give a narrative synopsis of the lessons in this
section.)

1.2. (Lesson 1)
1.2.1. (Detail)
1.2.2. (Detail)

6. Project Manager Comments


(Record closing thoughts about the project here, but remember that this is retained as an official project
document. Conclude this section by describing the way you celebrated the completion of the project with
your team.)

7. Project Completion Acceptance

Project Role Name Signature (Electronic is Date


acceptable)

Executive Sponsor

Functional Owner

Service Owner

Project Manager

Director

You might also like