Ending a project correctly matters as much as starting it right. PMBOK® 8 walks you through each closure step so nothing critical gets skipped.
1. Why Is Closure the Most Overlooked Phase?
When a project nears the finish line, everyone has already "mentally moved on" — the PM is thinking about the next project, team members have been pulled onto new assignments, and the sponsor loses interest once value has been delivered. The result: closure gets cut short or skipped entirely.
The consequences? Contracts don't close — vendors send invoices but no one verifies them. Lessons learned go uncaptured — the same mistakes repeat on the next project. Operations isn't ready — the support team receives the product without knowing how to run it. Stakeholder satisfaction goes unmeasured — the PM never knows whether the project truly succeeded.
PMBOK® 8, Section 2.1.6.9: "Close Project or Phase is the process of finalizing all activities related to the project or phase, including archiving knowledge, completing planned work, and releasing resources for new projects or operations."
2. The Four ECO Enablers — Project Closure Framework
Step | Enabler | Core Question |
|---|---|---|
1 | Obtain stakeholder approval | Have stakeholders accepted the deliverables? |
2 | Determine closure criteria | What criteria confirm the project is complete? |
3 | Validate readiness for transition | Is the operations team ready to receive the product? |
4 | Conclude activities | Have all closure activities been completed? |
3. Obtain Stakeholder Approval — Formal Acceptance
PMBOK 8 states clearly: "Confirm that deliverables have been delivered and formally accepted by the customer." Acceptance is not an email saying "looks good" — it is formal acceptance based on acceptance criteria defined at the outset.
Predictive: Formal Acceptance Process
Deliverables verified through Quality Control (inspection, testing)
Deliverables validated through Validate Scope (customer acceptance)
Acceptance signed by authorized stakeholders (sponsor, customer representative)
Accepted deliverables documented and archived
Adaptive: Iteration-Based Acceptance
PMBOK 8: "Confirm that all acceptance criteria are met. Ensure that deliverables have been reviewed and accepted by the appropriate stakeholders." In agile, acceptance happens each sprint through sprint reviews — closure represents the final acceptance for the entire product.
🌟 Important: If a stakeholder does NOT accept a deliverable — the PM must document the reasons, assess the impact, and determine next steps (rework, change request, dispute resolution, or partial acceptance with conditions).
Measure Stakeholder Satisfaction
💡 PMBOK 8 lists "Measure stakeholder satisfaction" as a mandatory closure activity. This is not a courtesy — it is data for the organization: did the project truly deliver value? NPS, satisfaction surveys, interviews — all must be completed before the team disbands.
4. Determine Closure Criteria — When Is "Done" Really Done?
PMs must define closure criteria before the project begins — not when the project is nearly over.
Closure Criteria Checklist — PMBOK 8
Category | Criteria | Evidence |
|---|---|---|
Deliverables | All deliverables delivered and accepted | Signed acceptance documents |
Scope | Scope objectives met, completion criteria verified | Scope verification reports |
Quality | Quality objectives met, standards verified | Test reports, audit results |
Schedule | Milestones completed, actual vs planned dates | Schedule performance data |
Cost | Budget reconciled, final accounting complete | Cost reports, final EVM |
Contracts | All contracts formally closed, payments processed | Contract closure docs, procurement audit |
Compliance | Regulatory, legal, environmental obligations met | Compliance certificates, audit reports |
Knowledge | Lessons learned captured, knowledge transferred | Lessons learned register, final report |
Resources | Resources released, equipment returned | Release confirmations |
Stakeholders | Satisfaction measured, feedback collected | Survey results, NPS |
PMBOK® 8: "The project manager should ensure that all work is completed and that the objectives are met by reviewing the project management plan."
5. Validate Readiness for Transition
This is the step many PMs skip — and the operations team pays the price. PMBOK 8 output: "Final product, service, or result transition" — transferring from the project team to those who will operate and maintain the product.
Transition Readiness Checklist
Area | Assessment Question | Action If Not Ready |
|---|---|---|
Operations team | Sufficient staff with the right skills to provide support? | Training, staffing, knowledge transfer sessions |
Documentation | Are runbooks, troubleshooting guides, and architecture docs complete? | Co-create documentation with the operations team |
Support processes | Help desk, escalation paths, SLAs established? | Set up support infrastructure before go-live |
Environment | Production environment stable, monitoring in place? | Infrastructure verification, monitoring setup |
Outstanding issues | Open defects and technical debt documented? | Handover issue log with priorities |
Warranty | Post-launch support period defined? | Define warranty terms, transition support team |
💡 PMBOK 8 also emphasizes: "Identify outstanding risks that should be accepted or transitioned to operations." — Risks do not disappear when a project closes. They must be handed over alongside the product.
6. Conclude Activities — Complete Closure Checklist
PMBOK 8 lists 12 specific closure activities. Here they are organized into four groups:
Group 1: Administrative Closure
- Ensure all documents and deliverables updated, all issues resolved
- Collect and audit project records
- Assess project success or failure
- Archive project information for future organizational use
Group 2: Knowledge and Learning
- Lessons learned — Identify and document lessons learned. PMBOK 8 Adaptive: "Facilitate knowledge-sharing sessions to transfer insights."
- Final retrospective — What went well? What didn't? What should the organization do differently?
- Knowledge transfer — Manage knowledge sharing and transfer to operations and the organization
Group 3: Financial and Procurement
- Final accounting — Reconcile all costs, process final payments, close purchase orders
- Contract closure — Formally close all vendor/supplier contracts
- Procurement audit — PMBOK 8: "A structured review of the procurement process for completeness, accuracy, and effectiveness."
Group 4: People and Stakeholders
- Resource release — Release team members, equipment, and facilities
- Recognition — Celebrate achievements, acknowledge contributions
- Stakeholder satisfaction — Measure and document
- Suggestions collection — Collect suggestions for improving organizational policies
Final Report — PMBOK 8
PMBOK 8 describes the Final Report as including: a summary-level project description, scope objectives plus completion evidence, quality objectives plus verification, cost objectives plus actuals plus variances, a summary of validation for the final product, schedule objectives plus milestone dates plus variances, a risk summary, and any other relevant information.
PMBOK® 8: The Final Report is a summary document for the organization — it becomes an OPA (Organizational Process Asset) for future projects. A PM who skips the Final Report leaves the organization without a valuable reference.
Early Termination
PMBOK 8: "The Close Project or Phase process also includes establishing procedures to investigate and document reasons that the project may have been terminated before completion." A cancelled project still requires closure — in fact, closure may matter even more in this case, because you must document why the project was cancelled, capture lessons learned, address remaining obligations, and assess the impact.
7. Predictive vs. Adaptive Closure
Aspect | Predictive | Adaptive |
|---|---|---|
Acceptance | Formal sign-off on all deliverables | Final sprint review + overall product acceptance |
Closure criteria | All scope items verified, baselines reconciled | All acceptance criteria met, product ready for use |
Lessons learned | End-of-project sessions (should be throughout) | Final retrospective + compile sprint retrospectives |
Documentation | Formal archives: plans, reports, baselines | Working software + essential docs + decision records |
Transition | Formal handover to operations with full docs | Often already in production via CI/CD; formal handover of support |
Contract closure | Same — all contracts formally closed | Same — all contracts formally closed |
PMBOK® 8 Adaptive Closure: "Confirm that all acceptance criteria are met. Ensure deliverables reviewed and accepted. Facilitate knowledge-sharing sessions. Hold final retrospective. Document key decisions, architecture rationale, and technical debt."
8. PMP Exam Tips
📍 Tip 1 — Lessons learned = throughout, not just at the end: PMBOK 8 is explicit: "incorporated during ongoing processes, not only at the end." When a question asks "when should lessons learned be captured?" — the answer is THROUGHOUT. But the closing phase is the LAST CHANCE — don't skip it.
📍 Tip 2 — Cancelled projects STILL need closure: When a project is cancelled — formal closure is still required: document reasons, release resources, close contracts, capture lessons learned. "Project cancelled = no closure needed" is always WRONG.
📍 Tip 3 — Procurement audit = mandatory: When a question asks "what should be done during contract closure?" — procurement audit always appears in the correct answer. It reviews the completeness, accuracy, and effectiveness of the procurement process.
📍 Tip 4 — Transition ≠ Just hand over: Transition includes training, documentation, support setup, transfer of outstanding risks and issues, and a warranty period. "Give them the code and walk away" = wrong answer.
9. Ten Scenario-Based Practice Questions
Question 1
Your project delivered all features, passed UAT, and the sponsor signed the acceptance document. However, the operations team says they're not ready to support the system — they haven't been trained and no runbooks exist.
Should you close the project?
A. Yes — the sponsor accepted the deliverables. Operations readiness is an operational issue.
B. No — readiness for transition is a closure criterion. Delay formal closure until operations is trained, documentation is complete, and support processes are in place.
C. Close the project but create a separate project for operations readiness.
D. Close the project and ask the sponsor to handle operations training.
Question 2
The project was cancelled at 60% completion due to a strategic pivot. The PM says: "Since we didn't finish, there's nothing to close. I'll release the team and start the new project."
Is the PM's approach correct?
A. Yes — cancelled projects don't need formal closure.
B. No — cancelled projects STILL require formal closure: document cancellation reasons, release resources, close contracts, settle financials, capture lessons learned, archive project info, and notify stakeholders.
C. Only close the contracts — everything else is unnecessary.
D. Have the PMO handle closure since the PM should focus on the new project.
Question 3
During project closure, you discover that one vendor contract was never formally closed. The vendor completed their work 4 months ago and final payment was made. The PM who managed that vendor has already left the organization.
What should you do?
A. The contract is effectively closed since work is done and payment made.
B. Formally close the contract: verify all deliverables were accepted, conduct a procurement audit, document vendor performance, and update organizational records.
C. Have legal close the contract since the PM left.
D. Send the vendor a contract closure notice and move on.
Question 4
The sponsor wants to skip the final retrospective because "the team is already moving to new assignments and it would be hard to gather everyone."
How should you respond?
A. Agree — the team is busy and forced retrospectives aren't productive.
B. Explain the value of final lessons learned for the organization, and propose an efficient format (90-minute focused session or async collection) that respects the team's time while capturing critical insights before institutional memory fades.
C. Conduct the retrospective without the sponsor's approval.
D. Send a lessons learned survey instead of a meeting.
Question 5
Your project's Final Report needs to be written. The sponsor asks: "What should be in it? Keep it practical."
Which elements should the Final Report include per PMBOK 8?
A. Just a summary of what was delivered and the final budget.
B. Project summary, scope objectives + completion evidence, quality objectives + verification, cost objectives + actuals + variances, schedule milestones + dates + variances, risk summary, validation of final product, and lessons learned.
C. A detailed log of all project activities from initiation to closure.
D. The project management plan updated with actual results.
Question 6
Your agile project delivered a product via CI/CD — features have been in production for months. The last sprint is complete and the product owner says "we're done." Operations has been supporting the product since Sprint 3.
What closure activities are still needed?
A. None — the product is already in production and operations is already supporting it.
B. Final sprint review for overall product acceptance, final retrospective, document architecture decisions and technical debt, formally close any vendor contracts, collect stakeholder satisfaction feedback, and create final report.
C. Just the final retrospective.
D. Archive the backlog and release the team.
Question 7
During closure, you find 3 open risks in the risk register that weren't fully mitigated. Two are related to system performance under peak load.
What should you do with these risks?
A. Close the risk register — the project is ending.
B. Document the open risks and formally transfer them to the operations team with recommended monitoring and response strategies.
C. Implement mitigations before closing the project.
D. Add them to the organization's enterprise risk register.
Question 8
The project is 95% complete. Two minor deliverables (help documentation and admin guide) remain, but the sponsor insists on closing immediately because "they're not critical." Budget and team are being reassigned.
What should you do?
A. Close the project — 95% is close enough.
B. Document the incomplete items, obtain formal acknowledgment from the sponsor that these deliverables are waived or deferred, and include this in the closure documentation to prevent future disputes.
C. Refuse to close until everything is 100% complete.
D. Complete the documents yourself after hours.
Question 9
Your team celebrated the go-live last week. This week, you ask the team to help write lessons learned. A developer says: "Why bother? Nobody reads those documents. Let's just move on."
How should you respond?
A. The developer has a point — lessons learned registers often go unread.
B. Acknowledge the concern, then explain that lessons learned have value beyond the document: the discussion itself builds team capability, specific insights can be applied to their NEXT project immediately, and well-captured lessons with "contact me" functions make them actionable for others.
C. Make it mandatory — it's part of the closure process.
D. Ask only senior members to contribute.
Question 10
Your construction project is complete. The client accepts the building. Six months later, a structural issue emerges. The client claims it's a project quality failure. Your team says the issue wasn't in the acceptance criteria.
What could have prevented this dispute?
A. More thorough testing before acceptance.
B. Clearer acceptance criteria AND a defined warranty period with specific post-closure support terms — both established during planning and formalized during closure. The closure process should have included comprehensive acceptance criteria covering long-term performance.
C. An extended project timeline for more quality checks.
D. A disclaimer in the closure documents.
Answer Key
Question 1: Answer: B
— PMBOK 8: closure includes "transfer products, services, or results to the next phase or into production/operations." Acceptance of deliverables ≠ readiness for transition. The PM should validate transition readiness BEFORE formal closure.
Question 2: Answer: B
— PMBOK 8: "Close Project or Phase also includes establishing procedures to investigate and document reasons the project may have been terminated before completion." Cancelled projects need closure even MORE — to capture why it failed, what was learned, and resolve all outstanding obligations.
Question 3: Answer: B
— PMBOK 8: "A procurement audit is a structured review of the procurement process for completeness, accuracy, and effectiveness." Payment ≠ closure. Formal closure includes verification, audit, performance documentation (OPA for future vendor selection), and proper contract termination.
Question 4: Answer: B
— PMBOK 8: "Identify and document lessons learned" is an explicit closure activity. The PM should advocate for it while being pragmatic about format. An efficient approach (focused session or hybrid) captures value without excessive disruption. Once the team disperses, these insights are lost forever.
Question 5: Answer: B
— PMBOK 8 Final Report specification includes all these elements. It's comprehensive but SUMMARY-level — not a detailed log (C) or just budget (A). The Final Report becomes an OPA for future projects.
Question 6: Answer: B
— Even with CI/CD and ongoing operations support, formal closure activities are still needed. PMBOK 8 Adaptive Closure: "Confirm acceptance criteria met, facilitate knowledge-sharing sessions, hold final retrospective, document key decisions and technical debt." Product in production ≠ project formally closed.
Question 7: Answer: B
— PMBOK 8: "Identify outstanding risks that should be accepted or transitioned to operations." Risks don't disappear when a project closes. The operations team must know what risks they're inheriting and how to monitor them. Closing the register (A) leaves operations blind.
Question 8: Answer: B
— If the sponsor chooses to close with incomplete items, it must be FORMAL — documented, acknowledged, and recorded. This protects the PM and the organization. PMBOK 8: "Ensure all documents and deliverables are updated and all issues are resolved" — if not resolved, they must be formally accepted as-is.
Question 9: Answer: B
— PMBOK 8 explicitly addresses this: "Tools that connect people to information can be enhanced by adding a 'contact me' function so users can reach the originators." The PM should make lessons learned VALUABLE, not just mandatory. When people see their insights helping future teams, they engage.
Question 10: Answer: B
— PMBOK 8: acceptance criteria should cover not just "what was built" but "how it should perform." Warranty terms define post-closure responsibility. The closure process should have formalized: what's covered, for how long, and who's responsible. Prevention during planning + formalization during closure = dispute prevention.
10. Conclusion
Project closure is the final chapter of the project story — but it determines how the project will be remembered, what the organization learns, and whether the product survives once the team disbands.
Three takeaways:
1. Closure is a process, not an event — Closing a project is not "sending a congratulations email and disbanding the team." It includes formal acceptance, knowledge transfer, procurement audit, financial reconciliation, lessons learned, resource release, and stakeholder satisfaction measurement. Each step has a purpose — skipping any one of them leaves a debt for the organization.
2. Transition ≠ Handing over code — The operations team must be READY: trained, equipped with documentation, informed about outstanding risks and issues. PMBOK 8 designates "final product transition" as the primary output of closure. A product nobody knows how to operate is a product that will fail.
3. Cancelled projects need closure too — A cancelled project still requires formal closure: document reasons, release resources, close contracts, capture lessons learned. Notably, lessons learned from a failed project are often MORE VALUABLE than those from a successful one — if you have the courage to capture them honestly.
PMBOK® 8: "Engaging relevant stakeholders is crucial to ensure a comprehensive closure process." — Closure is a collective responsibility, not the PM's alone. Sponsor, team, operations, vendors — all have a role to play.
Frequently Asked Questions (FAQ)
What steps does project closure per PMBOK 8 include?
Project closure includes: (1) Obtain final product acceptance from the customer/sponsor; (2) Complete final performance reporting; (3) Update lessons learned and OPAs; (4) Archive project documents; (5) Release project resources (team, budget, equipment); (6) Close contracts with vendors. Skipping any step creates loose ends for the organization.
Why are lessons learned important, and how do you do them well?
Lessons learned are organizational memory — they help future projects avoid past mistakes and build on proven practices. To make them effective: collect continuously (not just at project end), include both successes and failures, structure by topic (technical, management, stakeholder), and ensure they are stored in a searchable OPA repository.
How do you close a project that was cancelled early?
A cancelled project requires full administrative closure just like a completed one: document the cancellation reasons, return resources, close contracts, archive documents, and update lessons learned. PMs must not skip closure just because the project failed — OPA updates still deliver value to the organization.
Now that you understand project closure — it's time to practice with real exam questions.
Try Free PMP Practice Questions →
Official References:



