Close Project or Phase in PMBOK 8 — Complete Guide

Article updated in March 2026 for the PMBOK® Guide — Eighth Edition.

Close Project or Phase in PMBOK 8 — Complete Guide

Formerly known as: Close Project or Phase (PMBOK 6)

The product had launched. The client was satisfied. The team had celebrated. And then, six months later, the audit arrived. The procurement auditor wanted the final vendor invoices. The legal team needed the signed acceptance documents. The finance department needed confirmation that all project accounts had been closed. The HR team was trying to release two contractors who were technically still assigned to the project in the system. And nobody could find the lessons learned documentation — because it had never been formally compiled.

Incomplete project closure is a hidden epidemic in project management. Teams declare success when the product is delivered and immediately move on to the next project. The administrative, contractual, financial, knowledge, and resource closure activities — the boring but essential work of formally ending a project — are abandoned in the rush to the next initiative. The consequences accumulate: financial liabilities that aren’t properly closed, contractual obligations that are forgotten, organizational knowledge that is lost, resources that aren’t released for new priorities, and compliance evidence that can’t be produced when auditors ask.

In PMBOK 8, the Close Project or Phase process is the final and arguably most undervalued process in the Governance domain. Process 9 of 9, it involves finalizing all activities related to both successful and unsuccessful projects, phases, releases, iterations, or contracts. The close project or phase PMBOK 8 process provides three primary benefits: archiving project or phase information, completing planned work, and releasing organizational resources for new projects. It also includes confirming the extent to which value or the capability to deliver value has been achieved.

This guide covers:

• What Close Project or Phase means in PMBOK 8 and how it compares to PMBOK 6
• Complete ITTOs from the PMBOK 8 PDF source
• Detailed closure activities for predictive and adaptive approaches
• Step-by-step application guide
• Two real-world examples (Project Phoenix and ProjectAdm)
• Downloadable templates
• Five common errors and how to avoid them
• Tailoring for predictive, agile, and hybrid contexts

1. What Is the Close Project or Phase Process

According to the PMBOK® Guide — Eighth Edition, the Close Project or Phase process involves finalizing all activities related to both successful and unsuccessful projects, phases, releases, iterations, or contracts. The primary benefits include archiving project or phase information, completing planned work, and releasing organizational resources for new projects. The process also includes confirming the extent to which value or the capability to deliver value has been achieved.

Critically, PMBOK 8 acknowledges that closure applies not only to successful projects but also to projects that are terminated before completion. The process includes establishing procedures to investigate and document reasons that the project may have been terminated before completion — ensuring that even failed projects generate organizational learning.

The close project or phase PMBOK 8 process is the final process in the Governance domain and the terminal process in the project life cycle. It is positioned in the Closing phase and draws inputs from the entire project execution history — charter, management plan, all project documents, deliverables, and business documentation — to produce a final, properly archived, and formally closed project record.

PMBOK 6 vs. PMBOK 8 Comparison

2. Why Use the Close Project or Phase Process

Direct Benefits

• Resource liberation: Formally releasing project resources — personnel, facilities, equipment, and budget — allows the organization to redeploy them to new priorities immediately
• Knowledge preservation: Final lessons learned capture and organizational process asset updates ensure that the project’s accumulated knowledge benefits future projects
• Financial finalization: Closing project accounts, processing final invoices, and reconciling financial records prevents lingering financial liabilities
• Legal and contractual clarity: Formal acceptance of vendor deliverables, closure of contractual agreements, and resolution of outstanding claims creates legal clarity and eliminates future liability
• Governance completion: Project closure completes the governance record — demonstrating that the project was properly authorized, properly executed, and properly concluded
• Value realization confirmation: The explicit PMBOK 8 requirement to confirm the extent to which value has been achieved ensures that project success is measured against the original business case, not just delivery of outputs
• Stakeholder satisfaction: Formal closure includes measuring stakeholder satisfaction — capturing feedback that informs both relationship management and future project approaches

Cost of Skipping This Process

• Financial liabilities from unclosed vendor contracts and unreconciled project accounts
• Resource constraints on new projects because staff, facilities, and budget are still formally assigned to a “closed” project
• Lost organizational knowledge from unfinalized lessons learned
• Compliance and audit exposure from incomplete contractual and regulatory closure
• Stakeholder dissatisfaction from a sense that the project “just stopped” without proper handover

3. Inputs, Tools & Techniques, and Outputs (ITTO)

The following ITTO table is extracted from the PMBOK® Guide — Eighth Edition, Figure 2-12 (page 136 of the source PDF).

Key ITTO Explanations

Inputs

• Project charter: The original project authorization document. At closure, the charter is reviewed to confirm that the project has delivered what was originally authorized — or to document why it has not.
• Project management plan — all components: Every component of the PMP must be reviewed at closure to confirm completion and compliance. The change management plan, quality management plan, risk management plan, and all subsidiary plans must be reviewed against actual project performance.
• Accepted deliverables: The formal record of deliverables that have been completed and accepted by the customer or sponsor. No deliverable should be closed without formal acceptance documentation.
• Business case and benefits management plan: These are consulted at closure to confirm the extent to which the project achieved its intended value — a distinctive PMBOK 8 emphasis on value realization rather than just output delivery.
• Agreements and procurement documentation: All vendor contracts and procurement records must be reviewed and formally closed. Open claims, guarantees, and warranties must be resolved.

Tools & Techniques

• Document analysis: Systematic review of all project documents to confirm completeness and compliance. Identifies any documentation gaps that must be addressed before the project can be formally closed.
• Variance analysis: Compares planned performance against actual performance across the full project history — providing the analytical basis for the final report and lessons learned.
• Regression analysis and trend analysis: Examine project performance trends over the life cycle to identify systemic patterns — not just endpoint comparison of plan versus actual, but the trajectory that led to those outcomes.
• Meetings: Close-out meetings with the team, sponsor, client, and key stakeholders to formally confirm project completion, acknowledge contributions, and facilitate knowledge transfer.

PMBOK 8 Predictive Closure Activities (Section 2.1.6.9.1)

Satisfying completion or exit criteria:

• Ensure all documents and deliverables are updated and all issues are resolved
• Ensure the measurable project value was delivered with a plan to maintain it post-transition
• Confirm deliverables have been delivered and formally accepted by the customer
• Verify that all costs have been charged to the project
• Close project accounts
• Reassign or release project personnel
• Address excess project materials
• Reallocate or release project facilities, equipment, and other resources
• Prepare final project reports as required by organizational policies

Contractual agreement completion:

• Confirm formal acceptance of the external source’s work
• Finalize any open claims, guarantees, and warranties
• Update records to reflect final results
• Ensure all invoices due to external sources are paid
• Archive relevant information for future use
• Resolve any disputes or refer them to the dispute board

Additional closure activities:

• Collect and audit project or phase records
• Assess project success or failure
• Manage knowledge sharing and transfer
• Identify and document lessons learned
• Archive project information for future organizational use
• Transfer project products, services, or results to operations
• Collect suggestions for improving organizational policies and procedures
• Measure stakeholder satisfaction
• Verify all contractual, regulatory, legal, social, and environmental obligations have been met
• Identify outstanding risks to be accepted or transitioned to operations

PMBOK 8 Adaptive Closure Activities (Section 2.1.6.9.2)

In adaptive approaches, closure centers on wrapping up all activities related to the release or iteration:

• Confirm that prioritized backlog items are finished and all acceptance criteria are met
• Ensure all deliverables have been reviewed and accepted by stakeholders
• Conduct a final review to verify all project tasks are completed with no outstanding issues
• Facilitate knowledge-sharing sessions to transfer insights among the team
• Hold retrospectives to identify lessons learned and improvement opportunities
• Discuss outstanding risks to be accepted, transitioned to subsequent iterations, or carried into operations

Outputs

• Final report: The comprehensive summary of the project — objectives, performance against plan, change history, final cost and schedule actuals, quality performance, risk management outcomes, stakeholder satisfaction, value delivered, and lessons learned summary. This is the definitive project record for organizational use.
• Final product, service, or result transition: The formal handover of the project’s output to operations, the client, or the next phase. This may include training, documentation, support agreements, and transfer of ownership of project assets.
• Organizational process asset updates: All project documentation — templates updated, lessons learned formalized, historical performance data archived — contributed to the organizational knowledge base for future project benefit.
• Lessons learned register update: The final, comprehensive update to the lessons learned register capturing insights from the entire project life cycle.

4. Step-by-Step Application Guide

1. Review the project charter against delivered outcomes. Compare what was originally authorized against what was delivered. Confirm that all project objectives defined in the charter were met — or document why they were not. This is the PMBOK 8 value realization check: did the project deliver the intended value? Consult the business case and benefits management plan for the original value proposition.
2. Verify all deliverables are completed and formally accepted. Review the requirements documentation and acceptance criteria for every deliverable. Confirm that each deliverable has been formally accepted by the appropriate authority — customer, sponsor, or quality reviewer. Resolve any outstanding acceptance disputes before finalizing closure.
3. Close all vendor contracts and procurement documentation. For each vendor engagement: confirm formal acceptance of the vendor’s final deliverables; process all outstanding invoices; finalize open claims, guarantees, and warranties; update procurement records to reflect final results; and archive all contract documentation. Do not declare project closure until all vendor contracts are formally closed.
4. Close all project accounts and financial records. Verify that all costs have been charged to the project. Close project accounts to prevent further charges. Prepare financial reconciliation reports. Release any unspent approved budget back to the organizational funding pool per financial management procedures.
5. Release all project resources. Formally reassign or release all project personnel. Reallocate or release project facilities, equipment, and other resources. Update the resource management system to reflect these changes so that the organization can redeploy resources to new priorities without administrative barriers.
6. Complete final lessons learned and update organizational process assets. Conduct a structured final lessons learned session with the project team. Consolidate all lessons learned register entries into a comprehensive final document. Update relevant organizational process assets — templates, procedures, historical archives, and knowledge repositories — with insights from the project. This is the organization’s return on investment in the project’s knowledge management activities.
7. Produce the final report and conduct formal closure meetings. Compile the final project report — including objectives, performance summary, lessons learned, and value realization assessment. Conduct formal closure meetings with the team, sponsor, and client. Measure stakeholder satisfaction. Formally declare project closure and communicate it to all relevant stakeholders. Ensure that all contractual, regulatory, legal, social, and environmental obligations have been verified.

5. When to Apply This Process

The Close Project or Phase process is triggered by any of the following conditions:

• All project deliverables have been completed and accepted (successful project closure)
• A project phase is complete and the next phase is about to begin (phase closure)
• The project has been terminated before completion — due to changed business conditions, funding withdrawal, or strategic reprioritization (early termination closure)
• A release or iteration is complete (adaptive closure)
• All contractual obligations have been fulfilled (contract closure)

PMBOK 8 emphasizes that closure applies to unsuccessful projects as well as successful ones. Even terminated projects require systematic closure to protect the organization’s financial, contractual, legal, and knowledge interests.

Predictive vs. Agile Contexts

In predictive projects, closure is a comprehensive, document-intensive process covering all the administrative, contractual, and knowledge management activities described in Section 2.1.6.9.1 of the PMBOK 8 source. It typically spans several weeks and involves multiple stakeholder groups.

In agile projects, closure occurs at multiple levels: iteration closure (end of each sprint), release closure (end of each release cycle), and project closure (end of the overall initiative). Each level has its own closure activities aligned to PMBOK 8 Section 2.1.6.9.2 — focused on backlog completion verification, retrospectives, and knowledge transfer.

In hybrid projects, the predictive components require comprehensive administrative closure while the adaptive components close out iteratively, with a final project closure integrating both.

6. Real-World Examples

Example 1: Project Phoenix — Website Launch

Alex Morgan initiated the close project or phase PMBOK 8 process for Project Phoenix on day 88 of the 90-day project — building in time before the official deadline to ensure proper closure. The closure checklist was comprehensive: 47 deliverable acceptance confirmations, two vendor contract closures, financial account reconciliation, resource release, lessons learned finalization, and final report production.

The vendor contract closures revealed a nuance Alex had anticipated: the security testing vendor’s contract included a 30-day warranty period following final delivery, during which the vendor was contractually obligated to address any security vulnerabilities discovered in the initial audit. Alex documented this as an outstanding obligation in the final report and established a formal handover protocol with TechCorp’s IT security team to manage the warranty period — ensuring that the obligation didn’t get lost in the post-project transition.

The value realization review — conducted by comparing the original business case against delivered outcomes — showed that Project Phoenix had achieved 94% of the expected business value. The 6% gap was attributable to one feature deferred during the brand change request in week seven (already documented in the change log). CEO Sarah Chen formally accepted this outcome at the project close-out meeting, citing the documented change decision as the basis for the 6% shortfall. The governance record was complete, traceable, and defensible.

Alex’s final lessons learned document contained 31 insights, of which 19 were contributed to TechCorp’s project management office repository. The close project or phase PMBOK 8 process had produced organizational value that extended far beyond the website’s launch.

Example 2: Project ProjectAdm — SaaS PM Platform

Eduardo ran close project or phase PMBOK 8 activities on ProjectAdm across two levels: sprint closure (end of each two-week iteration) and the final project closure at platform launch. The sprint closure process was streamlined — 15 minutes of retrospective, a backlog completion check, and a three-item lessons learned log entry. Eleven months of sprint closures produced 187 documented lessons learned before the final project closure began.

The final project closure was more substantial: Eduardo and the team spent three days consolidating 11 months of sprint lessons into a final thematic analysis, identifying seven major themes that would inform how the organization approached SaaS development projects in the future. The DevOps vendor contract required formal closure including final performance rating submission to the vendor management system — which Eduardo completed with detailed documentation supporting the vendor’s performance rating.

The value realization assessment compared the original business case (projected first-year revenue from the platform) against the product’s actual market reception at launch. The platform exceeded first-month projections by 23% — a result Eduardo attributed directly to the continuous compliance monitoring and knowledge management processes that had prevented defects and informed product decisions throughout execution. The final report documented this causal chain explicitly, providing evidence that the close project or phase PMBOK 8 governance investments had contributed directly to business value.

7. Templates and Downloads

Apply what you learned with these templates from projectmanagement.com.br:

• Project Closure Document Template — Complete project closure report including deliverable acceptance checklist, lessons learned summary, value realization assessment, and resource release documentation
• Project Charter Template — Reference the original authorization document against which closure value realization is assessed

8. Five Common Errors

1. Error: Declaring project success when the product launches and skipping formal closure.
   Teams celebrate delivery and immediately move on, leaving financial accounts open, vendor contracts unresolved, resources formally assigned, and knowledge undocumented.
   How to avoid: Treat project closure as a mandatory deliverable with its own schedule, resources, and acceptance criteria. Add “project closure complete” to the project milestone list from the start, and allocate time and resources for it in the project schedule.
2. Error: Closing the project without formal deliverable acceptance documentation.
   Deliverables were “received” but never formally accepted in writing. Months later, the client claims a deliverable was not to specification — and there is no acceptance record to counter the claim.
   How to avoid: Require formal written acceptance for every deliverable before project closure. PMBOK 8 is explicit: confirm that deliverables have been delivered and formally accepted by the customer. No closure without acceptance documentation.
3. Error: Leaving vendor contracts open after the project ends.
   Vendor contracts are “assumed” to be complete but never formally closed. Warranty obligations are forgotten. Outstanding claims accumulate interest. Vendors continue invoicing against open purchase orders.
   How to avoid: Vendor contract closure is a mandatory close project or phase PMBOK 8 activity. Create a contract closure checklist that requires formal vendor acceptance confirmation, final invoice processing, warranty status documentation, and dispute resolution status before any vendor contract is considered closed.
4. Error: Conducting a single end-of-project lessons learned session after all memory has faded.
   A 2-hour session at project end produces a thin, generic document that captures surface-level observations rather than the rich insights accumulated throughout execution.
   How to avoid: PMBOK 8 and the Monitor Compliance process (Process 6) both emphasize continuous lessons capture. The close project or phase lessons learned session should consolidate and synthesize a register that has been actively maintained throughout the project — not create it from scratch.
5. Error: Skipping the value realization assessment.
   Teams confirm that outputs were delivered but never assess whether the intended business value was achieved. This leaves stakeholders without evidence that the project investment was worthwhile.
   How to avoid: PMBOK 8 explicitly includes confirming the extent to which value has been achieved as a closure benefit. Review the business case and benefits management plan at closure and document the value realization assessment in the final report — including any gaps and their documented causes.

9. Tailoring This Process

10. Process Interactions

Close Project or Phase is the terminal process in the Governance domain, drawing inputs from all preceding processes and producing the final organizational artifacts.

• Feeds into this process:
  • Initiate Project or Phase — the project charter provides the original authorization against which closure value realization is measured
  • Integrate and Align Project Plans — all project management plan components are closure inputs
  • Execute Sourcing Strategy (Process 4) — vendor deliverables and contracts are closure inputs
  • Manage Compliance (Process 5) — quality reports and compliance records are closure inputs
  • Monitor Compliance (Process 6) — lessons learned register is a primary closure input
  • Control Project Performance (Process 7) — final performance data is a closure input
  • Manage Change (Process 8) — change log and all approved changes are closure inputs
• This process feeds into:
  • Initiate Project or Phase — organizational process asset updates from closure (lessons learned, templates, historical data) inform future project initiation
  • Organizational operations — the final product, service, or result transition marks the handover to operational management

See the full process map at PMBOK 8 Complete Index.

11. Quick-Application Checklist

• Project charter reviewed — all original objectives confirmed as met (or documented gaps justified)
• All deliverables formally accepted in writing by the appropriate authority
• All vendor contracts formally closed with final invoice payment confirmation
• Open claims, guarantees, and warranties documented and resolved (or transferred to operations)
• All project accounts closed and financial reconciliation completed
• All project personnel formally reassigned or released
• All project facilities, equipment, and other resources reallocated or released
• Final lessons learned session conducted and register consolidated
• Organizational process assets updated with project lessons and templates
• Value realization assessment completed against original business case
• Outstanding risks documented and formally transferred to operations
• Final report produced and distributed to all relevant stakeholders
• Formal project closure declared and communicated to all stakeholders

Call to Action:

References

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Eighth Edition. Newtown Square, Pennsylvania, USA: Project Management Institute, 2025.

PMBOK Guide 8: The New Era of Value-Based Project Management. Available at: https://projectmanagement.com.br/pmbok-guide-8/

Disclaimer

This article is an independent educational interpretation of the PMBOK® Guide – Eighth Edition, developed for informational purposes by ProjectManagement.com.br. It does not reproduce or redistribute proprietary PMI content. All trademarks, including PMI, PMBOK, and Project Management Institute, are the property of the Project Management Institute, Inc. For access to the complete and official content, purchase the guide from Amazon or download it for free at https://www.pmi.org/standards/pmbok if you are a PMI member.