Scribd
Upload
17 views6 pages

Project Close Out Template

The document outlines the project close-out process, detailing version history, general project information, management effectiveness, lessons learned, administrative and contract closure, and information distribution. It includes sections for summarizing project performance against baselines, challenges faced, and archiving relevant data. Additionally, it provides a framework for obtaining necessary approvals and references key terms used throughout the document.

Uploaded by

Ovan Triwinarko
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
17 views6 pages

Project Close Out Template

The document outlines the project close-out process, detailing version history, general project information, management effectiveness, lessons learned, administrative and contract closure, and information distribution. It includes sections for summarizing project performance against baselines, challenges faced, and archiving relevant data. Additionally, it provides a framework for obtaining necessary approvals and references key terms used throughout the document.

Uploaded by

Ovan Triwinarko
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/ 6

[PROJECT NAME HERE]

Project Close-Out
Date: June 15, 2021
Version: 1.5

Prepared By:

Maria Rodriguez
Job Title Goes here

VERSION HISTORY
[Provide information on how the development and distribution of the , up to the final point of approval, was
controlled and tracked. Use the table below to provide the version number, the author implementing the version,
the date of the version, the name of the person approving the version, the date that particular version was
approved, and a brief description of the reason for creating the revised version.]
Version Implemented Revision Approved Approval Reason
# By Date By Date
1.0 <Author name> <mm/dd/yy> <name> <mm/dd/yy> <reason>

Template Version Date: 06/15/21

[COMPANY NAME] | Address or Disclaimer text can go on P a g e |1


1 GENERAL PROJECT INFORMATION
[Enter high-level general project information. Expand this section to include more
information if needed for the project..]
Description
Project Name [Project name]
Project Description [Description of project]
Project Manager [Project Manager name]
Project Sponsor [Project Sponsor name]
General Comments [Any additional general comments]

Baseline Actual Variance % Variance


Start Date [mm/dd/ [mm/dd/yyyy] [000 days] [00.0%]
yyyy]
Finish Date [mm/dd/ [mm/dd/yyyy] [000 days] [00.0%]
yyyy]
Hours [000 hours] [000 hours] [000 hours] [00.0%]
Days [000 days] [000 days] [000 days] [00.0%]
Budget [$0,000.00s] [$0,000.00s] [$0,000.00s] [00.0%]
2 MANAGEMENT EFFECTIVENESS
[Summarize how effectively the management needs of the customer and project were
met. Highlight the significance of approved changes to the baseline, their impact on the
project, and how they were managed. Compare baselines to actual and describe
discrepancies. Identify and discuss specific issues that challenged the project/project
team. Consider areas such as cost, schedule, scope, quality, risk, issue, change,
communication, implementation and transition, regulatory compliance, and overall
project team performance.]
3 LESSONS LEARNED
[Summarize project lessons learned including the cause of issues, reasoning behind the
corrective action chosen, and other types of lessons learned. Identify and discuss specific
issues that challenged the project/project team.]
4 ADMINISTRATIVE CLOSURE
[Summarize project administrative closure activities such as procedures to transfer the
project products or services to production and/or operations; stakeholder approval for all
deliverables; confirmation that the project has met all sponsors, clients, and other
stakeholder’s requirements; verification that all deliverables have been provided and
accepted; validation that completion and exit criteria have been met; regulatory
compliance items.]

[COMPANY NAME] | Address or Disclaimer text can go on P a g e |2


5 CONTRACT CLOSURE
[Summarize project contract closure activities such as formally closing all contracts
associated with the completed project.]
6 INFORMATION DISTRIBUTION & ARCHIVE
[Summarize the data archived in the project repository. The type of information actually
archived will differ depending on the scope and type of project. Consider items such as
contracts and proposals, business case, charter, scope statement, schedule, budget
estimate, project management documents, surveys, status reports, checklists, and
emails.]

[Archived items distributed to individual upon project close out. Note that this list may
include individual without access to the project’s archive repository. This should be
considered when deciding on an appropriate distribution medium.]
Item Distribution List Distribution Medium
[Archived Item] [name] [Email, fax, website, etc]
[Archived Item] [name] [Email, fax, website, etc]

[COMPANY NAME] | Address or Disclaimer text can go on P a g e |3


Appendix A: Project Close-Out Approval
The undersigned acknowledge they have reviewed the Project Close-Out Form and agree with the
approach it presents. Changes to this Project Close-Out Form will be coordinated with and approved by
the undersigned or their designated representatives.

[List the individuals whose signatures are required. Examples of such individuals are
Project Sponsor, Business Steward, Technical Steward and Project Manager. Add
additional signature lines as necessary.]

Signature: Date:

Print Name:

Title:

Role:

Signature: Date:

Print Name:

Title:

Role:

Signature: Date:

Print Name:

Title:

Role:

[COMPANY NAME] | Address or Disclaimer text can go on P a g e |4


Appendix B: References
[Insert the name, version number, description, and physical location of any documents
referenced in this document. Add rows to the table as necessary.]
The following table summarizes the documents referenced in this document.

Document Name Description Location


and Version
<Document Name [Provide description of the <URL or Network path where
and Version document] document is located>
Number>

[COMPANY NAME] | Address or Disclaimer text can go on P a g e |5


Appendix C: Key Terms
[Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link
below to for definitions of project management terms and acronyms used in this and other documents.

http://www2.cdc.gov/cdcup/library/other/help.htm
The following table provides definitions for terms relevant to this document.
Term Definition
<Term> <Definition>
<Term> <Definition>
<Term> <Definition>

[COMPANY NAME] | Address or Disclaimer text can go on P a g e |6

You might also like