---
reference_type: Focus Area
reference_id: FA05
name: Closing
version: "1.0.0"
status: Active
pmbok8_source: "Process Groups Practice Guide — Closing"
authority: PMI-derived
---

# FA05 — Closing
**Type:** Focus Area
**PMBOK8 Source:** Process Groups Practice Guide — Closing
**Version:** 1.0.0

## Definition
Closing is the focus area in which all project activities are formally completed, final acceptance is obtained, deliverables and benefits are transferred to the receiving organization, resources are released, and organizational memory is captured and archived. Closing is not merely administrative finalization — it is the structured handover that ensures the benefits the project was chartered to deliver are transitioned and owned by the business. It also preserves institutional knowledge through lessons learned consolidation and records archival, protecting the organization's future capability. Closing applies at the end of the full project and, in multi-phase projects, at the conclusion of each phase.

## Entry Conditions
- All project deliverables have been formally accepted by the sponsor or designated acceptance authority
- Sponsor and key stakeholder acceptance is documented and obtained
- All procurement contracts have been administered, closed, or are ready for final closure
- All open issues in the Issue Log (A18) are resolved or formally accepted as residual
- Financial closure prerequisites are met (all invoices processed, final costs confirmed)
- Authorization to close has been granted through FA04 exit criteria

## Primary Activities
- Obtain final product, service, or result acceptance from the sponsor or client, documented with formal sign-off
- Finalize and close all procurement contracts; confirm supplier obligations are fulfilled; release vendor relationships
- Release team members and resources formally; conduct performance evaluations and transition team to other assignments
- Document and consolidate final lessons learned from all project phases into the Lessons Learned Record (A21)
- Archive all project records per the Information Retention Record (A34) and organizational retention policies
- Complete financial closure by reconciling final actuals, releasing unused budget, and submitting final financial reports
- Transfer benefits to the business owner per the Benefits Realization Plan; confirm benefit ownership and measurement responsibilities post-project
- Produce the final performance report summarizing actual vs. planned performance across scope, schedule, cost, quality, and risk
- Conduct the project closure review (post-project review) to assess team performance, process effectiveness, and organizational learning

## Primary Outputs / Artifacts Produced
| Artifact | Purpose |
|---|---|
| A27 — Project Closure Record | The formal document that declares the project closed, records final performance summary, and captures sponsor sign-off |
| A21 — Lessons Learned Record (final consolidation) | Consolidates all lessons learned from all phases into a single organizational learning asset |
| A24 — Closure and Benefits Transition Record | Documents the formal transfer of deliverables and benefit ownership to the receiving business unit |
| A34 — Information Retention Record (archival actions) | Documents which records are archived, where, for how long, and under what access controls |

## Artifacts Consumed (Inputs)
| Artifact | Source |
|---|---|
| A14 — Integrated Project Management Plan | FA02 Planning; the governing document against which final performance is assessed and closure completeness is verified |
| A13 — Requirements Traceability Matrix (all requirements accepted) | FA02 Planning; confirms that all requirements have been delivered and accepted before formal closure |
| A17 — Performance Reports (final) | FA04 Monitoring and Controlling; provides the cumulative performance record used in the final report and closure review |
| A30 — Knowledge Record (consolidated) | FA03 Executing; feeds the final Lessons Learned consolidation with execution-phase insights |
| A19 — Risk Management Record (closed risks) | FA04 Monitoring and Controlling; documents risk closure status and residual risk transfers to operations |

## Skills Active in This Focus Area
| Skill ID | Skill Name |
|---|---|
| SKL-06-01 | Close Project or Phase |
| SKL-06-02 | Final Performance Review |
| SKL-06-03 | Conduct Post-Project Review |

## Relationship to Performance Domains
Closing engages several key performance domains at their terminal and reflective stages:

- **PD8-01 — Governance:** The primary domain for closing; executes the Close Project or Phase process, formalizes organizational archives, reconciles budgets, and completes contract closures.
- **PD8-02 — Scope:** Confirms that all scope requirements have been delivered and accepted (Validate Scope output transition).
- **PD8-05 — Stakeholders:** Assesses final stakeholder satisfaction and obtains formal sponsor sign-off.
- **PD8-06 — Resources:** Releases team members and physical resources, and conducts team evaluations.
- **PD8-07 — Risk:** Identifies residual risks to transition to operations and closes the risk register.

## Exit Criteria / Quality Gate
- Project Closure Record (A27) is completed and signed by the sponsor
- All deliverables formally accepted and transition confirmed in the Closure and Benefits Transition Record (A24)
- All procurement contracts formally closed with no outstanding claims
- Lessons Learned Record (A21) finalized and submitted to organizational knowledge repository
- All project records archived per the Information Retention Record (A34)
- Financial accounts closed; final financial report submitted and accepted
- Benefits transferred per A24 with named operational owner and ongoing measurement plan
- All team members formally released and reassigned
- Post-project review completed and findings distributed to the PMO or sponsoring organization

*Authority: Process Groups Practice Guide — Closing · Source type: PMI-derived*
*Repository: https://github.com/fakhruldeen/PMOSkills*
