---
ref_id: PR40
ref_type: Process
ref_name: "Close Project or Phase"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1"
companion_ref_shortcode: PG-APG
related_skills:
  - SKL-06-01
  - SKL-06-09
  - SKL-06-10
related_artifacts:
  - A24
  - A30
  - A34
file_path: "reference/processes/PR40-close-project-or-phase.md"
---
# PR40 — Close Project or Phase

## Process Identity
| Field | Value |
|---|---|
| **Process ID** | PR40 |
| **Process Name** | Close Project or Phase |
| **Process Group** | Closing |
| **Knowledge Area** | Integration Management |
| **PMBOK Source** | Process Groups: A Practice Guide §8.1; PMBOK 8 §2.1.6 |

---

## Purpose
Finalize all activities for the project, phase, or contract. Project or phase information is archived, the planned work is completed, and organizational team resources are released to pursue new endeavors.

---

## Inputs
| Input | Description |
|---|---|
| Project charter | Original project authorization document |
| Project management plan | All components |
| Project documents | Assumption log, basis of estimates, change log, issue log, lessons learned register, milestone list, project communications, quality control measurements, quality reports, requirements documentation, risk register, risk report |
| Accepted deliverables | Formally accepted outputs from Validate Scope |
| Business documents | Business case, benefits management plan |
| Agreements | Contracts and procurement agreements |
| Procurement documentation | Contract records and supplier correspondence |
| Organizational process assets | Closure templates, historical information |

---

## Tools and Techniques
| Tool / Technique | Notes |
|---|---|
| Expert judgment | Administrative closure, lessons learned facilitation |
| Data analysis | Document analysis, regression analysis, trend analysis, variance analysis |
| Meetings | Final lessons learned session, stakeholder satisfaction review |

---

## Outputs
| Output | Description |
|---|---|
| Project documents updates | Lessons learned register (final update) |
| Final product, service, or result transition | Formal handover to operations or the customer |
| Final report | Summary of project performance — scope, schedule, cost, quality, risks |
| Organizational process assets updates | Lessons learned repository, historical project data, closure documents |

---

## Administrative Closure Activities
- Confirm all deliverables are up to date and all issues are resolved.
- Confirm formal acceptance of deliverables by the customer.
- Ensure all costs are charged to the project.
- Close project accounts.
- Reassign personnel.
- Deal with excess project material.
- Reallocate facilities, equipment, and other resources.
- Elaborate final project reports as required by organizational policies.

## Contractual Closure Activities
- Confirm formal acceptance of the seller’s work.
- Finalize open claims.
- Update records to reflect final results.
- Archive information for future use.

## Knowledge Closure Activities
- Collect project or phase records.
- Audit project success or failure.
- Manage knowledge sharing and transfer.
- Identify lessons learned.
- Archive project information for the organization.

---

## Key Concepts
- Performed **once** or at predefined points in the project.
- The **final report** includes cost objectives, validation summary, schedule objectives, business need fulfillment, and risks/issues encountered.
- If a project is **terminated early**, this process also documents the reasons.
- The project manager must engage all proper stakeholders throughout this process.

---

## PMBOK 8 Alignment
- Closing activities are distributed across all performance domains in PMBOK 8.
- Lessons learned are central to the **Manage Project Knowledge** process (§2.1.6.6).
- Benefits realization and stakeholder satisfaction are key closure outcomes.

---

## Related Processes
- Depends on: PR32 (Validate Scope) — accepted deliverables
- Depends on: PR41 (Control Procurements) — closed procurements
- Terminal process: no downstream project processes

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A24 | Artifact | Primary artifact produced or updated by this process |
| A30 | Artifact | Primary artifact produced or updated by this process |
| A34 | Artifact | Primary artifact produced or updated by this process |
| SKL-06-01 | Skill | Skill that executes this process |
| SKL-06-09 | Skill | Skill that executes this process |
| SKL-06-10 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Is formal stakeholder acceptance obtained for all deliverables before closure?
2. Are lessons learned finalized, reviewed, and archived in the organizational knowledge base?
3. Are all contracts and procurement activities formally closed?
4. Is the benefits transition plan executed and benefits ownership confirmed?
5. Are all resources formally released and records archived per retention policy?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
