In this blog, we will explore the inputs, tools and techniques, and outputs of the Close Project or Phase process.

This process finalizes all activities for a project, phase, release, or iteration—whether successful or not. It confirms that the work is completed, value or capability is delivered as far as possible, transitions the results to operations or the next phase, captures lessons learned, and releases resources.

Let’s begin with the main output of this process—the Final Product, Service, or Result Transition. This represents the formal handover of completed deliverables to operations, support teams, the customer, or the next phase.

To achieve this, we need Accepted Deliverables as a key input. Accepted Deliverables are the output of the Monitor and Control Project Scope process. Once the work is completed and reviewed with stakeholders, and formally accepted by them, the deliverables become accepted deliverables.

Now, let’s look at another important input—the Project Charter. The charter defines the original purpose, objectives, high-level scope, and success criteria of the project. During closure, we compare what was achieved against what was originally authorized.

This helps us evaluate whether the project or phase has met its intended goals and whether it aligns with the business case.

Next, the Business Documents.

Business  Case – Describes the expected benefits and justification. At closure, you evaluate whether the project has delivered (or is on track to deliver) the expected value.

Example
The business case predicted a 20% productivity increase; early post-implementation data suggests 15%, which is noted in the final report with commentary.

Benefits Management Plan

Describes how and when benefits will be realized and measured. At closure, you confirm which benefits are realized now vs. in the future and who will track them. It ensures there is a clear owner and mechanism for tracking benefits after the project ends.

Project Management Plan – All Components

The Project Management Plan guides how the project is executed, monitored and controlled, and ultimately closed. It helps ensure that the project is wrapped up in a structured and proper manner.

During closure, we verify whether the planned work has been completed within the approved scope, schedule, and budget, as defined by the baselines.

While all components of the Project Management Plan may be relevant at this stage, its key role is to serve as a comprehensive reference of what was originally planned, enabling us to confirm completion and explain any variances.

Project Documents

The PMBOK ITTO list calls out several project documents

Assumption Log

Contains assumptions and constraints recorded throughout the project. At closure, you validate which assumptions proved true or false. It provides powerful lessons learned and context for explaining variances and outcomes.

Basis of Estimates

Documents how estimates were derived. At closure, you compare actuals to these bases to understand accuracy and bias. It helps improve future estimating practices by showing which methods and assumptions worked and which did not.

Change Log

Lists all change requests and their outcomes. At closure, you verify all changes are resolved and use the log to explain how the scope evolved.

It provides traceability of how the final product differs from the original scope and supports audit and accountability.

Issue Log Tracks issues and their resolution. At closure, you ensure no critical issues remain open or that any remaining ones are clearly transitioned.

It avoids leaving unresolved problems without an owner as the project team disbands.

For example An open issue about minor UI improvements is assigned to the operations team and noted as part of the transition.

Lessons Learned Register  Contains ongoing lessons captured during the project. At closure, you consolidate and finalize these into a more formal knowledge artifact. It allows the organization to reuse learning and not repeat the same mistakes in future projects.

Milestone List

Shows planned milestones. At closure, you confirm which milestones were achieved, delayed, or missed, and why. It helps explain schedule performance and identify scheduling improvements.

Project Communications

Includes emails, reports, minutes, and other communication artifacts. During closure, you may review them to reconstruct key decisions and prepare the final report.

For Example You use steering committee minutes to document when the decision to reduce scope was made and who approved it.

Quality Control Measurements

Contain actual test and inspection results. At closure, you verify that the product meets the quality criteria agreed in the quality management plan. They support objective confirmation that acceptance criteria and quality standards are met.

For example Test reports show 100% pass rate for all high-priority test cases; this is cited in the final report as evidence of product readiness.

Quality Reports

Summarize quality issues, trends, and resolutions over the project. At closure, they inform the final quality assessment and lessons learned. They highlight recurring quality issues and improvements that can guide future projects.

Requirements Documentation

Defines detailed requirements. At closure, you confirm which requirements were delivered, deferred, or dropped. It ensures clarity on what the project actually delivered versus what was originally requested.

For example – You mark some “nice-to-have” requirements as not implemented and document the agreed rationale (budget and time constraints).

Risk Register

Lists identified risks and their status. At closure, you update it for final risk outcomes and note any residual or secondary risks.

It supports risk lessons learned and ensures remaining risks are transferred to operations if relevant.

Risk Report

Summarizes overall risk exposure. At closure, you describe how risk profile evolved and how effective the risk responses were.

For example – The final risk report may show overall risk exposure decreased over time due to strong mitigation actions, which is highlighted as a success factor.

Next Agreements / Procurement Documentation

Contracts and procurement files are needed to confirm all contractual obligations are fulfilled and to close contracts formally. They protect the organization legally, ensure vendors are paid correctly, and prevent future disputes.

Organizational Process Assets

Existing OPAs (templates, policies, repositories) guide how closure is done and where closure artifacts must be stored. They standardize closure and ensure documents and knowledge are stored in accessible, recognized locations.

For example – The PMO’s closure checklist and final report template are used to structure the closure work and documentation.

Now Let’s talk about the tools and techniques.

Expert Judgment – Experts (PMO, legal, finance, operations, technical leads) advise on whether closure is complete, compliant, and properly documented.

Example
Finance experts verify that all invoices are reconciled and that project financial accounts can be closed.

Data Analysis – Document Analysis

During the project closure, it is needed to Review the plans, contracts, reports, and to validate that the requirements, scope, quality, financial, and contractual obligations are completed.

It provides evidence-based confirmation of completion and supports an accurate final report.

Data Analysis – Regression Analysis

Regression analysis can be used to understand relationships between project variables (e.g., cost vs. time) and performance, often for lessons learned.

It reveals drivers of cost and schedule performance that might not be obvious, informing future planning and control.

Data Analysis – Trend Analysis

Trend analysis examines performance over time (cost, schedule, defects) to see whether things improved or worsened.

It provides insight into the effectiveness of management actions and process changes across the project.

For example – Defect trends show a steady decline after a new code review practice was introduced, supporting that practice for future projects.

Data Analysis – Variance Analysis

Variance analysis compares planned vs. actual performance for scope, schedule, cost, and quality to explain deviations.

It provides a structured basis for explaining overruns or underruns in the final report and generating lessons learned.

Meetings

Closure meetings (final project review, lessons learned workshop, handover meeting) gather input from stakeholders and formalize acceptance and transition.

These meetings enable collective reflection, agreement on closure, and a clear handover of responsibilities.

Example – In a final lessons learned workshop, the team and stakeholders discuss what went well, what did not, and what to change next time.

Now let’s talk about the outputs.

Lessons Learned Register – You consolidate and refine lessons from throughout the project, adding closure-specific insights. It captures knowledge so future projects can benefit, reducing repeat mistakes and spreading effective practices.

Final Product, Service, or Result Transition

This is the formal handover of the completed deliverable(s) to operations, support, the customer, or the next phase team. It ensures that the receiving organization has what it needs (documents, training, access, responsibilities) to operate, support, or build on the deliverable.

Final Report

The final report summarizes performance, outcomes, variances, benefits, issues, and lessons learned.

It provides management with a clear record of project results and supports organizational learning.

For example – The final report includes final schedule and cost performance, key risks managed, benefits achieved so far, and major lessons.

Organizational Process Asset Updates

You update OPAs with closure artifacts (like the final report, final metrics, templates, checklists, lessons, contract closure docs) and potentially refine standards. It enriches the organization’s knowledge base and may improve methodologies, standards, and templates for future projects.

And that’s it.

With that, we have completed the Close Project or Phase process.

I hope you now have a clear understanding of how projects are formally closed, how knowledge is captured, and how deliverables are successfully transitioned to the people who will use and support them.