Author: © Megan
Download Now: Project-Closure-Report-Template-Free-Download.docx
Project Closure Report
Like all aspects of a project, its closure should be planned and tracked. This may one of the more overlooked aspects of project management, but its benefits and importance to the project and future ones like it are highly valued by project managers. A good project closure report should be the basis for a project plan for a similar future project.
The report compares between the plan at the beginning of the project, and the final outcome of it. This output is then presented to the key stakeholders, the client and vendors, and to the team members. This report is usually quite emotional, especially in a long term project. It is the final output of the team, and they know that once it’s completed, the project is finally over.
In order for the project to be officially closed, the following basic criteria must be met –
- The major milestones have been completed
- The above have met their quality specifications
- The key stakeholders (internal and external, i.e. the client) have accepted the closure and have signed off on it.
- The project has been completed on time and on budget (certain flexibility is acceptable here of course).
These criterions above can change from project to project, and must be defined upon its official kick off.
The most important steps of the closure report are –
- Actual vs. planned: the first step is to compare the actual timeline, scope, budget, quality and resource use to the planned ones at the beginning (or at the last scope change). This step will give a good sense of how successful the project was (the more successful, the closer the actual will be to the planned). This step is done by the PMO, and approved by the PM / COO.
- Interviews of the major team members: Once step #1 is completed, they should be presented to the team leads and managers in order to get their input, remarks and lessons learned. Also their contributions should be formally recorded and recognized, for future evaluation and compensation.
- The client needs to formally sign off on the project, herby confirming that the company has met all of its obligations as stated in the SOW / contract.
- A checklist with the major tasks of a closure report needs to be put together and approved.
- The CFO must approve that all of the expenditure is accounted for, and that all of the PO’s (Purchase Orders) have been fulfilled. In some cases an audit is required, in order to present to the customer that all of their payments were received.
- Identifying the records which need to be kept after the project has been completed is a very important step. Depending on the clients’ field of business and country, there are several rules & regulations which must be adhered to regarding record keeping. Any and all legal signed documents, PO’s, payments received and authorized and any other documents which the legal counsel of the company specifies must be kept and recorded. This can also help with planning a new project in a similar field.
- Once the above steps are completed and signed off by the PM and stakeholders, It must be communicated to all involved that work on the project must discontinue unless told otherwise.
- Once step #6 is done, all payments involved in the project need to be discontinued.
- If a maintenance project is signed (or included in the original contract), then the final scope in the project closure report will be the beginning point of the maintenance project.
The importance of a checklist
The attached checklist needs to be filled out and signed as a part of the report. Even seasoned PM’s and PMO’s who have brought many projects to a full closure, may sometimes overlook basic steps of the report. A checklist is the best way to avoid these mistakes, which may leave a bad taste in the mouths of otherwise happy and content clients. The checklist should also specify who is responsible for the tasks which appear in it.
All lists are prone to change according to the client, the company, the country and many other factors. The attached list specifies the basic and most important tasks, which should appear in any closure report.
The following points should be kept in mind when putting together a project closure report –
- Closing a report might be an emotional task for team members who have been involved in the project from the kick off, and have come to see the project as their “baby”. Keeping this in mind, it may be a good idea to bring in a team of people who weren’t directly involved in the project, or may have recently joined. This will ensure objectivity and that this task is seen as just another one in the projects’ lifecycle.
- Since this is the last major work of the project, and is usually done after the final deliverable has been signed off by the client, it may be not taken seriously by all of the team members. Perceiving the closure report as a mini-project with milestones, deadlines and a work plan can ensure that the report will be completed in a timely manner.
- Like any other tasks, planning this one well in advance will improve its final outcome.
- While debriefing the team members, it is a good idea for their immediate supervisor to review their work on the project and give them any constructive criticism. Most companies do this exercise on a yearly / bi-yearly basis, but at the closing a project is a much better time to review and analyse the team members’ contributions and personal KPI’s.
- The above debriefing (or interviews) should be done in a structured manner, with the projects’ goals clearly listed and weather the team member helped in its achievement.
- Usually the PMO writes the report, and the PM or COO approves it.
Was this document helpful? Rate it Now
Date Posted: 2017-10-03 04:09:03